Try the demoGet Started
  • CMS comparison

ApostropheCMS vs. Payload

ApostropheCMS and Payload are both open-source, self-hostable JavaScript platforms. Payload makes Next.js the foundation of the application, while ApostropheCMS provides a complete content and page-management system with native rendering or Astro-powered frontend choice.

The key difference

Apostrophe CMS icon

ApostropheCMS is designed for

Editor-managed websites and products where structured content, integrations, application behavior, and in-context editing need to work together. Use native JSX for a simpler project or Astro for frontend freedom.

Payload icon

Payload is designed for

Next.js applications that need a typed backend, generated administration interface, authentication, APIs, access control, file storage, and direct server-side database access in the same project.

The biggest difference

ApostropheCMS includes direct editing through the rendered page in its open-source CMS foundation. Payload's open-source editing experience centers on its generated administration interface, Preview, and developer-configured Live Preview. Payload promotes a more directly comparable Enterprise Visual Editor, but currently marks it as coming soon. Both platforms are MIT-licensed, code-first, self-hostable, and capable of powering more than a conventional marketing website.

ApostropheCMS and Payload at a glance

Compare the architecture, editing models, content operations, and implementation responsibilities most likely to affect long-term fit.

Platform and architecture
Features
ApostropheCMS
Payload
Product and source model
MIT-licensed open-source CMS. Community Edition is free; Pro and Assembly add paid capabilities. MIT-licensed open-source application framework and CMS. The open-source product is free; Enterprise adds commercial capabilities, hosting, and support.
Primary architecture
Complete Node.js CMS application. Provides content models, page management, editing, APIs, authentication, permissions, and application extensibility. Next.js-native full-stack framework. Installs in a Next.js application and generates the backend, Admin Panel, APIs, authentication, and access-control foundation.
Frontend approach
Native server-side JSX or Nunjucks, or an official Astro integration. Astro lets teams use React, Vue, Svelte, Solid, and other supported frontend frameworks while preserving in-context editing. Next.js is the current application foundation. The Admin Panel, HTTP layer, and primary frontend architecture live within the Next.js application.
Content APIs
REST APIs and custom application routes. APIs can complement native or Astro rendering or support a fully headless implementation. REST, GraphQL, and Local APIs. The Local API lets server-side code perform operations directly without an HTTP request.
Databases
MongoDB, PostgreSQL, and SQLite MongoDB, PostgreSQL, and SQLite
Deployment
Self-host or use optional Apostrophe managed hosting Self-host wherever Next.js runs, use supported deployment templates, or purchase Enterprise hosting

Payload describes itself as a Next.js full-stack framework and requires a supported Next.js installation. Its typed configuration generates the Admin Panel and Local, REST, and GraphQL APIs. ApostropheCMS supports server-rendered JSX and Nunjucks as native template options. Its JSX templates run on the server rather than providing a React runtime. The official Astro integration is the path to using frontend frameworks such as React, Vue, Svelte, and Solid while retaining in-context editing.

Editing and content operations
Features
ApostropheCMS
Payload
Standard editing experience
Edit directly through the rendered page. In-context editing is included in Community Edition and preserved through Astro. Generated administration forms with Preview and Live Preview. Developers connect the frontend to Payload's Admin Panel and preview tools.
Direct visual editing
Included in open source. Editors work directly through the actual rendered experience. Announced as an Enterprise Visual Editor. Payload's Enterprise overview currently marks the feature as coming soon.
Page composition
Add and arrange widgets and layouts through the page. Developers define the available components and design guardrails. Manage Blocks and rich-text structures through generated forms. Developers build the frontend that interprets and renders those structures.
Content modeling
JavaScript schemas for pages, pieces, widgets, relationships, and custom fields Typed configuration for Collections, Globals, fields, relationships, and Blocks
Draft and publishing workflow
Draft, submit, share, publish, and schedule included in open source Drafts, autosave, publishing, and scheduled publishing available when configured. Enterprise Publishing Workflows add multi-step approvals.
Version history
Document Versions in Pro and Assembly Versions, diffs, and rollback available in open source when enabled
Permissions
Contributor, Editor, and Admin roles included. Advanced Permissions adds custom groups and granular document- and content-type controls. Developer-defined access control included. Rules can operate at the collection, operation, document, and field levels.
Localization
Unlimited locales and localized page management included. Manual and automatic translation tools are available in Pro and Assembly. Unlimited locales and field-level localization included. The Admin Panel is translated into more than 30 interface languages.

