Payload
Open-source, Next.js-native headless CMS and app framework that installs into your existing app folder
Payload is an open-source headless CMS and backend framework that installs directly into an existing Next.js app folder, giving you a TypeScript backend and a React admin panel without standing up a separate service. It has 43,792 stars as of July 2026, is MIT-licensed, and deploys serverlessly on Vercel or Cloudflare as well as anywhere Node runs. For a founder it removes the reason content work usually stalls — there is finally somewhere non-technical to edit — but a CMS decides how pages get made, never whether anyone reads them.
What Payload is
Payload (github.com/payloadcms/payload) describes itself as the first Next.js-native CMS that installs directly into your existing app folder. Instead of running a separate CMS service and pulling content across an API, the backend and the admin panel live inside the Next.js app you already have, which means you can query the database directly from React Server Components. It is written in TypeScript, MIT-licensed, and has 43,792 stars as of July 2026.
The project positions itself as both an app framework and a headless CMS rather than only the content half, and it leans on that: the admin interface is generated from your own collection config and extended with your own server components. Getting started is a single create-payload-app command, and the maintainers point newcomers at the website template because it demonstrates the full set — rich-text blocks, on-demand revalidation, live preview — with a Tailwind front end in the same app folder.
What you get out of the box
The feature list below is what the repository itself advertises, not a wish list.
- A generated React admin panel — built from your collection config, extensible with your own server components, so editors get a real interface you did not have to design.
- Auth, versions and drafts — authentication, document versioning, drafts, a block-based layout builder, a Lexical rich-text editor, conditional field logic and granular access control are included rather than bolted on.
- Types that follow your data — a fully TypeScript codebase with automatic types generated for your own content, plus REST and GraphQL if you want them and direct database queries in server components if you do not.
- Deploy where you like — one-click serverless templates for Vercel and Cloudflare, or self-host on your own infrastructure; the project makes a point of having no vendor lock-in.
Where Payload fits a founder's growth stack
A CMS is the substrate under content-led growth. The moment you want more than a handful of pages — a blog, a comparison section, location or integration pages — the bottleneck stops being design and becomes publishing: who can add a page without a developer, and how fast. That is the machinery behind building SEO pages at scale and programmatic SEO, and Payload's official templates for a website, a blog and an ecommerce store are aimed squarely at it. Next to its neighbours, it overlaps Ghost on publishing and Medusa on storefronts while staying a general content backend rather than either.
The boundary worth being honest about is that a CMS decides how a page is made, never whether it earns a visit. Publishing capacity is necessary and not sufficient: what still has to happen is choosing subjects worth covering, writing something a reader could not get from the top of the results page, and earning the links and mentions that make any of it rank. Founders routinely install a CMS and conclude, months later, that content did not work — when what was missing was never the tooling.
A CMS, or content in code?
Not every site needs a CMS, and picking wrongly is expensive in both directions. The question is who edits, how often, and what has to be true before a page goes live.
| Approach | Best when | What you give up |
|---|---|---|
| Headless CMS like Payload | Non-technical people publish, content changes often, and you need drafts, versions and roles | A schema and a deployment to maintain; edits land through a UI rather than code review |
| Content in code, in typed data files | The people editing are the people shipping, and you want every change tested before it goes live | Anyone who cannot open a pull request cannot publish |
| A hosted SaaS CMS | You want no infrastructure at all and can live inside the vendor's model | Portability, and a bill that grows with your content |
First-party note from building AgentCeres — the AI Growth Officer at agentceres.com: our own marketing pages take the second route. Every answer, glossary and project page on this site is an entry in a typed TypeScript file rather than a CMS record, and that was a deliberate trade. Because the pages are code, a test suite runs on each one and fails the build when a page breaks a link, drops its internal links, or hardcodes a number that will go stale — checks a CMS structurally cannot perform, since its job is to accept what an editor typed. The cost is real and we pay it: nobody who cannot open a pull request can publish here. If our editors were not also the people shipping the app, Payload's model would be the right one.
FAQ
- Is Payload free?
- The framework is free and open source under the MIT license, so you can self-host it at no software cost and pay only for the infrastructure you run it on. The maintainers also sell Payload Cloud, a managed hosting option for teams that would rather not operate it, and the repository advertises one-click serverless deploys to Vercel and Cloudflare, which have their own pricing. Check the repository's license file for the version you install.
- Payload vs a hosted CMS like Contentful or Sanity — which should a founder pick?
- Pick a hosted CMS if you want zero infrastructure and the vendor's content model fits how you work. Pick Payload if you are already building on Next.js and want the CMS inside your own app, your data in your own database, and no per-seat or per-record ceiling to plan around. The trade is operational: Payload is code you maintain and deploy, while a hosted CMS is a service you configure and pay for.
- Do I need a developer to use Payload?
- To set it up, yes — collections, fields and access rules are defined in code, and the app is deployed like any other Next.js project. After that, no: the point of the admin panel is that non-technical people can create, edit, draft and publish content without touching the codebase. The developer cost is front-loaded into the setup rather than spread across every page.
- Does a CMS help with SEO?
- Indirectly, by removing friction. A CMS does not make pages rank, but it removes the reason most content programs stall, which is that publishing requires a developer. Faster publishing means more attempts, and more attempts is how content programs find what works. The ranking itself still comes from covering subjects properly, answering real questions and earning links — none of which any CMS supplies.
You built it. Now grow it.
AgentCeres is a managed AI marketing team — specialists draft the SEO, social, and outreach that fill your links, you approve what ships. 14-day free trial, from $19/month.