Payload review

Payload is an open-source framework for building content-rich applications, not just a hosted content API. Its code-defined schemas generate a backend and admin panel, and the framework is designed to run natively inside a Next.js app. That puts it in the application stack alongside the frontend and server code, rather than requiring a separate CMS deployment by default.

The framework targets headless CMS projects, eCommerce, enterprise applications and digital asset management. Its feature set also includes visual editing and content prepared for RAG and vector embeddings. Teams can run the open-source framework on their own infrastructure or use Payload Cloud, which has paid monthly plans. That gives developers control over deployment while letting marketers work through a generated admin interface. The main architectural trade-off is the close Next.js fit: it suits teams standardizing on that stack better than teams seeking a framework-neutral CMS.

The homepage's setup command is npx create-payload-app. Payload describes itself as fully typed and Next.js native: define the schema in code, then use the generated backend and admin panel in the app. The integration surface the homepage emphasizes is this schema-driven backend, the Next.js app and visual editing. A Reddit commenter also describes Payload's Local API as a way to access content within the same deployment.

The homepage does not name supported languages, SDK packages, REST or GraphQL endpoints, webhooks, or a plugin catalog. Before committing, confirm SDK and language support, API protocols, authentication options and integration details in Payload's documentation. That matters if other services need to read or write content, or if your team wants to keep the CMS separate from the frontend. The available setup command is clear; the API contract for a particular integration still needs checking.

Self-hosted Payload is listed as free under the open-source MIT option, with no user or seat caps, API call quotas or usage limits beyond your infrastructure. Your costs are therefore hosting and operations. Payload Cloud's Standard plan is $35 per month and lists 512MB RAM, 3GB database storage, 30GB file storage and 50M serverless RPUs.

Pro costs $199 per month and lists a dedicated M10 Atlas cluster, 30GB database storage, 150GB file storage, 100GB monthly bandwidth, 1GB RAM, 1 vCPU and 2 instances. Standard and Pro overages are listed at $0.50 per GB of database storage, $0.20 per GB of bandwidth per month and $0.02 per GB of file storage. The pricing lists no annual Cloud rates. Enterprise pricing is not published; the listed plan includes custom infrastructure and a 99.9% uptime SLA. Ask how RPUs are billed beyond the Standard allocation and what your expected usage will cost.

The self-hosted framework is listed as open source under the MIT license, and Payload says it is intended for projects from freelance work to enterprise needs. Self-hosting avoids a required Payload Cloud subscription, but teams still own infrastructure, updates and operations. One Reddit commenter notes that the JavaScript code can be forked; that is a potential fallback, not a guarantee of ongoing maintenance.

Payload's homepage does not publish a data-export format or migration procedure. Confirm how to export content, files and relationships before you depend on the platform, and test that process as schemas change. Payload's Next.js integration can reduce deployment boundaries for teams already using that stack, but it can also raise switching costs for teams that later move away from it. A Reddit thread raised concerns about future vendor direction and lock-in; those are user concerns, not confirmation of a change to the license or roadmap.

Production sizing depends on whether you self-host or use Payload Cloud. Standard lists 512MB RAM, 3GB database storage, 30GB file storage and 50M serverless RPUs; Pro lists 1GB RAM, 1 vCPU, 2 instances and 100GB monthly bandwidth. The listed storage and bandwidth overages can add to the bill. Enterprise is the only listed plan with a 99.9% uptime SLA. Confirm expected traffic, resource scaling, backups and incident support with Payload before choosing a plan.

The homepage does not publish security certifications or compliance details, so ask for the documentation relevant to your deployment. Production teams should also plan schema migrations as content models evolve. One Reddit post describes localization setup as “a giant pita” for a project with multiple languages and flexible pages, while a commenter notes that changing SQL schemas can require migrations. Those reports point to work to budget for, not a universal outcome.