Try the demoGet Started
  • CMS comparison

ApostropheCMS vs. Contentful

Author: Published by Apostrophe Technologies

Last Updated

ApostropheCMS and Contentful both support structured content, APIs, localization, workflows, and modern frontend development. Contentful provides a vendor-operated, API-first content platform. ApostropheCMS provides an open-source JavaScript CMS that can combine content management, application behavior, page composition, and in-context editing within one extensible system.

The key difference

Apostrophe CMS icon

ApostropheCMS is designed for

Editor-managed websites and SaaS platforms in which content, page composition, application logic, integrations, and in-context editing need to work together. Teams can render natively with server-side JSX or Nunjucks, or use Astro for frontend-framework choice.

Contentful icon

Contentful is designed for

Organizations that want a managed, API-first content platform for creating structured content once and delivering it across websites, applications, and other channels. Contentful operates the content platform while development teams build and host the experiences that consume its APIs.

The biggest difference

ApostropheCMS can be the CMS, application layer, page-management system, and editing experience. Contentful primarily acts as a separately operated content platform. Live Preview and Contentful Studio add visual context and page-building tools, but the rendered frontend remains a separate implementation. Both platforms support structured content, localization, previews, workflows, APIs, and multiple digital channels. The primary decision is whether the CMS should be part of the application you are building or a managed service that your applications consume.

ApostropheCMS and Contentful at a glance

Compare the product models, editing experiences, plan boundaries, and operational responsibilities most likely to affect implementation and long-term ownership.

Platform and architecture
Features
ApostropheCMS
Contentful
Product and source model
MIT-licensed open-source CMS. Community Edition is free; Pro and Assembly add paid capabilities. Proprietary managed content platform. Free, Lite, and Enterprise plans provide different limits and commercial capabilities.
Primary architecture
Complete Node.js CMS application. Can provide content models, pages, editing, APIs, permissions, integrations, and application behavior. API-first content platform. Contentful operates the content and delivery infrastructure; frontend experiences are implemented separately.
Frontend approach
Native server-side JSX or Nunjucks, or an official Astro integration. Astro enables React, Vue, Svelte, Solid, and other supported frontend frameworks while preserving in-context editing. Framework-agnostic delivery APIs. Developers choose, build, and host each frontend that consumes Contentful content.
Astro support
Official integration with in-context editing Connect through Contentful APIs and developer implementation
Content APIs
REST APIs and custom application routes REST and GraphQL delivery APIs, management APIs, and CDN delivery
Deployment
Self-host or purchase optional Apostrophe managed hosting Contentful operates the content platform; your team operates the rendered frontend

Contentful describes itself as an API-first platform for centrally managing and delivering content across digital touchpoints. Its architecture deliberately separates the platform from the experiences consuming its APIs. ApostropheCMS supports server-rendered JSX and Nunjucks. Its official Astro integration preserves in-context editing while allowing teams to use Astro-supported frontend frameworks.

Editing and content operations
Features
ApostropheCMS
Contentful
Standard editing experience
Edit directly through the rendered page. In-context editing is included in Community Edition and preserved through Astro. Structured entry forms with Live Preview. Editors update fields beside the rendered frontend, with optional live updates and inspector mode.
Visual page building
Compose developer-defined widgets and layouts through the page Contentful Studio Experiences. Editors assemble registered components through a separate visual canvas.
Frontend requirement for visual building
Astro supports React, Vue, Svelte, Solid, and other frontend options. Native JSX or Nunjucks can be used without Astro. Experiences uses a React SDK. Components are registered through @contentful/experiences-sdk-react.
Structured content modeling
JavaScript schemas for pages, pieces, widgets, relationships, and fields Content types, fields, references, rich text, validations, and reusable entries
Draft and publishing workflow
Draft, submission, shareable previews, publishing, and scheduled publishing included in open source Drafts, previews, publishing, and scheduling. Tasks, configurable workflows, automations, and localized workflows vary by plan
Version history and rollback
Document Versions in Pro and Assembly Published-entry version comparison and restoration included
Roles and permissions
Contributor, Editor, and Admin included. Advanced Permissions adds custom groups and granular controls in Pro and Assembly. Space roles and permissions. Default and custom role availability and limits vary by plan.
Localization
Unlimited locales and localized page management included. Manual and automatic translation tools are available in Pro and Assembly. Field- and entry-level localization. Locale limits, locale-based publishing, and localized workflows vary by plan.

Contentful Live Preview places the entry editor and rendered frontend side by side. Live updates and inspector mode require the Live Preview SDK. Contentful Studio Experiences uses a React-based SDK for registering and rendering components. Contentful supports scheduled publishing, published-entry version comparison and restoration, configurable workflows, and localized workflows. Availability differs across Free, Lite, and Enterprise plans.

