What is Payload CMS in October 2026?
Payload is an open source headless CMS and application framework written in TypeScript. It installs inside a Next.js app, so the admin panel, the API and your front end can live in one repository and deploy as one unit. The licence is MIT, which means no seat fees and no vendor lock on the code. Payload joined Figma in June 2025 and remains open source. That changes who owns the roadmap, not what you can run.
You choose the database (Postgres, MongoDB or SQLite through adapters) and the host. Payload Cloud exists, but as of October 2026 project creation there is Enterprise only, so most teams self host on a VPS, a container platform or Vercel. Plan for that hosting work before you pick Payload. Our list of free headless CMS platforms shows what the licence leaves you paying for: servers, backups and engineering time.
Who Payload suits, and who should pick something else
Payload fits a team that writes TypeScript and treats the content model as application code. Collections, fields, hooks and access rules are defined in config files, reviewed in pull requests and typed end to end. It also fits products where the CMS is half the app: a portal, a B2B SaaS site with gated pages, a multi-tenant setup.
Look elsewhere in three cases:
- Editors need a drag and drop visual page editor out of the box. Storyblok or Prismic get there faster.
- Nobody on the team wants to run a database and a server. A hosted platform such as Sanity or Contentful removes that job.
- You already have a Node team deep in Strapi plugins. Strapi vs Payload lays out when a move is worth it.
If you are choosing between self hosted and hosted, Payload vs Sanity covers where the content lives and who runs it.
What we build with Payload
Marketing sites and blogs. Pages assembled from typed blocks, drafts and version history, live preview inside the admin, scheduled publishing, and a Next.js front end that revalidates on publish.
Gated and multi-tenant products. Access control in Payload is a function you write per collection and per field. That is how we build member areas, client portals and one admin serving several brands. Our comparison of access control across CMS platforms shows how unusual that depth is.
Custom admin and back office tools. Because the admin is React, we replace fields, views and dashboards with our own components instead of working around the product.
Background work. The jobs queue handles imports, search indexing and scheduled tasks, so you do not need a second service for them.
Proof from our projects
Payload is the platform behind most of the shipped work on our headless CMS agency page. In a Payload build for a European mid-market B2B SaaS, editors stopped waiting on engineering, and time to publish fell by roughly two thirds, with LCP on the main landing page down from 4.2s to 1.7s. A replatform for a US-based Series-B fintech moved the marketing site off WordPress and cut publish time by about two thirds.
Migrating into Payload
Most Payload projects start with a WordPress, Drupal or custom CMS. We map the old types to collections, write repeatable import scripts that run against staging, move media to object storage and carry every URL over with redirects. Rich text converts into Payload’s Lexical format, which is where most cleanup time goes. The general process is in our WordPress to headless CMS migration page and the CMS migration checklist.
What does Payload cost to own?
The licence costs nothing, so the bill is made of hosting, a managed Postgres or MongoDB, object storage for media, backups, and the engineering time to upgrade. Payload ships major versions, and config level changes land in your code, so someone has to own upgrades. Teams with no such person should budget for a support retainer or choose a hosted platform. Build cost depends on the number of collections, custom admin views, access rules, locales and how much content moves in. We scope it after a short audit and bill fixed price for migrations or time and material at the $50 to $150 per hour band.
How an engagement runs
Week one is a content audit and a schema document your editors sign off. Then we build the collections and hooks in git, deploy staging with CI, and show editors real content early. Launch follows a content freeze, a final import and a redirect check in Search Console.
Typical stack around Payload
| Layer | Usual choice |
|---|---|
| Front end | Next.js in the same repo, or Astro reading the API |
| Database | Postgres through the Drizzle adapter |
| Media | S3 compatible storage |
| Hosting | Container on a VPS or a managed platform, with CI deploys |
| Search | Algolia, Meilisearch or Postgres full text |
Our Next.js team owns the front end, and you can hire a Payload developer for a team that already has a project. For the wider picture see our headless CMS hub.
