Payload

Payload is an open-source content management system (CMS) and application framework built with TypeScript. It is headless, meaning it manages and serves content through an API rather than rendering a fixed front end of its own — so a developer can consume the content in any site or app they build. What sets Payload apart is that it is code-first and installs directly into a Next.js project's app folder, so the backend and admin panel live in the same codebase and deployment as the front end, with no separate service to run. You define your content models as TypeScript, and Payload generates a REST API, a GraphQL API, and a React-based admin panel for non-technical editors to manage content. It is MIT-licensed and self-hosted, so the core is free and lives in your own codebase like any other part of the application.

The point of a headless, code-first CMS like Payload is control and integration. Because content models are defined in code, they live in version control alongside the rest of the application, change through the same review process, and give developers a fully typed backend rather than a settings screen. Because it installs into Next.js, there is no separate backend to host and keep in sync — same repo, same deploy. Editors still get a friendly admin panel to write and organize content, while developers get typed APIs to pull that content into whatever they are building. Teams use Payload as a headless CMS for websites and as the backend for larger applications, including commerce and digital-asset management, precisely because it combines an editor-friendly interface with a developer-friendly, code-defined core.

Payload belongs to the headless-CMS category alongside tools like Strapi, Sanity, Contentful, and others, and the useful distinctions are hosting model and how content is defined. Some headless CMSs are software-as-a-service — hosted by the vendor, configured through a web dashboard, priced per seat or per API call. Payload takes a different stance: it is open-source, self-hosted, MIT-licensed, and code-first, so you run it yourself, define content in TypeScript, and are not metered on usage or seats. Its tightest distinction is its Next.js-native design — it installs into your Next.js app rather than running as a separate backend, which appeals to teams already building on that stack. Against a SaaS CMS you trade managed hosting for control and no usage limits; against another self-hosted CMS the pull is the code-first, TypeScript, Next.js-integrated approach.

Placing Payload accurately also means not confusing it with the systems around it. Payload is a CMS and application framework, not a general-purpose database — it needs a database underneath it (it supports stores such as MongoDB and PostgreSQL) to persist the content it manages. It is also not a front-end framework in itself; it works with Next.js and React to deliver an admin experience and APIs, while you build the visitor-facing site. So in a real stack, Payload is the content and backend layer, a database sits below it, and a Next.js front end sits alongside it. Choosing Payload is choosing a self-hosted, code-first content backend that integrates tightly with a modern React and Next.js front end, rather than a hosted dashboard you configure and pay per seat to use.

Payload fits well when a team is already building on Next.js and TypeScript and wants its content models to live in code, under version control, with typed APIs and no separate backend to operate. Define content structures deliberately, since they are code and will evolve through pull requests like any other schema. Lean on the generated REST and GraphQL APIs to pull content into the front end, and give editors the admin panel so non-technical users can manage content without touching code. Because Payload is self-hosted, plan for the operational side — hosting, the database it depends on, backups, and updates — that a SaaS CMS would otherwise handle for you. Used this way, Payload gives developers a typed, code-first backend and editors a usable interface in one integrated stack.

The failures are mostly mismatches of fit and neglected operations. Choosing a self-hosted, code-first CMS when a team wanted a zero-ops hosted dashboard leads to friction, because someone must run and maintain Payload and its database. Ignoring the operational burden of self-hosting — updates, scaling, backups — turns a free core into a hidden cost. Confusing Payload with the database beneath it, or expecting it to render the front end by itself, misunderstands its role as the headless content and backend layer. The discipline is to adopt Payload for what it is — an open-source, TypeScript, Next.js-native headless CMS that trades managed hosting for control and code-first modeling — and to own the self-hosting responsibilities that come with that trade.

Payload is an open-source, TypeScript-based headless CMS and application framework that installs into Next.js and serves content over REST and GraphQL APIs, distinct from hosted SaaS content platforms.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where payload is a core concern: