A Payload CMS alternative for a managed website without a custom CMS build

Why people look for a Payload CMS alternative in 2026

Payload has a strong claim to being the best content backend a Next.js team can adopt. You declare a collection in TypeScript, and the framework produces the database schema, a typed client, REST and GraphQL endpoints, authentication, field-level access control, lifecycle hooks, drafts, versions and localisation. It is MIT licensed and it runs inside your own application rather than behind somebody else's API. Teams that pick it rarely regret the engineering. They come looking for an alternative for a different reason: the shape of the daily work after launch.

The content model is a file, so content work is engineering work

Because collections and fields live in payload.config.ts, the schema is under version control. That is a genuine advantage for review, history and consistency across environments. It also means a request as small as adding a subtitle to a landing page collection travels the full path of a code change: edit the config, run a migration on Postgres or SQLite, regenerate types, raise a pull request, get a review and deploy. A marketing team that files five of those a month is not asking for much. They are still spending an engineer's week to get it.

Nothing renders until someone writes the front end

Headless is the point of the product, and it has a cost that shows up on day one. Install Payload and you have an admin panel and an API. There is no theme, no homepage, no blog index and nothing for a visitor to load. The official website template and the one-click Vercel deploy shorten the distance, and what they produce is a starter you then design and build. Before any of that, the documented requirements are Node.js 20.9.0 or newer, a JavaScript package manager with pnpm preferred and yarn 1.x unsupported, one of MongoDB, Postgres or SQLite, and a Next.js version inside a narrow supported band, with an explicit warning that not all Next.js 15 and 16 releases are compatible.

No published price, and no managed path for new projects

Checked on 11 September 2026, payloadcms.com carries no dollar figure on any live page. The self-hosted card says free forever, the instant-deploy cards hand you to Vercel, Neon or Cloudflare, and Enterprise is a Get a Demo form. Figures circulating on third-party aggregator sites for the old Payload Cloud tiers appear on no live Payload page, so this comparison does not repeat them. Payload joined Figma, announced on the Figma blog on 17 June 2025 at Config 2025, and the open-source project has kept shipping, with v3.89.0 released on 10 September 2026. The managed product moved the other way: the live Cloud page says deployment of new projects is currently paused, existing projects continue running as normal, and the FAQ answers the migration question with 'Yes, eventually.' The Enterprise card still offers self-hosted or with Payload, which sits awkwardly beside that, so treat Payload-run infrastructure as unsettled rather than available.

How Grigora compares

Grigora takes the opposite position on every one of those trade-offs. The content model is edited in a dashboard, so a new field is a dropdown and a save rather than a commit and a release. The site exists before anyone opens an editor, because the AI generates a first draft from a description of the business and there are website templates underneath it. Hosting, SSL, CDN and backups are included and there is no runtime for you to keep current, so the supported Next.js version band and the Node upgrade schedule stop being your problem.

One subscription instead of four invoices and a sprint

Starter is $12 a month billed annually. That covers the website and its hosting, the CMS with posts, categories, author profiles, directories and moderated comments, a newsletter with 2,500 subscribers and a campaign builder with automations and segmentation, and a store with a catalogue, variants, stock and digital downloads at 0% platform commission through Stripe or Razorpay. SEO ships as part of the product: metadata, schema controls, sitemaps and IndexNow submission, alongside free SEO tools on the marketing site. On Payload, the CMS is the product and each of those other things is either a plugin that stops at the API, an external service to integrate, or software somebody writes. Pro is $20 a month for two sites and 7,500 subscribers, and Business is $45 a month for five sites and 25,000 subscribers. Professional mailboxes start at $5 each, and White Label is a separate plan at $199 a month for agencies reselling under their own brand.

Where Payload CMS still wins, and it wins clearly

Two places. The first is the content model. If you need twenty related collections with typed fields, hooks on every lifecycle event, access rules evaluated per field and per document, localisation across languages and a generated GraphQL API over all of it, Payload does that and Grigora does not come close. The second is ownership. MIT licence, your repository, your MongoDB or Postgres instance, no per-seat or per-page fee, and nobody able to change the terms on content you already published. Add to that an admin panel built from React components you can replace outright, which is why agencies reach for it when a client needs an editing interface in the client's own vocabulary. Weigh those honestly. If either one is the requirement that decides the project, stay on Payload. If the requirement is that the person who wants a new field can add it themselves this morning, that is what Grigora is built around.