Payload is an open-source, MIT-licensed headless CMS and fullstack framework, written in TypeScript and built to run natively inside a Next.js /app folder, aimed at developers who want a TypeScript backend and admin panel without signing up for another SaaS.

What it is

Payload is a headless CMS that doubles as an application framework. It installs directly into an existing /app folder in a Next.js project, making it a Next.js native CMS rather than a separate service that has to be deployed, wired up, and kept in sync with a front end. The backend and the admin panel are both fully TypeScript, with automatic types generated for your data, and the admin UI is a customizable React application. The project is licensed under MIT and lives in the JavaScript and TypeScript ecosystem, with topics covering cms, headless-cms, jamstack, nextjs, express, graphql, and mongodb.

The concrete problem it solves is duplication and lock-in. Instead of running a hosted CMS in one place and a front end in another, Payload lets a team combine front and back end in the same /app folder, query the database directly in React Server Components without going through REST or GraphQL, and deploy anywhere, including serverless targets. It replaces the pattern of subscribing to yet another SaaS CMS, and the README positions it against traditional content management systems by stating that developers never need to touch legacy WP code again.

Key capabilities

• Next.js native: installs inside your own /app folder and lets server components extend the Payload UI.
• Direct database queries from React Server Components, so REST and GraphQL endpoints are not required for reads.
• Fully TypeScript, with automatic types generated for your data.
• Authentication out of the box, with HTTP-only cookies and CSRF protection.
• Versions and drafts, plus localization for multi-locale content.
• Block-based layout builder, a Lexical rich text editor, and conditional field logic.
• Granular access control, with document- and field-level hooks for every action Payload provides.

Who uses it and how

• Next.js teams building websites, ecommerce stores, blogs, or portfolios from production-ready templates, which ship with React Server Components and Tailwind front ends.
• Serverless teams deploying one-click on Vercel with a Next.js front end, a Neon database, and Vercel Blob for media storage.
• Cloudflare teams deploying one-click with Workers, R2 for uploads, and D1 as a globally replicated database.
• Application developers who want the front end and the backend in a single /app folder rather than two projects.
• Template authors who publish reusable starter kits under the payload-template topic for community discovery.

Getting started

Scaffold a project with pnpx create-payload-app@latest; new users are directed to the website template via pnpx create-payload-app@latest -t website. One-click deploy options are also provided for Vercel and Cloudflare.

How it compares

No list of paid products being replaced is provided in the facts, so the nearest named comparison is WordPress, which the README contrasts by promising that developers never touch legacy WP code again, and the broader category of regular CMS products. Among the tools named in the facts, Payload is distinctive because it is both the CMS and the application framework, sitting alongside the Express, GraphQL, MongoDB, and Next.js pieces that its topics reference rather than replacing them with a hosted service.

When to use it — and when not to

Choose Payload when the team writes Next.js and TypeScript and wants the content backend, admin panel, and front end in one repository, accepting responsibility for the database and file storage that your chosen deploy target provides, such as MongoDB, Neon, D1, R2, or Vercel Blob. A self-hoster must operate that database and storage layer, and the project currently carries over a thousand open issues, so teams wanting a fully managed, zero-ops CMS should not pick it. Developers without Next.js experience will also face a real learning curve, because the CMS assumes it lives inside a Next.js application.

pnpx create-payload-app@latest

npx create-payload-app --example example_name