TypeScript-native headless CMS and application framework that runs inside a Next.js app rather than alongside one.
TL;DR verdict
The best answer in this category for a Next.js team, and close to the only sensible one if an AI agent is doing much of the work. It asks for a framework commitment in return, and its scaffolding will not run unattended, which is an awkward shape of flaw for exactly that audience.
Payload is a headless CMS that installs into a Next.js application rather than running beside it. You describe each collection in a TypeScript configuration file, and the editing interface, the REST and GraphQL endpoints and the database tables are all generated from that description. A command regenerates TypeScript interfaces for your content, so the same definitions type your front end. It stores content in a database you choose and point it at, and it is published under the MIT licence for self-hosting.
The capabilities it ships, and which of them stand out.
Standout features
What the product does not do, kept separate from what we could not establish.
Product limitations
Could not verify
Teams already building on Next.js
One repository, one deployment and local data access make this materially simpler than running a CMS as a separate service, and none of that benefit is available to anyone on a different framework.
Projects where an AI agent writes much of the code
The schema is a file the agent can read and the generated interfaces constrain what it can invent. That combination is why this places second on our ranking of platforms for AI coding agents.
Applications where content and application data belong together
Pointing it at your existing Postgres puts editorial content in the same database as everything else, so relating the two is a query rather than a synchronisation job.
Anyone not using Next.js
The entire argument rests on running inside that framework. Outside it, you are taking on a younger ecosystem and a smaller plugin market in exchange for benefits you cannot collect.
Teams who need a price before a conversation
Self-hosting is free and everything above it is quoted, so a buyer who must present costed options to a finance team cannot do that from the public pages.
Marketing teams who want to compose pages visually
The generated interface is forms over fields, and visual editing sits behind the enterprise tier. Storyblok is built for page assembly and is the honest recommendation if that is the daily work.
MIT licensed and free to self-host with no seat or feature limits. Hosted templates and Enterprise are quoted through the get-started flow rather than a public price table.
| Plan | Published price | What the tier includes |
|---|---|---|
| Self-hosted | $0 |
|
| Enterprise | Custom |
|
Pricing watchouts
Rajat Kapoor
Co-founder, SaaSInsight
We wrote a collection definition in TypeScript, registered it in the configuration, and ran the type generator. It produced a complete interface for the collection along with a select helper, exactly as documented. This is the specific thing that makes AI-assisted work safer here than on a platform where the model lives in a dashboard: the agent cannot invent a field, because the compiler already knows the field list.
We also confirmed that the blank template registers the MCP plugin in its default configuration, rather than leaving it as an integration to add later.
One real obstacle. The supported installer requires an interactive terminal and fails with uv_tty_init returned EINVAL when run without one. For a product whose strongest audience is teams automating their tooling, having the official entry point refuse to run unattended is an awkward first impression.
One thing we should be clear about, so it is not mistaken for a finding. Pulling the template from the monorepo instead of using the installer ran into unresolvable workspace dependencies and APIs missing from the published packages. That was an unsupported route of our own choosing, not a defect, and it plays no part in the assessment.
We did not run this in production, operate it over time, or use the editing interface with real editors, so nothing here speaks to how the admin experience holds up in daily editorial use.
Most headless platforms are a separate service you integrate with: a hosted dashboard somewhere else, an API key, a deployment you do not control, and a permanent question about whether the schema in production matches the code that consumes it. Payload's proposition is to delete that seam. The CMS becomes part of the application, the definitions become part of the codebase, and the deployment becomes the one you already do.
The gains are concrete rather than architectural pleasantries. Fetching content locally rather than over HTTP to your own API removes a network hop and the failure modes around it. A schema change and the front-end change that depends on it can arrive in the same commit, reviewed together, which is not possible when the model lives in a vendor's dashboard. And the generated interfaces mean a mistake about the shape of your content is a compile error rather than an empty div in production.
The cost is a framework commitment, and it should be treated as one. Choosing this is choosing Next.js for as long as the site lives, because a migration away takes the CMS with it. That is a reasonable bet for many teams in 2026 and a bad one for anyone whose front end is uncertain.
There is also a maturity difference worth naming plainly. Against Contentful or Storyblok, this is a younger product with a smaller plugin ecosystem and fewer people who have already solved your unusual problem publicly. In exchange you get something they structurally cannot offer, so the trade is real rather than a straight downgrade, but a team that expects to find an answer to every question already written somewhere will notice.
The developer experience claims hold up. We tested the part that matters most for AI-assisted work and it did what the documentation says. What we could not establish is anything on the commercial side beyond self-hosting, because no figure is published for it. That is a limit on this assessment rather than a criticism of the product, and it is why the value score reflects a generous licence rather than a complete picture.
Where another tool in the category fits a reader better.
Choose this if you want the editing experience shaped in code but are not on Next.js, or want a hosted content API rather than one you operate.
Read reviewChoose this if you want an open-source CMS that is framework-agnostic, with a larger plugin ecosystem and a published hosted price.
Read reviewChoose this if marketing needs to assemble pages visually, which is the one thing this deliberately does not do outside its enterprise tier.
Read reviewAimed at what the public site cannot settle.
Yes, under the MIT licence, with no seat limits and no feature gates on the self-hosted version. That is a much larger free offering than a typical free tier, which usually caps users or API calls. The managed hosting and the enterprise tier are quoted rather than priced publicly.
Effectively yes, and you should treat it as a framework decision rather than a CMS one. It installs into the Next.js App Router and most of its advantage comes from being part of that application. On another framework you would be choosing a younger product without the benefit that justifies it.
It is among the best in this category, which is why it places second on our ranking for that use. The schema is a TypeScript file an agent can read and edit directly, the generated interfaces constrain what it can invent, and MCP is registered in the default scaffold with permissions settable per collection. The caveat is that the official installer will not run in a non-interactive shell.
MongoDB, Postgres or SQLite, selected by adapter when you set the project up. Pointing it at a Postgres instance you already run means editorial content and application data sit together, so relating them is an ordinary query rather than a synchronisation job.
Not in the version you can install for nothing. Editors get a generated form interface, and visual editing is listed among the enterprise capabilities. If page assembly on a canvas is what your team expects, this is not the platform for it.
Partly first-hand. In August 2026 we defined a collection in TypeScript, generated the types and confirmed the default MCP registration, which is what the ease of use score reflects, and we hit the installer's terminal requirement directly. We have not run it in production or used it for real editorial work, and no price is published above the free licence, so the commercial side is assessed only at that end.
Buy this if you are building on Next.js and expect to stay there. Nothing else in this category collapses the CMS and the application into one repository, and on a project where an agent is writing a good share of the code, a schema the compiler checks is worth more than any feature comparison will show. Two reservations. Scaffolding will not run unattended, which is an irritating shape of problem for exactly this audience, so plan the first setup as a manual step. And procurement cannot get a number from the public pages, so if a costed option is needed before anyone will engage, start that conversation early rather than at the end.
Try Payload freeUpdated September 2026
Hands-on tested. The account above is what we did with it, and the scores reflect that as well as the published evidence. How we rank
| Criterion | Weight | Score |
|---|---|---|
| Core capabilityHow well it does the job it exists for. | 30% | 8/10 |
| Value and real costWhat you actually pay, and whether you can find that out before you buy. | 25% | 8/10 |
| Ease of useSetup, day-to-day use and how long it takes to get something useful. Only scored when we have used it. | 20% | 6/10 |
| Integrations and extensibilityWhat it connects to, and whether your data can come back out. | 15% | 7/10 |
| Support and documentationWhat is committed to in writing, and what you can read without a sales call. | 10% | 6/10 |
By Rajat Kapoor. SaaSInsight is funded by labelled placements and affiliate links. Some links may be paid — always labelled. Read our disclosure policy.
