Payload review

Payload is an open-source, code-first framework for building content-rich applications. You define the data schema in code, and Payload generates a backend and admin panel from it. It runs natively in Next.js, so teams can build the backend into a Next.js app rather than treating the CMS as a separate product. The stated use cases include headless CMS, eCommerce, enterprise applications, and digital asset management.

For content teams, Payload offers visual editing to preview and change how content looks. It also describes its content as ready for retrieval-augmented generation (RAG) and vector embeddings. That makes it a framework for teams building their own content system, not simply a hosted editor to configure without development. You can host it yourself for free, or pay for Payload Cloud, which starts at $35 per month according to the published pricing information.

The main value is control over the data model and deployment. Code-defined schemas generate the backend, while the Next.js integration can keep the CMS and application in one project. A commenter on r/nextjs says this setup can avoid a separate deployment and points to Payload’s Local API as a reason it works well for their project. That is one user’s experience, not a guarantee that every architecture will be simpler.

Self-hosting is the price advantage: the open-source plan is $0 per month, with no user or seat caps, API-call quotas, or usage limits beyond the infrastructure you provide. Payload Cloud’s Standard plan is $35 per month and lists 512 MB RAM, 3 GB database storage, 30 GB file storage, and 50 million serverless RPUs. Pro costs $199 per month and includes a dedicated M10 Atlas cluster, 30 GB database storage, 150 GB file storage, 100 GB monthly bandwidth, and 1 GB RAM, 1 vCPU, and two instances.

Reddit users describe using Payload for projects from websites to eCommerce and internal software. Those comments suggest flexibility, but they are not independent validation of every use case.

Payload’s flexibility comes with a development burden: schemas are defined in code, and the product is built around Next.js. That suits developer-led teams better than marketers looking for a standalone, no-code CMS. The published materials do not specify whether visual editing removes the need for development work.

Cloud plans also have concrete ceilings. Standard includes 512 MB RAM, 3 GB database storage, 30 GB file storage, and 50 million serverless RPUs. Pro raises those allowances, but still lists 30 GB database storage, 150 GB file storage, 100 GB bandwidth per month, and two instances. Standard and Pro overages are listed at $0.50 per GB of database storage, $0.20 per GB of monthly bandwidth, and $0.02 per GB of file storage. Annual Cloud prices are not published; Enterprise pricing is also not published, though its plan lists custom infrastructure and a 99.9% uptime SLA.

There is a separate roadmap question. A Reddit thread following Figma’s acquisition of Payload raised concerns about future priorities and vendor lock-in. Other commenters were comfortable continuing to use it. The long-term direction remains uncertain in the discussion.

Payload’s self-hosted open-source version costs $0 per month, with no user or seat caps, API-call quotas or usage limits beyond your own infrastructure. Payload Cloud starts at $35 per month for Standard, which includes 512MB RAM, 3GB database storage, 30GB file storage and 50M serverless RPUs, according to the published pricing details.

Pro is $199 per month: a $164 monthly jump from Standard. It adds a dedicated M10 Atlas cluster, 1GB RAM, 1 vCPU, two instances, 30GB database storage, 150GB file storage and 100GB monthly bandwidth. 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.

Enterprise pricing is custom, with unlimited database and file storage, bandwidth and custom domains listed. Cloud annual prices are not published, and no free-trial terms are provided. Budget for infrastructure if self-hosting; on Cloud, watch storage and bandwidth overages.

Moving to Payload is likely to take developer time: it is code-first, uses code-defined schemas and is built natively into Next.js. That makes it a better fit for teams able to rebuild or adapt their application than for marketers expecting a no-code migration. Plan to map your existing content model to Payload’s schemas and check how your current app handles editing and delivery. The published material does not document import, export or migration tooling, so confirm those details before committing.

Self-hosting gives you control over the hosting environment, but does not remove the work of moving application code and content if you later leave. Cloud adds a hosting dependency; the published material does not specify a one-click exit or data-export process. We also have no Reddit posts or comments in the published sources, so we can’t responsibly say what users report as reasons for leaving. The stated trade-offs are cloud resource caps and roadmap uncertainty; verify current limits and your exit path with Payload before switching.