Platform operations
Features
ApostropheCMS
Contentful
Operating multiple sites
Assembly provides one shared application and a central Multisite Dashboard. Sites share code and integrations while maintaining isolated content, users, media, domains, permissions, and branding. Spaces, Connected Spaces, and Templated Spaces. Contentful provides workspace, content-reuse, and governance models for multiple projects and standardized sites.
Managed infrastructure
Optional first-party application hosting. Hosting is priced separately from Pro and Assembly. Vendor-operated content platform and CDN. The rendered frontend and related infrastructure remain separate.
Commercial capabilities
Community, Pro, and Assembly. Paid products add advanced governance, versions, enhanced translation tools, AI capabilities, and multitenant operations. Free, Lite, and Enterprise Platform plans. Studio, Personalization, enterprise governance, localized workflows, and other capabilities have separate plan or add-on boundaries.
Support model
Community resources or direct support from Apostrophe Technologies. Teams retain the option to self-host. Community, plan-based support, Customer Success, Professional Services, and enterprise SLAs

Contentful's current pricing distinguishes Starter, Lite, Enterprise, and Templated Space models. Enterprise offerings include Connected Spaces and can add Contentful Studio; Templated Spaces are aimed at high volumes of smaller standardized sites. Apostrophe Assembly runs many independently edited sites from one codebase and provides a dashboard for creating and managing them.
  • Architecture

One CMS application or a separate content platform?

Contentful operates the content platform while your team builds the applications that consume it. ApostropheCMS can connect content, page management, integrations, backend behavior, rendering, and editing within one extensible JavaScript application.

Contentful centralizes content types, entries, assets, references, localization, and APIs in its managed platform. Developers then build and host the websites, applications, or other channels that retrieve that content. This is a strong model when content must serve many independently developed touchpoints.

ApostropheCMS is a complete Node.js CMS application. Developers can use the same extensible system to define:

  • Content schemas and relationships

  • Pages and reusable content pieces

  • Editor-facing widgets and controls

  • Authentication and permissions

  • Routes and APIs

  • Integrations and business logic

Teams then choose their frontend approach:

  • Native server-side JSX or Nunjucks for a simpler project contained within ApostropheCMS

  • The official Astro integration for React, Vue, Svelte, Solid, or another Astro-supported frontend framework with in-context editing preserved
One extensible CMS application, with a choice of frontend approach
Vendor-operated content platform delivered through APIs to separately built experiences
Apostrophe CMS icon

ApostropheCMS may be a better architecture when

The CMS is part of a custom website, portal, or digital product.

Content, page management, backend behavior, and integrations need to work within one extensible system.

You want native rendering or Astro-powered frontend choice without losing in-context editing.

Contentful icon

Contentful may be a better architecture when

Content must serve many separately built products or channels.

The organization wants a vendor to operate its core content infrastructure.

The existing architecture already treats content as a centralized API service.

  • Editing experience

In-context editing vs. Live Preview and Studio

ApostropheCMS makes the rendered page the primary editing interface. Contentful offers structured form editing with Live Preview, plus a separate Studio product for visual composition.

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

Contentful Live Preview displays the frontend beside the entry editor. Editors continue updating structured fields while the preview reflects changes. Live updates and inspector mode can connect visible content to its corresponding entry field.

Contentful Studio Experiences provides a different model. Developers register React components through the Experiences SDK, and editors assemble those components in a visual canvas. Studio is offered as an additional Contentful product for Enterprise customers rather than being the standard Platform editing model.

Editing approaches compared

  • ApostropheCMS In-Context Editing and Live Preview

    Direct in-context editing

    Edit text, images, widgets, and layouts through the rendered page. For widgets that require the editor modal, live preview shows changes instantly.

    • Open source

  • Contentful Live Preview

    Form editing beside the frontend

    Update structured fields while viewing the rendered result.

    • Contentful Platform, with implementation setup

  • Contentful Studio Experiences

    Visual composition canvas

    Assemble registered React components into page experiences.

    • Enterprise add-on
Apostrophe CMS icon

ApostropheCMS's editing experience may be a better fit for your editors if

Editors should work directly through the same rendered experience visitors see.

In-context page composition should be part of the open-source CMS foundation.

Visual composition should not require the frontend to use React.

Contentful icon

Contentful's editing experience may be a better fit for editors when

Structured forms paired with a live rendered preview meet the editorial requirement.

A React-based visual composition system fits the frontend architecture.

Centralized content reuse across many channels matters more than editing directly through each channel.

See the visual editing difference

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

  • Content model

Structured content for one application or many channels?

Contentful is optimized for centralized, channel-neutral content. ApostropheCMS connects structured content to the pages, application behavior, and editing experience that use it.

Contentful teams define content types, fields, validations, references, and reusable entries, then retrieve the resulting content through REST or GraphQL APIs. This supports organizations that want one content model to serve websites, applications, email, signage, and other channels.

