Screenshots
The Story
Payload is a content management system that installs into an existing application rather than running beside it. Instead of a separate admin service reached over an API, Payload mounts its admin panel and its API inside a Next.js or Express application, sharing the same database and the same deployment.
The configuration is code. Collections, fields, access control, and hooks are declared in TypeScript files, which means the content model is versioned with the application and can be type-checked. The generated admin panel reflects that configuration.
Because it mounts into the application, the deployment story is the application's deployment story. There is no second service to host, and the database is the one the application already uses. The source is published, and the product can be self-hosted, which is the norm for this category.
Overview
Payload's design choice is that the CMS should be part of the application, not a service next to it.
Collections, fields, access rules, and lifecycle hooks are declared in TypeScript configuration files. The content model therefore lives in the repository, is reviewed like code, and can be type-checked.
The admin panel is generated from that configuration and mounted inside the application. There is no separate admin service to deploy, and the panel shares the application's authentication and database connection.
Because the CMS runs inside the app, deployment is the app's deployment. A team already running Next.js or Express adds Payload rather than adding a service, which removes a network hop and a second set of credentials.
Key Features
- Content model in code
Collections and fields are TypeScript configuration, versioned with the application.
- Admin panel in-app
The admin UI mounts inside the application rather than running as a separate service.
- Access control as functions
Read and write rules are functions that run against the request, not a separate permission UI.
- Open-source core
The source is published in a public repository with a license file.
Where Payload is a strong choice, and where it is not
Choose Payload if you are building a TypeScript application and want content management inside it, with the model declared in code and reviewed like the rest of the repository.
Look elsewhere if you want a hosted CMS with a visual model builder and no deployment of your own, or if your team does not work in TypeScript.
Getting started
A local install is quick; the decision that takes time is how to model your content.
- ~15 minTime to first document
Scaffold a project, start the dev server, and the admin panel is at a known route.
- FreeCost to start
Self-hosted and free. The paid cloud plan removes the hosting work.
- Node + a databasePrerequisites
Node.js and MongoDB or Postgres. A template scaffolds the rest.
Known limitations
Constraints confirmed from the project's documentation.
- You own the deployment. Upgrades, backups, and the database are your responsibility unless you pay for cloud.
- Code-first configuration. Collections and fields are defined in TypeScript, which is a strength for developers and a barrier for a non-technical editor.
- Smaller plugin ecosystem than the established CMS platforms, so an unusual requirement may mean writing the integration yourself.
- MongoDB is the default even though Postgres is supported, so the two paths are not equally mature.
Pick Payload if you want the CMS to live inside your application
It installs into an existing Next.js app rather than running beside it, which removes the separate service and the API glue between them.
The differentiator is locality: the admin panel, the content model, and the application share a codebase and a deployment. For a developer-led team that is a significant simplification.
If a non-technical team needs to configure the content model through a UI, or you want a large plugin marketplace, a conventional headless CMS is the better fit.
FAQ
What is Payload?
Payload is an open-source headless CMS and application framework that installs into a TypeScript application, mounting its admin panel and API in-app.
Is Payload open source?
Yes. The source is published in a public repository with a license file. Check the repository for current license terms.
Does Payload need a separate server?
No. Payload mounts inside an existing Next.js or Express application, so it shares the application's deployment and database.
Is Payload free?
Payload lists a free open-source tier alongside a paid cloud offering. Check the pricing page for current terms.
What stack is Payload built with?
CompassPad records Payload as a TypeScript and React application that runs on Node.js with PostgreSQL or MongoDB storage, based on the public repository.
What we checked
- LIVESite and primary link
The marketing site resolved and the primary product link reached the product itself.
- PRICINGPricing page
The pricing page resolved and lists the current plans and limits.
- DOCSDocumentation
Public documentation resolved and covers the product's core surfaces.
- SOURCESource page
The linked source page resolved and is reachable without an account.
Discussion
No comments yet. Be the first.
Join the conversation. Sign up to comment.
Sign up free