sneek_

WP made me want to pull my hair out

now that we're built on Next.js (3.0 beta), we now use Next.js as an optional head

you can still use Payload headless of course with any frontend but out of the box you have everything you need. it's pretty nifty

100%. We are actually working on a little "badge" style thing. Needed bad.

Hmm, one clarification - there is no enterprise Payload version. All of our enterprise features are just plugins - which anyone could build.

In this way, would you consider WordPress to be open-core as well, considering the amount of paid plugins there are available?

Fair. Good feedback. For what it's worth, we are actively looking at our licensing model trying to make it easier for situations exactly like yours.

Might have some updates for you soon.

Happy to hear this! Thank you for chiming in here. Hope to see you around the community.

Hey! Would love to hear more about this.

Performance problems are usually something related to maybe missing indexes in your database for fields that you query on often, or similar. Payload itself is super thin. Can you give me an example of where you're seeing slowdowns? Maybe I can point you in the right direction.

Also I would love to hear about where Payload is not flexible enough. Extensibility is one of our priorities so if there is something you'd like to accomplish, but can't, I will see what I can do about it!

Hey there - small to medium orgs can use one of the available community, open source SSO plugins, with the only caveat that they are not officially supported by Payload. Or you could build your own!

Question - does the word "enterprise" make you think that the amount we charge would make it unfeasible for your org to pay to use Payload?

I don't think it's ideal that we hide all our "premium" features behind the word "enterprise" and have been thinking of alternative words / messaging to describe that.

I think server components have been very badly marketed. They're totally opt-in, so I don't see how this would make React instantly a terrible framework. I for one think they represent a lot of value.

If you don't use them, then React is quite literally no different to you.

Hey! I'm CEO of Payload and want to make sure we resolve any bugs you found. Pretty much the whole team is focused on closing issues right now as we work toward 3.0 stable so depending on when you were trying out Payload, I'd imagine you might see lots of the bugs you faced as already resolved.

Keystone would be my other vote though, if I were looking for a CMS and Payload didn't exist. I think that is a solid crew.

We have a package that allows you to deploy Payload in a NextJS app serverlessly, and it works great. I actually tried bundling as one endpoint early on while exploring with the NextJS approach and it seemed to work perfectly. But honestly I can’t remember the pros and cons.

I’d say give it a shot, and if you need anything, let us know!

Thank you! That’s one of my favorite features too. Pretty straightforward to implement too. We’ve got some examples in the docs and the repo if you’re interested.

Honestly you nailed the reason why Payload exists. Both the editor AND developer experience are important and when you have both, you end up with a better project.

If you need anything as you build, let us know and we will make it happen! Exciting stuff.