Payload CMS

What Is Payload CMS?

Payload is an open-source, TypeScript-native headless CMS designed to live inside your application repository. Unlike SaaS platforms, Payload is code-first, you define your content schema, access control, and hooks directly in TypeScript configuration files that sit alongside your application code.

It ships with a fully functional admin UI out of the box, REST and GraphQL APIs, and deep Next.js integration (including App Router support). Because it's open source and self-hosted, there are no per-seat fees and no vendor lock-in.

Key Features

• TypeScript-first - schema defined in TS config files, fully typed throughout
• Next.js App Router integration - can be embedded directly in your Next.js project
• Flexible access control - field-level, document-level, and collection-level permissions
• Blocks field - composable page builder blocks with typed schemas
• Hooks system - lifecycle hooks (beforeChange, afterRead, etc.) for custom logic
• Local API - call Payload directly from server components without HTTP overhead
• Self-hosted or Payload Cloud - full control over data and infrastructure

Pricing

Payload is MIT-licensed and free to self-host. Payload Cloud, the managed hosting option, starts at $20/month for a single project. For teams comfortable with infrastructure, self-hosting on Vercel, Railway, or a VPS keeps costs minimal.

The total cost of ownership is low compared to SaaS alternatives, there are no per-seat fees or bandwidth charges.

Our Experience

Payload is our strongest recommendation for Next.js projects where the team has development capacity and wants maximum control. The TypeScript schema colocated with application code creates a tight feedback loop, changes to content types are versioned alongside application code, type errors surface immediately, and the Local API eliminates an entire network layer in server-side rendering.

The admin UI is clean and functional without requiring configuration. Access control is genuinely powerful, we've built multi-tenant setups, role-based editorial workflows, and field-level permissions that would require custom middleware in other systems.

Where Payload requires more thought: hosting and database management fall on your team. For early-stage startups without dedicated DevOps, this is manageable with Payload Cloud or Railway deployments, but it's a real consideration.

When Lucky Media Recommends Payload CMS

We reach for Payload when:

• The project is built on Next.js and the team wants CMS and application code colocated
• Full ownership and zero vendor lock-in are non-negotiable
• Access control requirements are complex (multi-tenant, role-based field visibility)
• The team is TypeScript-proficient and wants a code-first development experience
• Budget constraints make SaaS CMS pricing prohibitive at scale

We'd suggest alternatives when:

• The editorial team needs a polished, intuitive interface with minimal configuration
• The project requires enterprise SLA and dedicated vendor support
• Infrastructure management is out of scope for the team

faq

Is Payload CMS free?

The core framework is open source and free to self-host. Payload Cloud, the managed hosting option, starts at $20/month. There are no per-seat fees or content record limits, you pay for infrastructure, not for users or content volume. For teams that self-host on Render, Railway, or a VPS, the only cost is the server. > Note: Since Payload joined Figma, the signups for Payload Cloud are paused.

Payload vs Sanity: what is the difference?

Payload runs inside your application codebase, schemas, access control, and the admin panel are all part of your repository. Sanity is a separate managed service. Payload gives full code ownership with no vendor dependency; Sanity offers a more polished out-of-the-box editing experience and managed infrastructure. Payload is the better choice for developers who want zero lock-in; Sanity is better when the editorial experience and real-time collaboration are the priority.

Does Payload CMS require a database?

Yes. Payload supports MongoDB and PostgreSQL. The database is managed by your team or via a managed service (PlanetScale, Neon, Supabase, Railway). Payload Cloud includes managed database hosting. For self-hosted deployments, most teams use managed Postgres on their cloud provider of choice.

Is Payload CMS good for non-technical editors?

It depends on how much the developer customizes the admin panel. Out of the box, the Payload admin is functional but relatively minimal compared to Sanity or Storyblok. With custom field components, conditional fields, and a thoughtful schema, Payload can produce an excellent editorial interface. It requires developer investment upfront that SaaS CMS platforms handle automatically.

Can I use Payload CMS without Next.js?

Yes. While Payload is closely associated with Next.js and includes a first-class Next.js integration, it works with any Node.js-compatible stack. The admin panel can run as a standalone Express/Fastify app or embedded within your framework. Teams using Astro, Nuxt, or a custom Node backend can use Payload as the CMS layer without Next.js.