Payload CMS Review: Your Next.js Backend? (2026)

Quick Answer

Payload CMS is an open-source, Next.js-native headless CMS and backend framework (MIT license, v3.85.2 as of July 1, 2026, 43.4k GitHub stars) that runs inside your app's /app folder instead of on a separate server. As of July 2026 it is the strongest choice when you want a self-owned, code-first content and data layer bolted directly into a Next.js project. It is not a full SaaS starter: you still build your own billing, pricing pages, and user-facing auth flows around it. Pick Payload when you want to own the backend; pick something more assembled when you want the whole app scaffolded for you.

We curate open-source starters at ShipGarden by one rule: does it actually deploy, and what quietly breaks once it does. Payload passes the first test easily. The second test is where the honest notes live.

Payload is a headless CMS and application framework built with TypeScript that installs into an existing Next.js app. Instead of running a CMS on one box and your site on another, Payload's admin panel and REST/GraphQL/local APIs live in the same Next.js runtime. That single fact is why Next.js teams keep reaching for it. The Payload GitHub repository (43.4k stars, MIT, July 2026) and the official site both lead with the same line: it is the Next.js backend, not a bolt-on.

The five ways to deploy Payload

Every gallery review here ends with the same question a founder actually asks: how do I ship this, and what will it cost me on a Tuesday. Here are the five real paths, easiest to most owned.

Path 1 is genuinely a few minutes: scaffold, pick a database, open the admin panel at /admin. Path 3 is the one we recommend for most SaaS builders, because Payload is happiest as a long-running Node process where database connections stay warm. Path 2 (Vercel) works, but read the caveat below before you assume serverless is free-lunch. Path 5, Payload Cloud, is the maintainer's managed hosting; it is a paid product and pricing lives on payloadcms.com rather than being a fixed sticker we can quote here.

The database decision

Payload is database-agnostic through official adapters. Per the Payload database docs (2026), it officially supports three:

• 

  MongoDB with Mongoose (the historical default)

• 

  PostgreSQL with Drizzle
• SQLite with Drizzle

The Postgres and SQLite adapters run on Drizzle and are solid in 2026, but Payload grew up Mongo-first, so most tutorials and community answers still assume MongoDB. If your team is a Postgres shop, you are on a well-paved but slightly younger road.

What it really costs

Payload itself is $0. It is MIT-licensed, and you can self-host it forever without paying the maintainer a cent. Your real bill is the sum of three things you would pay for on any stack:

• Compute: a hobby deploy is free on

  

  Vercel or Railway; a small production node lands in the low tens of dollars a month in 2026.
• Database: a managed Postgres (Neon, Supabase) or MongoDB Atlas free tier covers early stage; you graduate to a paid tier when traffic or storage grows.
• Optional managed hosting: Payload Cloud if you would rather not run the Node process yourself.

So the honest cost story is: the framework is free, and you pay normal hosting math. There is no per-seat CMS tax and no content-entry paywall, which is the whole appeal versus a hosted SaaS CMS.

Where Payload loses

This is the section the agency blog posts skip. Payload is very good, and it is not for everyone.

It is a backend framework, not a SaaS starter. This is the big one. Payload gives you a content and data layer with a beautiful admin panel. It does not hand you a pricing page, a Stripe billing loop, a marketing site, or a finished end-user auth flow. You build those. A founder on r/nextjs put it plainly in May 2026: Payload is "very flexible, but out of the box it is pretty bare bones and you have to dev basically everything" (r/nextjs, 2026). That is not a bug; it is the design. Just know you are buying a backbone, not a business.

Serverless has friction. On Vercel, every function invocation wants a database connection, and a config-as-code CMS with a rich admin panel is heavier than a static content fetch. You will reach for a pooled, serverless-friendly database (Neon, Atlas) and connection limits sooner than you expect. Path 3 (a long-running Node host) sidesteps most of this.

The learning curve is real. Everything is config-as-code: you model collections, fields, access control, and hooks in TypeScript. That is powerful and versionable, and it is more upfront work than clicking fields together in a hosted CMS.

If you want the whole app scaffolded, this is the wrong layer. Payload assumes you are a developer assembling an app. If your goal is to go from a prompt to a deployed SaaS with auth, payments, database, and an admin already wired together, you want a different tool. An AI app builder like Totalum (https://www.totalum.app) generates a full Next.js app on that stack (it ships on BetterAuth with an included data admin panel), which is a faster on-ramp for non-developers. The trade is real and worth stating plainly: you give up Payload's deep, code-first content modeling and its MIT ownership story for the builder's more opinionated output. Different layer, different buyer.

When to pick something else

Honest curation means telling you when to walk past the specimen. Here is who each option genuinely serves.

If your project is content-heavy and developer-owned, the specimen you want is Payload. If you are earlier and want more assembled for you, look one row down. We reviewed one of those adjacent backends recently in our Convex reactive-backend review, and Payload sits in the same shelf of our open-source Next.js starter scorecard.

Verdict

Payload earns its 43.4k stars. In July 2026 it is the most natural backend for a team that lives in Next.js and wants to own its content layer as code, with no per-seat CMS tax and a genuinely good admin panel. It loses only when you ask it to be something it never claimed to be: a finished SaaS in a box. Buy the backbone, know you are building the body.

Your move: if you already have a Next.js app and keep hand-rolling a content model, scaffold Payload on Path 1 this week, wire a Postgres adapter, and see how it feels before you commit a schema.

FAQ

Is Payload CMS free?
The framework is free and open-source under the MIT license, so self-hosting costs you nothing beyond your own compute and database. Payload Cloud, the maintainer's managed hosting, is a separate paid product.

Does Payload CMS work with the Next.js App Router?
Yes. Payload 3.x is Next.js-native and runs inside your app's /app folder, with its admin panel and APIs sharing the same Next.js runtime.

Which databases does Payload support?
Three official adapters as of 2026: MongoDB with Mongoose, PostgreSQL with Drizzle, and SQLite with Drizzle.

Is Payload a good SaaS starter?
It is a backend and CMS layer, not a full SaaS starter. It gives you data modeling and an admin panel, but you still build billing, pricing pages, and end-user auth flows yourself.

Can you deploy Payload on Vercel?
Yes, but plan for serverless database connection limits. A pooled, serverless-friendly database helps, and a long-running Node host (Railway, Fly, a VPS) avoids most of the friction.

How many GitHub stars does Payload have?
43.4k stars as of July 2026, on version 3.85.2, per its GitHub repository.

Payload or Strapi?
Choose Payload for a code-first backend that lives inside your Next.js repo. Choose Strapi if you want a longer-established, standalone CMS with a larger plugin ecosystem and do not mind running it as a separate service.