Payload Preview creates a link to the rendered frontend, while Live Preview embeds that frontend in an iframe inside the Admin Panel and updates it as form data changes. Payload's configurable Versions feature supports change history, diffs, drafts, autosave, and restoration. Scheduled publishing requires the drafts option to be enabled and a mechanism that processes Payload jobs.

Platform operations
Features
ApostropheCMS
Payload
Multitenancy
Assembly provides a shared application and central multisite dashboard. Sites share code and integrations while maintaining isolated content, users, media, permissions, domains, and branding. Official multi-tenant plugin. Developers have to define the tenant collection, access model, domain routing, provisioning, frontend behavior, and operational interface.
Managed hosting
Self-hosting or optional managed hosting. Hosting is priced separately from Pro and Assembly. Self-hosting, deployment templates, or Enterprise hosting. Enterprise arrangements can include dedicated support and hosting.
Commercial capabilities
Pro and Assembly. Add advanced permissions, versions, translation tools, AI features, and multitenant site operations. Enterprise. Adds capabilities such as SSO, publishing workflows, AI tools, dedicated support, and hosting. The Visual Editor is currently marked coming soon.
  • Architecture

Frontend flexibility or a Next.js foundation?

Payload builds the CMS into a Next.js application. ApostropheCMS can render natively with server-side JSX or Nunjucks, or use Astro to bring other frontend frameworks to the CMS.
One extensible CMS application, with a choice of frontend approach
Payload’s Local API lets server-side code interact with Payload directly, without network latency or a separate HTTP request.

Which CMS architecture is better for you?

Apostrophe CMS icon

ApostropheCMS's architecture may fit better when

You want a simpler CMS application using native server-side JSX or Nunjucks.

You want Astro to provide frontend-framework choice without losing in-context editing.

Content, page management, integrations, application behavior, and presentation should work within one extensible CMS system.

Payload icon

Payload's architecture may fit better when

Next.js is already the chosen application foundation.

A typed backend and generated Admin Panel should live in the same project.

Direct server-side access through the Local API is important.

Bottom line: Payload integrates the CMS deeply into a Next.js application. ApostropheCMS can provide a simpler native application with server-side JSX or Nunjucks, or use Astro to bring frontend-framework choice to the CMS without sacrificing in-context editing.

  • Editing experience

In-context visual editing vs. live preview

ApostropheCMS makes the rendered page the editing interface. Payload’s open-source experience uses generated forms with Preview and Live Preview, while its direct Visual Editor is a separate Enterprise capability.

In ApostropheCMS, editors click directly into text, images, widgets, and layouts on the rendered page. The page remains the primary workspace whether the project uses native server-side rendering or the official Astro integration.

Payload generates administration forms from the project's schema. Developers can configure a Preview link that opens the frontend or use Live Preview to embed the frontend in the Admin Panel and reflect unsaved form changes in real time.

Payload promotes an Enterprise Visual Editor for point-and-click editing and component rearrangement through the rendered frontend. Its current Enterprise overview marks this capability as coming soon, so it should not yet be treated as equivalent to an established, generally available editing workflow.

Apostrophe CMS icon

Apostrophe's in-context visual editing may fit better when

Editors regularly create complete pages and content-rich experiences.

Direct editing through the rendered page should be included in open source.

The editing experience must continue when using an Astro frontend.

Payload icon

Payload's form editing with visual context may fit better when

Editors are comfortable working primarily through generated forms.

Developer-configured Preview or Live Preview provides enough visual context.

The team prefers to build and control the frontend-preview implementation.

Bottom line: ApostropheCMS includes direct in-context editing in open source. Payload includes Preview and Live Preview in open source, while its more directly comparable Enterprise Visual Editor is currently marked coming soon.

See what it feels like to edit the actual page

Change content, add components, adjust layouts, and manage pages directly through the rendered experience.

  • Content model

Code-first models, different outcomes

Payload configuration generates an application backend, Admin Panel, and APIs. ApostropheCMS schemas connect structured content to pages, editor controls, APIs, and rendered experiences.

Payload developers define Collections, Globals, fields, relationships, Blocks, authentication, hooks, and access rules through typed JavaScript or TypeScript configuration. The same configuration generates the Admin Panel and Local, REST, and GraphQL APIs.

