Running Payload CMS?

Payload CMS collections or access control giving you grief? We sort it out.

Payload is a developer's CMS: TypeScript config, your own database, no magic admin panel built in a different stack. That is why engineers like it and why editors sometimes find it hard to trust. We make the admin usable, the access rules provable, and the hosting something that will not fall over on a Monday morning.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

payload.log

still failing

What it is

Payload CMS at a glance

Payload CMS is a headless content management system where the schema, access control and admin UI are all configured in TypeScript rather than clicked together in a dashboard. It was founded in 2018, went open source in 2019, and the company was acquired by Figma in 2025 while the project remains MIT licensed.

The admin UI is a React application generated from your config, the API comes as REST and GraphQL for free, and the storage layer supports both MongoDB and relational databases through drizzle based adapters for Postgres and SQLite. Version 3 was a significant rewrite targeting Next.js App Router, which means Payload can run in the same Node server as your frontend. It is typically chosen by teams who want to own their content layer end to end rather than send it to a SaaS CMS.

Type
Code first headless CMS and admin framework
First released
2019 public beta, 1.0 in 2021, 3.0 in 2024
License
MIT, open source
Maintained by
Payload CMS, Inc., now part of Figma
Typically used for
Headless content for marketing sites, SaaS back offices, multi tenant admin panels, Next.js backed products

The honest version

Payload CMS pros and cons

No technology is all upside. This is where Payload CMS earns its place and where it tends to cause trouble.

Where Payload CMS is strong

  • Config is codeCollections, fields, hooks and access control live in TypeScript files in your repo, which means code review, version history and tests cover the content model like any other code.
  • The admin UI is includedA production grade React admin is generated from your schema without hand building forms, which saves weeks compared with wiring Headless UI from scratch.
  • You own the databasePostgres, SQLite or MongoDB, hosted wherever you prefer, with migrations you can inspect. No vendor lock in on the data layer.
  • Access control is per fieldRead, create, update and delete rules can be defined at document and field level, which is far more precise than most SaaS CMSes allow.
  • Next.js App Router integrationPayload 3 runs inside a Next.js app, so API routes, authentication and the admin share a single deployment, which simplifies hosting a lot.
  • Reasonable upgrade storyMigration guides are written, not inferred, and major version jumps come with scripts to help, which is unusual quality in this corner of the CMS market.

Where Payload CMS bites

  • Editors need trainingThe admin is good but it is still built for engineers first. Content teams coming from WordPress or Webflow will need a short on ramp and some custom components to feel at home.
  • You host it yourselfPayload Cloud exists, but most deployments are on your own infrastructure. That means Node runtimes, backups, scaling and TLS are your problem rather than someone else's.
  • The admin bundle can get largeRich text editors, media libraries and many collections produce a JavaScript bundle that is slow on cold start, particularly on serverless where cold functions are not forgiving.
  • Migrations need disciplineSchema changes are TypeScript changes, and the migration tooling helps but is not magic. Multi tenant and legacy data shapes still need careful thought before deploy.
  • Smaller community than Strapi or WordPressPlugins, themes and tutorials exist but the pool is narrower, so answers for less common problems sometimes require reading source.
  • Access control is powerful and easy to get wrongField level rules, document level rules and collection level rules compose in ways that need tests, otherwise an editor role quietly gains access to something they should not have.

Sound familiar?

Common Payload CMS problems we fix

The Payload CMS problems that bring people to us, and what you have once each one is fixed.

You must define a secret in payload.config.ts

Server will not start after deploy

Environment variables missing in the production environment, a secret rotated in the dashboard but never pushed to the Node process, or a cold start that loaded config before the env was ready.

Boot reliable across environments

Access denied. You are not allowed to perform this action

Editors cannot do what the brief said they could

Access rules written for admin only during development, never widened for editor roles, or a field level rule that quietly overrides the document level allow.

Access matches the actual roles

migration pending: 2026_11_add_tenant_id

Migrations stuck or failing in production

