Glossary

Payload CMS

Looking to learn more about Payload CMS, or hire top fractional experts in Payload CMS? Pangea is your resource for cutting-edge technology built to transform your business.
Hire top talent →
Start hiring with Pangea's industry-leading AI matching algorithm today
A Pangea Expert Glossary Entry
Written by John Tambunting
Updated Feb 20, 2026

What is Payload CMS?

Payload CMS is an open-source headless CMS and full-stack application framework built natively on Next.js and TypeScript. Unlike most headless CMS platforms that run as separate services, Payload installs directly into your existing Next.js /app folder — content API, admin panel, and frontend all in the same deployment. The project was built by a web development agency that grew frustrated with available options, entered Y Combinator in 2022, and in June 2025 was acquired by Figma as part of Figma's push into design-to-deployment workflows. Enterprise customers including Microsoft, ASICS, and Blue Origin use it in production, and the GitHub repository has accumulated tens of thousands of stars.

Key Takeaways

  • Payload installs inside your Next.js app folder, eliminating the separate CMS service and its network round-trips.
  • Content schemas are defined in TypeScript config files, making them version-controllable and reviewable in pull requests.
  • The core software is MIT-licensed and fully free to self-host with no feature gating.
  • Figma acquired Payload in June 2025 to anchor its design-to-deployment platform — the MIT license was kept intact.
  • Demand for Payload skills is almost always bundled with Next.js, TypeScript, and PostgreSQL on full-stack contracts.

What Makes Payload Different

Most headless CMS platforms are separate services your app calls over HTTP — you build your Next.js site, then separately manage a Contentful or Sanity workspace. Payload flips that model. It lives inside your codebase, which means no network latency between your content API and your rendering layer. For content-heavy sites where Core Web Vitals matter, that difference is measurable.

The other architectural bet Payload makes is code-first schema definition. Content types, access control, and field-level hooks are all TypeScript config files — no GUI schema editors that generate opaque JSON you can't diff. For engineering teams that care about reviewing schema changes in pull requests the same way they review code changes, this approach is natural. The tradeoff is that non-technical editors can't reconfigure content types on their own.

Payload vs. Strapi vs. Sanity

Payload is the right pick when your team is TypeScript-fluent, you're building on Next.js, and you want the CMS to live in your codebase with no separate service to manage. Self-hosting is free; the admin panel is for editors, not schema configuration.

Strapi is a better fit when non-engineers need to configure content types through a GUI, or when your stack isn't Next.js. Strapi has a larger plugin ecosystem and a more mature no-code schema editor. It's JavaScript rather than TypeScript-first, though TypeScript support has improved.

Sanity is the cloud-native option for teams that prioritize real-time content collaboration. Editors can work simultaneously on the same document; Payload doesn't match that workflow. Sanity charges per API call with no self-hosting — the opposite of Payload's pricing model.

Pricing

The core Payload software is free under an MIT license — self-host it on any infrastructure and pay nothing to Payload Inc. For teams that want managed hosting, Payload Cloud Standard runs $35/month (512MB RAM, 3GB database, 30GB file storage) and Cloud Pro runs $199/month with a dedicated cluster, 30GB database, and 150GB storage. Enterprise Cloud starts at $10,000/year and adds SSO, AI auto-embedding, A/B testing, and SLA guarantees.

Most developer teams self-host and pay only their infrastructure provider — a Railway or Render deployment for a typical project runs $5–20/month. The cloud plans make sense for agencies that want managed infrastructure, not for teams comfortable running Postgres and Node.

Production Gotchas Worth Knowing

Payload's self-hosting freedom comes with operational responsibility most SaaS CMS products absorb for you. The most common production mistake: deploying on a platform with an ephemeral filesystem (Heroku being the classic example) without configuring external file storage. Uploaded assets silently disappear on dyno restart. Every Payload production deployment needs an explicit decision on four things: database, file storage (S3 or equivalent), email provider, and CDN.

Build memory is another genuine constraint — the compilation step is memory-hungry and will crash underpowered CI runners. Edge function deployments (Vercel Edge, Cloudflare Workers) hit bundle size limits that require careful tree-shaking to work around. Teams upgrading from v1/v2 face a meaningful migration to v3's multi-database architecture; this is not a minor version bump.

Payload CMS in the Fractional Talent Market

Companies hire Payload expertise for a specific scenario: they're building a custom Next.js application and want a backend content layer that lives in their codebase instead of a separate SaaS subscription. The hire profile is almost always a full-stack Next.js developer — standalone Payload-only roles are rare. When we see Payload listed in a job requirement, it's typically alongside TypeScript, PostgreSQL, and React, signaling a custom build project rather than a CMS implementation.

Digital agencies and product-led startups are the core hiring market. Because Payload projects tend to have a concentrated initial build phase with lighter ongoing maintenance, fractional and project-based engagements fit naturally. The Figma acquisition in 2025 has raised the tool's profile; expect hiring demand to increase as Figma builds Payload into its design-to-deployment workflow.

The Bottom Line

Payload CMS is the most developer-native option in the headless CMS space in 2026 — a genuine full-stack framework, not just a content API with an admin panel bolted on. Its MIT license and Next.js-native architecture make it a credible choice for teams that want to own their infrastructure and keep their content layer inside the codebase. Figma's acquisition signals where the platform is heading: deeper integration with the design-to-production workflow. For companies hiring through Pangea, Payload expertise indicates a full-stack developer who can build production-grade applications with TypeScript, owns the backend end-to-end, and doesn't rely on SaaS scaffolding.

Payload CMS Frequently Asked Questions

Is Payload CMS free to use?

Yes. Payload's core software is MIT-licensed and completely free to self-host. You pay only for the infrastructure you run it on (database, hosting, storage). Payload Cloud managed hosting plans start at $35/month for teams that don't want to manage infrastructure themselves.

Does Payload require Next.js?

Payload v3 (the current major version) is built natively on Next.js and is designed to install into a Next.js /app directory. Earlier versions ran as a standalone Node/Express service, but the current architecture is Next.js-first. Teams not on Next.js would be better served by Strapi or Directus.

How long does it take a developer to get productive with Payload?

A developer with TypeScript and Next.js experience can build and deploy a functional Payload project in two to three days. The configuration API is well-documented and the official docs cover most common patterns. There are no formal certifications, but the Discord community and GitHub discussions are active and searchable.

What happened when Figma acquired Payload?

Figma acquired Payload in June 2025 to anchor its design-to-deployment platform. Figma committed to maintaining the MIT open-source license and continuing investment in the open-source project. In the near term, nothing changed for existing users. The longer-term roadmap involves Figma building a CMS product for marketers on top of Payload's backend infrastructure.

When should I choose Payload over Contentful or Sanity?

Choose Payload when you want to self-host, avoid per-seat or per-API-call pricing, and are already building on Next.js and TypeScript. Choose Contentful or Sanity when your content team needs a polished SaaS interface, real-time collaboration, or enterprise workflow features that your engineering team doesn't want to build and maintain themselves.
No items found.
No items found.