ApostropheCMS developers define pages, reusable content pieces, widgets, relationships, and custom fields through its module and schema systems. Those definitions shape both the stored content model and the interface editors use through the rendered page. REST APIs and local-style model APIs are also available.

Apostrophe CMS icon

Apostrophe's content model may fit better when

Structured content and page composition need to work together.

Schemas must produce a purpose-built in-context editing experience.

Custom editor interfaces are part of the product requirement.

Payload icon

Payload's content model may fit better when

The application needs a strongly typed Next.js backend.

Collections, hooks, authentication, and database operations are central.

GraphQL is important.

Bottom line: Payload configuration generates an application backend and Admin Panel. ApostropheCMS schemas define both the content system and the page experience editors manage.

  • Content operations

Different strengths in editorial workflow and versions

ApostropheCMS includes more of the editorial handoff in open source. Payload includes deeper open-source version history, diffs, and rollback.
Features
ApostropheCMS
Payload
Draft content
Included Included when drafts are enabled
Autosave
Supported through the editing experience Available when configured
Preview drafts
Included through the rendered page Preview and Live Preview can be configured
Submit for editorial review
Included Custom implementation or Enterprise Publishing Workflows
Share a draft without login
Included No equivalent first-party workflow identified
Schedule publishing
Included Available when configured with an active jobs runner
Version history and diffs
Pro and Assembly Included when Versions is enabled
Restore an earlier version
Pro and Assembly Included when Versions is enabled
Configurable multi-step approvals
No configurable multi-stage workflow Enterprise Publishing Workflows

Payload’s open-source Versions system is a meaningful strength. When enabled, it can retain changes, show diffs, restore earlier versions, support drafts, and autosave content. Scheduled publishing is available but depends on project configuration and a running jobs process. Payload’s Enterprise Publishing Workflows add defined approval stages, notifications, and inline feedback. ApostropheCMS Community Edition instead provides more of the editorial handoff itself, including contributor submission, preview, shareable drafts without requiring reviewer accounts, publishing, and scheduled publishing. Document Versions and rollback are Pro and Assembly capabilities.
Apostrophe CMS icon

ApostropheCMS's workflow features may fit better when

Contributors need a ready-made submit-for-review process.

Stakeholders need to review drafts without receiving CMS accounts.

Editorial handoff and scheduled publishing should work in open source.

Payload icon

Payload may fit better when

Version history, diffs, and rollback should be available in open source.

Developers want to define workflow behavior through access control and application logic.

Enterprise multi-step approval workflows fit the organization's requirements.

Bottom line: ApostropheCMS includes the stronger open-source editorial handoff; Payload includes the stronger open-source version-history system.

  • Governance

Editorial roles vs. code-defined access

ApostropheCMS starts with a ready-made publishing hierarchy. Payload gives developers granular programmatic control over users, documents, fields, and operations.

ApostropheCMS

Contributor → Editor → Admin

Ready-made roles divide content creation, publishing, and application administration.

Advanced Permissions in Pro and Assembly adds custom groups and more granular document-, content-type-, and locale-level controls.

Payload

Authenticated user + application data → access function → permitted operation

Developers can evaluate the current user, roles, document data, tenant, request context, and other application criteria.

Access rules can apply to collections, operations, individual documents, and fields.

Apostrophe CMS icon

ApostropheCMS may fit better when

Editorial roles should work without extensive configuration.

Contributors and publishers need clearly separated responsibilities.

Administrators should be able to manage governance without changing application code.

Payload icon

Payload may fit better when

Permissions are tightly connected to application data and business logic.

Developers need field-, document-, and operation-level control in open source.

Authentication serves both the Admin Panel and the customer-facing application.

Bottom line: ApostropheCMS begins with an editorial permissions model. Payload offers deeper programmatic access control in open source.

  • Localization

Page localization vs. field localization

Both platforms support unlimited locales. ApostropheCMS localizes pages and reusable content, while Payload localizes selected fields within Collections and Globals.
Features
ApostropheCMS
Payload
Number of locales
Unlimited Unlimited
Localization model
Localized pages, page structures, and reusable content Field-level localization for configured fields and nested structures
Publishing by locale
Localized documents participate in the standard editorial workflow Locale-specific publishing status is available as an experimental beta feature
Admin UI translation
Translatable; currently ships in six languages and can be extended by developers Translated into more than 30 interface languages
Manual translation workflow
JSON import and export in Pro and Assembly Import/export plugin can move localized values, but is not an equivalent translation workflow
Automatic translation
Available in Pro and Assembly AI translation promoted through Payload Enterprise
Locale-specific permissions
Available through Advanced Permissions in Pro and Assembly Can be implemented through developer-defined access rules