A migration that worked on a fresh development database fails on production data because of an inferred type mismatch, a column already added by hand, or a timeout on a large table.

Migrations run clean on live data

admin bundle: 8.4 MB

Admin UI is painfully slow

A rich set of field types, several media libraries and a long list of collections producing a large admin bundle that stutters on the first paint, especially over slow connections.

Admin fast and usable again

MongooseError: buffering timed out after 10000ms

Database connection flakiness

A serverless deploy that is opening a new Mongo connection every request, or a Postgres pool that is sized wrong for the environment, producing intermittent timeouts.

Database connections stable

slug must be unique, but another document has this value

Duplicate slugs crash publishing

A content import or a localisation workflow that creates documents sharing a slug across locales, hitting the unique constraint in a way the admin does not help with.

Slugs resolved per locale

sharp: Input file is missing

Uploads failing on image processing

A sharp installation that works locally and not on the host, or an S3 adapter that uploads before processing finishes, leaving the admin with a broken thumbnail.

Image pipeline reliable in production

no owner

Payload project inherited from a previous team

A production Payload instance with a half documented schema, custom hooks nobody has read, and an admin that nobody dares to upgrade in case something breaks.

Project owned and documented by your team

What we do

Payload CMS help, from rescue to ongoing support

Debug one access rule, or let us run the whole Payload stack.

Rescue
A Payload instance that will not deploy, an admin that keeps crashing or a migration that is stuck. We stabilise it first and write up what happened second.
Schema and access design
Collections, fields, access rules and hooks designed around the actual editors and the actual content, with tests covering the access edges.
Hosting and operations
Node runtime, database, backups, CDN for media and TLS set up on whichever host makes sense, with a deployment pipeline your team can run without us.
Upgrades and migrations
Moving from Payload 1 or 2 onto 3, including the Next.js integration work and the migration scripts needed to carry live content across without downtime.
Custom admin components
Field components, dashboards and workflows that match how your editors actually work rather than the generic defaults, so content teams stop fighting the UI.
Managed Tech
Dependency updates, backup verification, admin performance watched, and an engineer on call who has read your collections when a rule starts behaving oddly.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Payload CMS alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Payload CMS questions

Something else? Call+1 737 727 7327

Should we use Payload instead of WordPress or Strapi?

Payload wins for TypeScript heavy teams who want the content model under version control and expect to run the CMS inside a Next.js codebase. WordPress still wins for marketing sites run by non technical editors with a plugin ecosystem need. Strapi is the closer comparison and the choice between the two usually comes down to which stack your team already knows well. We will give you a plain read for your case rather than default to the newest option.

Can you take over an existing Payload project?

Yes. We inventory the collections, document the custom hooks, review the access control for roles that currently exist, and bring the hosting and backups into something your team can run. Most takeovers end with a shorter config, a documented admin, and a deployment pipeline that no longer depends on whoever set it up originally.

How do we migrate from Contentful or Sanity to Payload?

We map each content type to a Payload collection, carry assets over to the chosen storage backend, write a scripted import that runs idempotently so re-runs are safe, and verify counts and fields before cutover. The tricky parts are usually rich text format differences and references between documents, which we handle explicitly rather than letting an importer guess.

Why is our Payload admin slow to load?

The admin bundle grows with every field type, media library and custom component, so a site that started fast gets sluggish as the model grows. We split rare field types out of the main bundle, cache assets through a CDN, pre warm the Node runtime on serverless, and trim collections that were added for a feature that never shipped.

Can editors use Payload without a developer?

Day to day content work, yes, once the admin is tuned and the fields match their mental model. Structural changes to the content model still land as code, which is the trade off Payload makes on purpose. For teams that want to add a new field without a deploy, a hybrid setup with WordPress for marketing pages is sometimes the right call.

How much does Payload CMS help cost?

No charge for estimates. Send a description of the site, a rough collection list and any errors that are biting, and a price comes back in writing before any work is scheduled.

Free estimate

Payload CMS giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.