ApostropheCMS developers define pages, reusable pieces, widgets, relationships, and custom fields through JavaScript schemas and modules. Those definitions shape the stored content, APIs, page composition tools, and editor-facing interface.
Pages, pieces, and widgets drive editing controls, APIs, and the rendered experience
Channel-neutral content delivered through APIs to many independent channels
Apostrophe CMS icon

ApostropheCMS's content model may fit better when

Structured content and page composition must work together.

Content types are closely connected to custom application behavior.

Schemas need to create a purpose-built editor experience, not only an API model.

Contentful icon

Contentful's content model may fit better when

The same structured content must feed many independent products and channels.

Content modeling is managed centrally and separately from frontend implementation.

REST and GraphQL delivery are central architectural requirements.

  • Content operations

Ready-made workflow or configurable content operations?

ApostropheCMS includes a practical editorial handoff in open source. Contentful offers broader tasks, workflows, automation, scheduling, and localized content operations across paid plans.

Editorial Workflow Features
Features
ApostropheCMS
Contentful
Draft content
Included Included
Preview content
Included through the rendered page Live Preview beside the entry editor
Submit for editorial review
Included Tasks or configurable Workflows, depending on plan
Share a draft without login
Included No directly equivalent standard workflow identified
Schedule one entry or document
Included Scheduled publishing available on paid plans
Configurable workflow steps
No configurable multi-stage workflow Available through Contentful Workflows
Workflow automations
Not a standard workflow feature Available through Workflow actions and automations
Localized workflows
Locale-specific workflow and permissions through the Apostrophe model Available in eligible Enterprise configurations
Version comparison and rollback
Pro and Assembly Published-entry versions included

Contentful Workflows can include multiple steps, role and permission rules, editing and publishing restrictions, automations, and localized translation workflows. Scheduled publishing is included on Lite and Enterprise rather than the Free plan. Contentful also includes comparison and restoration of previously published entry versions. This is a meaningful strength relative to ApostropheCMS Community Edition, where Document Versions is a paid Pro and Assembly capability.

ApostropheCMS's editorial workflow features may fit better when

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

Stakeholders need to review drafts without receiving CMS accounts.

Core review and scheduled publishing should be included in open source.

Contentful's editorial workflow features may fit better when

The organization needs configurable multi-stage or localized workflows.

Content operations span large teams, markets, and channels.

Automation, tasks, notifications, and enterprise governance are central requirements.

  • Governance

Editorial roles or enterprise governance?

ApostropheCMS begins with a clear publishing hierarchy. Contentful provides Space-level roles and a broader governance model for organizations, teams, Spaces, environments, tags, and workflows.

ApostropheCMS

Contributor → Editor → Admin

Ready-made roles separate 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.

Contentful

Organization → Space → role and permissions

Contentful includes default roles such as Admin, Editor, and Author. Roles are assigned at the Space level, and the same user can hold different permissions in different Spaces. Custom-role availability and total role limits depend on the plan.

ApostropheCMS's permissions models may fit better when

Familiar editorial roles should work without extensive configuration.

Governance needs to operate directly on page and content documents.

Teams want advanced controls without committing to a proprietary SaaS platform.

Contentful may fit better when

Permissions span many Spaces, teams, environments, markets, and workflows.

Content operations are managed centrally across a large organization.

Enterprise identity, compliance, service levels, and governance are primary requirements.

  • Localization

Page localization or centralized localization?

Both platforms support multilingual content. ApostropheCMS organizes localization around pages and editor-managed experiences, while Contentful localizes structured entries and fields across channels.

Localization
Features
ApostropheCMS
Contentful
Locale count
Unlimited Limits vary by plan; Enterprise is configurable
Localization model
Localized pages, page structures, and reusable content Field- and entry-level localization
Localized editing
Included through the standard in-context editing experience Localized fields and entries in the Contentful editor
Locale-specific publishing
Localized documents participate in the editorial workflow Locale-based publishing available on eligible plans
Admin UI translation
Translatable; currently ships in six languages and can be extended English, German, and French supported
Manual translation workflow
JSON import and export in Pro and Assembly Commonly handled through integrations, apps, or external processes
Automatic translation
Available in Pro and Assembly AI translation and localized workflows available through Contentful’s commercial platform
Locale-specific permissions
Advanced Permissions in Pro and Assembly Roles, workflows, and localized governance vary by plan

Contentful supports field-level localization, entry-level strategies, locale-based publishing, and localized workflows. Current plan limits differ substantially: Free and Lite include fixed locale allowances, while Enterprise supports custom numbers of locales and advanced localized operations. Contentful also promotes AI-assisted translation within its broader platform.

ApostropheCMS's approach to localization may fit better when

Editors need to localize complete pages and page structures.

