We're on it. Actually I think the whole site needs to be redone but I'm never happy with my own work.
215 karma · joined March 2, 2021
We're on it. Actually I think the whole site needs to be redone but I'm never happy with my own work.
Both are possible. Thank you for your kind words!
However, v2 is coming and that will 100% be open-source!
Yes—as you mentioned, Payload is self-hosted, open-source, natively TypeScript and extremely extensible both on the API and admin UI sides. Outside of specific features that we support and others do not, those are the big differentiators. But there are lots more!
Yes, all of our first-party offerings are plugins and 100% of their functionality can be accomplished with Payload core itself. No need to fork or extend. Our plugin infrastructure runs incredibly deep and it's super straightforward.
Mongo was extremely deliberate. The nature of "content", especially pages and posts, lends itself extremely well to the document-based structure of NoSQL. Add in complex field types like arrays, a block-based layout builder, groups, and more, and this becomes even more apparent. But this all being said, supporting Postgres is on our radar and will be happening at some point. Our internal infrastructure is already quite organized and swapping out a different database adapter won't be a monumental task. It'll require some work, for sure, but it's doable.
Thank you for the great questions!
Payload could power the same use cases as something like vBulletin, but its use cases are significantly more widely applicable because Payload is not geared solely toward being community software. Instead, Payload delivers a content API and admin UI to power / manage just about any type of digital product you can think of, ranging from enterprise marketing websites, to native apps, to omni-channel content (think Spotify music), to SaaS app backends, to video games. Of course, forums are included here.
Does that help clarify?
Looking forward to it!
> I always came with the perspective that your CMS need not and usually should not be responsible for any of that and you can manage all of that in the application tier via a tag manager product or the like
Totally agreed. A CMS should stick to managing content. And its flexibility should allow it to integrate with services that are purpose-built. In addition to those that you mentioned, a good example of this would be Algolia for search experiences.
> "it will require far fewer developer hours to implement" which will resonate a lot more with budget holders.
I also resonate with this, and I think this needs to be worked into our positioning more, because that, at its core, is what Payload tries to do -through- its developer friendliness. When you don't have to fight your software, you save an incredible amount of time. At the core of any larger content infrastructure is code, and the more efficiently you can implement it, let alone maintain it, the more time / money you can save.
Great question!
For hundreds of seats, with a more robust SLA, your costs would scale linearly, but it's entirely based on what you need.
Does that help?
Would love to see if you gave this a shot, and we'd be happy to help along the way on Discord!
- We are open source / MIT
- You can re-use Payload's auth layer in your own apps and with Contentful you can't
- Contentful has rigid RBAC, but Payload features function-based access control down to the field level
- Payload supports field conditional logic, meaning "check a checkbox, see more fields, uncheck it, extra fields disappear". This is huge. And is super hard to build right but it's very important for a good admin experience.
- Payload gives you a local Node API (note: not HTTP / REST / GraphQL.) Contentful does not. With Payload's local API, you can do lots of awesome things within hooks, access control, etc. - and even reuse it in your own endpoints. All of this is impossible with Contentful without going through their HTTP layer
- Payload lets you add your own admin UI views
- Payload has no usage limits
- Payload is code-first, Contentful is "point and click"
Phew. There's a lot more. This all is just top-of-mind word vomit.
Our enterprise offering can either be self-hosted or it can leverage Payload Cloud, once we have it built. Some enterprises opt to manage Payload on their own infrastructure, and just pay us for SLA and premium features like SSO, audit logs, etc. But we do have enterprises in line to use our managed infrastructure as well... so basically, the answer is "both".
Does that help answer your questions?
It's true that some will self-host Payload, and that's awesome. But look at NextJS - you can self-host NextJS as well, but most people go to Vercel. Hosting a CMS is quite a bit more complicated than a static site or a set of serverless functions, because you need to have a database and permanent file storage as well. Payload will provide all of that out of the box with a one-click Git integration.
Our users thus far have been telling us that they struggle with cobbling together vendors and wish that this was easier, so we're building Payload Cloud as a result.
One other aspect of Payload Cloud is that even though we -provision- the infrastructure for you, you'll always have access to it. You'll be able to connect to your DB, back it up, export it, etc. This is all in the works now!
I would love to hear more about this at some point too, btw.
Outside of being written in TypeScript with more modern conventions, the fact that Payload borders on an application framework is what would make someone choose it over something like Drupal.
Feature-wise, this commonly means reusing Payload's auth in your own app(s), defining function-based access control rather than RBAC, swapping in React components into the admin UI, and more.
But another HUGE reason is that when we built Payload, we tried to keep its own internal conventions as close as possible to just regular JS / TS. If you know JS, you know Payload. With Drupal and even WP to an extent, you need to know how _their_ conventions work. It's all very specific to the platform and the Payload team has always hated that. Devs don't want to learn CMS - they want to learn the underlying language, and Payload embraces that to its core.
Payload's config is straight up TypeScript. Import a React component, pass it to your config, and boom — it shows up in your admin UI.
Everything is written like that and this is certainly where we shine!
How do you do your content nowadays? Git-based CMS? Markdown? Would love to know!
One goal of ours is to make this not the case - but you are 100% right. The whole notion of "app framework / headless CMS" doesn't have a good label so right now we've gotta make some concessions. We have this discussion quite often!
I think that your comment is pointing at one of the areas that traditional CMS -do not successfully address- in that CMS is typically only thought of as a means to manage website content. But content is much more broad. Think of Spotify (managing album art, playlists, artist descriptions) but using that content through native apps, smart TV apps, web apps, etc.
For example, some of our current enterprise clients are using Payload to deliver _their_ clients with a customized copy of Payload to manage their own virtual events (attendees, webinar links, landing page content, post-webinar video recordings, etc). Or to manage a "broadcast platform" where their client can publish their own Roku channel (episodes, series, seasons, playlists, etc). This is all content, yet it's not marketing page content.
One of the bigger uses of Payload so far has actually been to power the entire backend for an Uber-like snow plow service, where the business side can log in and provide customer support, manage requests, approve service providers, and more. The devs were able to leverage Payload's auth, access control, hooks for Stripe integration, and last but not least - the entirety of its admin UI.
That's not to say that we -can't- power marketing websites. Of course Payload can do that in spades. But that is only one small aspect of our target market and we make the most sense for enterprise content needs, where dev teams may need to manage more than just marketing pages. Maybe they also need to manage customer support resources or more intense content needs (like Klarna).
In my experience implementing enterprise websites for large companies, the buying process usually goes like this:
- Director or VP of Marketing says we need to modernize and move to a better web stack, let's go headless
- They start to evaluate options, but need engineering backup because headless CMS is a tech decision
- They tell their engineering team to go find the best headless CMS
- Devs do the recon, then report upward
Our strategy is to appeal straight to devs, and by being a solid product that they can advocate for, they will. This is actually how Klarna found my agency when we were hired to build their enterprise site - by the engineers. Decision to go headless came from the top, but then engineers found me and selected tech. Same with a few of Payload's bigger inbound enterprise opportunities in the pipeline right now.
Long story short, I fully understand your question and in all reality our messaging is nowhere near sharp / completed. We've seen a lot of growth over the past few months and are about to the point where we can take a breath, revisit some of this, and razor-sharpen our positioning!
WP is a blogging platform from the early 2000's that still uses many of the same code conventions that it started with. It does have a REST API, and you can extend it with plugins to work as a headless CMS, but it's riddled with inefficiencies and is truly a great example of why most devs would not think to reach for a CMS if they were building a SaaS app. Can you build a SaaS app with WP? Sure. Should you? Absolutely not. WP is good for its plugins and themes, but for anything more robust, it falls apart.
Strapi is a contender that is quite similar to Payload but they have a mixed focus on "GUI-based" logic and code-based logic. You design your content models with a GUI, and access control is highly limited to a typical RBAC pattern. Where in Payload, everything -starts with code-. You can version control your schema, because it's all just a config. Deploy to other environments (stage, prod, etc) with ease. Use and re-use functions across different collections. Even access control is handled beautifully with functions in Payload, and is significantly more powerful than RBAC.
I'd say our killer feature though is the simplicity, yet robustness of our admin UI. We have many features that Strapi does not have - like field conditional logic (Check a checkbox field, see more fields. Uncheck checkbox, those fields go away). Our admin UI is also completely extensible. You can create custom field types easily just by importing React components and passing them to a field config - then boom, your React component appears in the admin UI rather than the built-in component. It's intensely powerful.
There's a lot more, but these are just a few quick points. I've been using headless WP for ~6 years, and I've always liked the idea of Strapi, but never trusted it enough to hit production. That's why we built Payload.