Payload places no limit on configured locales. Localization applies at the field level, including nested structures when configured. Its locale-specific publication status is explicitly documented as experimental and in beta. Payload distinguishes content localization from administration-interface internationalization, and its Admin Panel currently supports more than 30 interface languages. Payload promotes translation as part of its Enterprise AI offering, while public implementation and packaging details remain sales-led.
Apostrophe CMS icon

ApostropheCMS may fit better when

Editors need to localize complete pages and page structures.

Manual and automatic translation should be first-party CMS workflows.

Localization must work alongside editorial workflow and configurable governance.

Payload icon

Payload may fit better when

Individual fields within application records need localized values.

Developers want explicit API control over locale and fallback behavior.

Broad built-in translation coverage for the Admin Panel is important.

  • Multitenancy

Build the multitenant layer yourself or use Assembly to start with it built in

Payload provides a plugin and developer-configured foundation for multitenancy. Apostrophe Assembly adds provisioning, isolation, and central oversight for customer-managed sites.

Payload’s official multi-tenant plugin adds tenant relationships to selected collections, filters data by tenant, and supports tenant-aware administration and access patterns. Developers still define the tenant collection, domain model, routing, provisioning process, frontend behavior, and the management experience around the application.

Apostrophe Assembly adds the product layer needed to provision and operate many independent editor-managed sites. Sites share application code and integrations while maintaining isolated content, users, media, permissions, domains, and branding. Authorized teams manage the portfolio through a central Multisite Dashboard.

Apostrophe CMS icon

Apostrophe Assembly may fit better when

Your product provides editor-managed websites to customers.

Non-developers need to create, configure, and oversee sites.

Each site needs isolated content, users, media, permissions, and branding.

Payload icon

Payload may fit better when

Multitenancy is part of a custom Next.js application.

Developers want to own the tenant schema, routing, provisioning, and management interface.

Tenants are application accounts or workspaces rather than complete managed websites.

Bottom line: Payload provides multitenant building blocks. Assembly provides a supported platform for operating many customer-managed sites.

  • Deployment

Software licensing, hosting, and support

Both platforms can be self-hosted, but their commercial offerings package software capabilities, infrastructure, and support differently.

ApostropheCMS

Community Edition is MIT-licensed and self-hostable. Pro adds advanced permissions, document versions, translations, and AI-powered tools. Assembly adds multitenant site operations. First-party managed hosting is optional and priced separately.

Payload

The core product is MIT-licensed and self-hostable. Payload can run anywhere its supported Next.js application can run. Official deployment options include Vercel and Cloudflare templates. Enterprise can include hosting, dedicated support, SSO, publishing workflows, and additional commercial capabilities. Enterprise pricing is sales-led.

Bottom line: Compare licensing, application hosting, database, media storage, support, infrastructure, and internal maintenance—not simply whether the core software is free.

  • In Summary

Which CMS fits your project?

Choose based on your application foundation, the role the CMS needs to play, and the editing experience your team needs.

Apostrophe CMS icon

Choose ApostropheCMS when

Best fit: Editor-managed websites, digital platforms, custom product experiences, and multitenant customer-site applications.

Editors need to build and manage complete pages directly through the rendered experience.

In-context editing should be included in the open-source product.

You want either a simpler native project using server-side JSX or Nunjucks, or an Astro frontend with React, Vue, Svelte, Solid, or another supported frontend framework.

Contributor submission, shareable draft previews, and scheduled publishing should work out of the box.

Localization needs to include complete pages, page structures, and first-party translation workflows.

You need a supported platform for operating customer-managed sites.

Payload icon

Choose Payload when

Best fit: Next.js applications, custom application backends, internal tools, commerce platforms, and products where CMS functionality is one part of a broader application.

Next.js is the current application foundation.

You want a typed backend, generated Admin Panel, authentication, and APIs inside the same project.

GraphQL is a strict requirement.

Deep code-defined access control is important.

Open-source version history, diffs, and rollback are priorities.

Your developers want to build the editorial, page-building, or tenant-operations experience around Payload's application framework.

Compare the editing experience—not only the technology stack

See how content schemas, reusable components, layouts, workflow, and in-context editing work together in ApostropheCMS.