Unlimited core locales should not depend on a SaaS plan.

Manual and automatic translation should work as first-party CMS extensions.

Your editorial team is or might be global and in need of a translated admin interface

Contentful's localization may fit better when

Localized structured content must feed many separate channels.

Translation is part of a centralized enterprise content operation.

Locale-based publishing and localized workflows fit the organization’s Contentful plan.

All editors are native English speakers

  • Multiple sites

Separate content workspaces or one shared site platform?

Contentful provides Spaces and enterprise content-reuse models. Apostrophe Assembly provides one shared CMS application with the site-management layer already included.

Contentful Spaces provide separate content workspaces. Environments isolate versions of content and configuration within a Space. Connected Spaces and cross-Space references allow enterprise teams to share and govern content across Spaces.

Contentful now also promotes Templated Spaces for deploying high volumes of smaller, standardized sites based on structures controlled by an Enterprise Space. This makes Contentful more relevant to multisite evaluation than a simple “one Space per website” description suggests.

The remaining distinction is what comes with the platform. Contentful provides content workspaces, templates, governance, references, and APIs. Your team still implements and operates the frontend applications, domains, site provisioning experience, customer access model, and any product-specific site-management interface.

Apostrophe Assembly includes the shared CMS application and operating layer for independent customer-managed sites. Sites can share schemas, components, integrations, and releases while maintaining isolated users, content, media, permissions, domains, and branding. Sites are created and managed through a central dashboard.
Spaces and governance models feeding separately built site frontends
One shared CMS application operating isolated customer-managed sites

Apostrophe Assembly may fit better when

Your product or service delivers editor-managed websites to customers.

The provisioning, isolation, branding, and oversight layer should come with the CMS product.

Every site shares application logic and proprietary integrations.

Contentful may fit better when

Products or sites should remain separate content workspaces.

Central content reuse and governance matter more than one shared website application.

Your organization will build and operate the frontend and site-management layer separately.

  • Commercial model

Which CMS should you choose?

ApostropheCMS gives teams control over the CMS application and operating environment. Contentful provides managed content infrastructure through an ongoing SaaS relationship.

Apostrophe CMS icon

Apostrophe might be a better CMS choice if

Community Edition is MIT-licensed and self-hostable.

Pro adds advanced permissions, versions, translation tools, and other commercial capabilities.

Assembly adds multitenant site operations.

First-party managed hosting is optional and priced separately.

Direct product support is available without requiring teams to give up self-hosting.

Contentful icon

Contentful might be a better CMS choice if

Contentful operates the content platform, APIs, and content-delivery infrastructure.

Free, Lite, and Enterprise plans carry different limits for users, roles, locales, Spaces, API usage, bandwidth, and features.

Contentful Studio, Personalization, and other products may carry separate commercial boundaries.

Enterprise plans add Customer Success, Professional Services, support, governance, compliance, and SLA options.

Your organization still develops and operates the rendered frontend.

Which CMS costs less?

There is no honest universal answer.

A self-hosted ApostropheCMS project can reduce recurring software costs and preserve infrastructure control, but your team owns the operational work. Contentful removes responsibility for operating the content platform but introduces an ongoing subscription, usage limits, and plan boundaries.

Compare total cost across:

  • CMS software and add-ons

  • Contentful usage or Space requirements

  • Application and frontend hosting

  • Database, media, and CDN infrastructure

  • Developer implementation

  • Content operations

  • Required users, roles, locales, and environments

  • Support, governance, and compliance requirements

  • Ongoing maintenance

Which platform fits your project?

Choose based on whether you need a managed content platform serving many channels or a CMS application that connects content, pages, custom behavior, and editing.

Apostrophe CMS icon

Choose ApostropheCMS when

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

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

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

You want native server-side JSX or Nunjucks, or Astro-powered frontend-framework choice.

The CMS is part of a custom website, portal, product, or application.

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

You need control over hosting, data, integrations, and application architecture.

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

Contentful icon

Choose Contentful when

Best fit: Large centralized content operations, omnichannel programs, composable enterprise stacks, and organizations standardizing on managed content infrastructure.

You want a vendor-operated, API-first content platform.

Structured content must serve many independently developed channels.

Your organization prefers not to operate its CMS infrastructure.

Configurable enterprise workflows and centralized content operations are major requirements.

Spaces, Connected Spaces, Templated Spaces, and enterprise governance fit your operating model.

Contentful Live Preview or a React-based Studio implementation fits the editorial requirement.

Your organization accepts the commercial and architectural boundaries of managed SaaS.

ApostropheCMS is a strong Contentful alternative for JavaScript teams that need the CMS to be part of the application they are building—not only a managed source of structured content.

Contentful may be the stronger choice when centrally governed, channel-neutral content and vendor-operated infrastructure are more important than application ownership or direct in-context page editing.