ENATIV Logo
ENATIV
Back
© 2026 ENATIV
ProjectsServicesKnowledge hubContact
contact@enativ.pl
  1. Knowledge hub
  2. ›
  3. CMS & content
  4. ›
  5. Payload CMS

Payload CMS

An open-source TypeScript headless CMS with an editor panel generated from config in code.

CMS & contentUsing since 2023 · Featured project: Budzowska Fiutowski i Partnerzy

Category
CMS & content
Using since
2023
Featured project
Budzowska Fiutowski i Partnerzy

In practice

I pick Payload CMS most often when editors need their own panel and the whole system should live in one repository with the site code. At Budzowska Fiutowski i Partnerzy the law firm edits its content itself, with no developer, and Next.js reads it from the same config.

What is Payload CMS?

Payload CMS is an open-source headless CMS written in TypeScript. You describe collections and fields in a config file, and Payload generates an admin panel and the APIs from it. Authentication and access rules come built in.

It runs as part of a Next.js app, so the panel and the site can share a repository and one deployment. Data lives in the database you choose, connected through an adapter.

License
MIT
Language
TypeScript
Databases
PostgreSQL, MongoDB, SQLite
Schema
Configuration in code

How I work with Payload CMS

I start with the editor, not the site's look. First I settle who edits what, because collections, blocks and permissions follow from it.

  1. Collections and blocks

    I describe collections and custom content blocks in the config, so an editor builds a page from ready pieces and stays inside the layout.

  2. Content migration

    When a site moves off an old system, I carry the content and images into Payload and make sure the URLs stay the same.

  3. Site and deployment

    I build the site in Next.js, keep data in PostgreSQL and run everything in Docker on a VPS.

When it fits, and when it doesn't

Payload makes sense where the CMS is part of the project, not a separate tool.

A good fit when

  • A company site where editors manage all content themselves.
  • A bilingual site with custom content blocks.
  • An application with bookings or invoices where the CMS is one module.
  • A migration off an old system that keeps the URLs.

Not a fit when

  • A brochure site with a few pages that someone edits once a year.
  • A team where nobody will maintain config in code.
  • Editors who are meant to design new content types in the panel.
  • A MySQL or MariaDB database that cannot be changed.

In those cases I look at Strapi, and for a simple site at WordPress too.

Payload or Strapi?

Both are headless CMSs with their own panel. They differ in where the content model is born and what they pair with in a project.

Payload CMS and Strapi compared
CriterionPayload CMSStrapi
Data modelCollections and fields in configContent-type Builder in the panel, local
DatabasesPostgreSQL, MongoDB, SQLitePostgreSQL, MySQL, MariaDB, SQLite
APIREST and GraphQL from configREST by default, GraphQL as a plugin
PermissionsAccess rules in code, per fieldBuilt-in roles set in the panel
Editor panelGenerated from field configReady-made, extended with plugins

Choose Payload when

the schema should live in the repository and go through code review, and the CMS should run in the same app as a Next.js site. You get control of the model, but a developer makes the changes.

Choose Strapi when

you need a MySQL or MariaDB database or your team already knows Strapi. Modelling in the panel is handy early on, just remember it works only locally.

On Kuma.de I used Strapi with custom roles and permissions, and on Budzowska Fiutowski i Partnerzy Payload CMS 3 with custom content blocks.

Pitfalls from real projects

Old HTML in the new editor

From the Budzowska Fiutowski i Partnerzy project

At Budzowska Fiutowski i Partnerzy the biggest challenge was moving content and images from an old MariaDB database into Payload CMS. Legacy HTML had to become Lexical rich text, without losing the existing URLs and their SEO value.

Frequently asked questions

The core is free: the code is MIT-licensed and runs on your own server. You pay for hosting, the database and the work on the site, so the cost follows the project scope, not the number of editors.
Payload is part of a Next.js app, so it runs wherever you deploy the site, on a VPS or in a cloud. The data sits in your own database. At Budzowska Fiutowski i Partnerzy I deployed it in Docker on a VPS through Coolify.
Yes, because the panel shows only the fields I defined in the config. At The Travelling Cows the agency manages trips and content itself, and at the law firm editors change everything from team profiles to practice descriptions.
It can. First I settle what has to carry over, the content with its images and the URLs, then I estimate the work. Where the data comes from matters less than how clean it is. I write more about the older platform in the WordPress entry.

On this page

  • In practice
  • What is Payload CMS?
  • How I work with Payload CMS
  • When it fits, and when it doesn't
  • Payload or Strapi?
  • Pitfalls from real projects
  • Frequently asked questions

Related topics

  • Payload CMS
  • Next.js
  • Strapi
  • WordPress
  • PostgreSQL
  • Medusa.js
  • Docker

Related services

  • Web ApplicationsModern, fast and scalable web applications using React and Next.js.
  • E-CommerceHeadless Shopify, Medusa.js, and custom storefronts with Stripe.

Planning a site with an editor panel?

Tell me who will edit the content and where it has to come from. I'll say plainly whether Payload fits, or whether Strapi or a simpler tool is the better pick.

Describe your projectSee Budzowska Fiutowski i Partnerzy