This guide is for a CTO, product owner or marketing lead who is choosing a content platform for a website, portal or web app before a build starts. It sits under web application development, the service that usually builds the front end and the integrations around the CMS you choose.
In this guide
- What actually separates one headless CMS from another?
- How do Contentful, Strapi, Sanity and Payload differ?
- Which editorial model does your team need?
- Which hosting model can you actually run?
- Which API shape fits your front end?
- Decision rules: which one should you choose?
- Choosing and proving a headless CMS
- When should you not go headless?
- Where AI fits in a headless CMS project
- What delivery record exists, and what does not?
- Alternatives to the four: other routes and when to pick them
- What are the limits of this comparison?
- Frequently asked questions
- Next step
What actually separates one headless CMS from another?
Every headless CMS stores structured content and serves it to front ends through an API. The differences that matter for a buying decision sit in three places, and feature checklists hide all three.
Editorial model. Who edits, how much page layout control they expect, and how they preview a change before it goes live. A marketing team that builds landing pages every week needs something different from a product team that edits help articles inside an app.
Hosting model. Who runs the content store and the editing interface. The four products cover four distinct models: a vendor-hosted service, a hosted content store with an editor you can run yourself, a self-hosted open-source server, and a CMS embedded inside your own application.
API shape. How the front end reads content: REST, GraphQL, a dedicated query language or a direct call inside the same process. The shape decides caching, preview and how much glue code your developers write.
How do Contentful, Strapi, Sanity and Payload differ?
| Option | Hosting model | Editorial and modelling | API shape |
|---|---|---|---|
| Contentful | Vendor-hosted service; content served through a global CDN | Content types managed in the hosted web app; separate environments for changes | REST delivery, preview and management APIs, plus a GraphQL content API |
| Strapi | Open-source server you host and customise | Admin panel for editors; models and plugins live in your project | REST and GraphQL |
| Sanity | Hosted Content Lake; open-source Studio you configure in code and deploy yourself or on Sanity's hosting | React-based Studio, real-time collaboration, highly customisable | GROQ query language and GraphQL |
| Payload | Open-source TypeScript codebase installed into a Next.js app, on MongoDB or Postgres | Admin panel generated from your code config | REST, GraphQL and a direct Node.js API |
Each row comes from the vendor's own documentation, cited below. Contentful's API basics list separate delivery, preview and management APIs, while Payload's documentation describes REST, GraphQL and direct database APIs generated from your config.
Which editorial model does your team need?
Start with the people who will edit, not the developers who will integrate. Three questions sort most teams.
- Do editors need to preview unpublished changes in the real page? All four can support preview, but the work differs. Contentful exposes a separate read-only preview API for drafts; with Payload the CMS sits inside the same Next.js app, so preview is part of the application code.
- Do several people edit the same document at once? Sanity's Studio is built for real-time collaboration and is the natural fit when editing is a shared, frequent activity.
- Who changes the content model? If developers own the model and want it in version control, Sanity and Payload keep schemas in code. If the model should be editable in a hosted interface by a content lead, Contentful fits better.
Which hosting model can you actually run?
Hosting is where lock-in and operations work trade against each other. A vendor-hosted service removes servers, patching and backups from your list, and adds a contract, usage limits and an exit plan. A self-hosted open-source server removes the vendor dependency and adds an operations duty that someone must own every month.
Strapi describes itself as an open-source headless CMS that you can self-host and customise, which suits teams that need data to stay in their own infrastructure. Sanity is a hybrid: the Content Lake is Sanity's hosted store, while the Studio can be deployed on your own hosting. Running the Studio yourself does not move the content itself, so it does not answer a data-residency requirement on its own.
Payload removes the separate CMS server entirely: it runs inside your Next.js application on your database. That is the simplest topology for a product team, and it ties the CMS lifecycle to the application's release cycle.
Which API shape fits your front end?
If the front end is a static or cached marketing site, a CDN-backed delivery API such as Contentful's keeps reads fast without your own servers. If the content feeds several channels with different shapes, a query language like Sanity's GROQ, or GraphQL on any of the four, lets each channel ask for only the fields it needs. If the CMS lives inside one Next.js app, Payload's direct Node.js API avoids a network hop and an API client.
Decision rules: which one should you choose?
- Marketing team edits often, no wish to run servers, enterprise procurement is normal: start with Contentful.
- Editing is collaborative and the editor experience must be shaped to the content: start with Sanity.
- Data must stay in your infrastructure and you have someone to run it: start with Strapi.
- A TypeScript team builds one Next.js product and wants the CMS in the same repository: start with Payload.
- Two rules point to different options: the hosting rule wins, because it is the hardest to change later.
These rules pick a starting point for a proof of concept, not a final answer. Run the checklist below before any demo.
Choosing and proving a headless CMS
-
Model the content first
List the content types, their fields and relationships, and the three pages that are hardest to build. A CMS chosen before the model is chosen on its demo.
-
Write down the editorial workflow
Roles, drafts, approvals, scheduled publishing and preview, as the editors describe them.
-
Decide the hosting constraint
Data residency, security review and who runs the platform each month.
-
Build one hard page in two candidates
Same model, same page, real preview; time how long it takes and note what needed custom code.
-
Check the exit
Export the content of the proof of concept and confirm it can be imported elsewhere.
-
Agree ownership
Name who owns the content model, upgrades and access reviews after launch.
When should you not go headless?
Skip headless when one person edits a small marketing site and a traditional CMS with a page builder already does the job; the separate front end adds cost and no benefit. Skip it when nobody on the team can build and maintain a front end, because a headless CMS ships without one. And when the site is really a store, the decision is about commerce architecture first.
See headless commerce versus traditional platforms
Where AI fits in a headless CMS project
AI helps in two places: drafting a first content model from existing pages for an analyst to correct, and generating summaries, translations or alt-text drafts that editors review before publishing. Netbase works with the major commercial and open-source AI tools and models, chosen per project, and the content API is what makes those workflows possible without copying content by hand.
Editors still approve every published change, and developers still own the model and access rules.
- In delivered work
Product recommendation engine
Built for 4over4's online printing store from browsing and purchase history; a delivered AI feature named with a client, not a CMS project.
- Available capability
AI content workflows
AI drafting and enrichment on top of a content API is a capability Netbase offers, not yet tied to a published CMS case.
What delivery record exists, and what does not?
Netbase works as offshore development partner on a multi-tenant cloud ERP delivered as SaaS for a US client, not named, whose stack includes React and Next.js, Laravel and Strapi on AWS. For a loyalty and rewards technology company, also not named, Netbase delivered a headless reward shop platform on Magento 2 Open Source with a Next.js front end. Netbase also builds WooCommerce, Magento 2, Laravel and headless commerce platforms.
Delivery runs in a six-step lifecycle with weekly reviews and KPI dashboards, and Netbase runs and maintains what it builds under an agreed support scope. Most Netbase projects are delivered on fixed-price contracts. Netbase can build on any of the four products compared here, but no published Netbase record describes a Contentful, Sanity or Payload project, and no speed, cost or traffic result is claimed.
Alternatives to the four: other routes and when to pick them
- A traditional CMS with themes. Pick it when editors need page building and there is no front-end team.
- A headless mode of a traditional CMS. Pick it when editors already know the CMS and only one channel needs an API.
- A custom admin inside the application. Pick it when the "content" is really product data with business rules; our web application development team often builds it in the same stack, and a portal requirement checklist and Laravel admin criteria help scope it.
- A commerce platform's own content features. Pick them when most pages are product and category pages.
The selection criteria stay the same for every route: who edits, who hosts and how the front end reads. For the server side of a self-hosted CMS, see our Node.js and React and Next.js stack pages; for a product serving many customers, the guide to multi-tenant SaaS architecture covers isolation choices.
What are the limits of this comparison?
- It compares four products; other headless products can be sorted by the same three axes.
- Features and hosting options change quickly; check each vendor's documentation on the day you decide.
- Vendor prices and plan limits are left out on purpose, because they change and depend on usage.
Plan the next step with a Netbase consultant
Frequently asked questions
Payload installs into a Next.js app and runs in the same codebase, which suits one product team. Strapi runs as a separate server, which suits several front ends sharing one content back end or a team that wants the CMS released on its own schedule.
You can deploy the open-source Studio on your own hosting, but the content itself is stored in Sanity's hosted Content Lake, so self-hosting the Studio alone does not keep the content in your infrastructure.
Moving content is usually the easy part, because every option has an API for export. The work is in the front-end queries, preview wiring and editorial habits, which is why the hosting and API choice deserves a proof of concept first.
No. Search visibility depends on the front end you build: rendering, page speed, metadata and redirects. A headless CMS gives you control over those, and the duty to get them right.
Next step
If you are choosing a content platform for a new site or app, book a solution review and bring your content model and editorial workflow.
Related services and solutions
Web application development with AI built in where it converts Netbase provides web application development for product and commerce teams that need fast, maintainable web apps and storefront front ends, with AI search, assistants and automation added where they measurably help. Since 2012 Netbase has worked with 500+ businesses across 80 countries; according to its published case studies, PrintLeo's page load improved 35% and 4over4's conversion rose 48%.
Learn More
API integration services that keep your systems in agreement and ready for AI Netbase provides API integration services for commerce and operations teams that need e-commerce, ERP, CRM, shipping and payment systems to agree, so data moves once and AI services can act on it, with retries, monitoring and reconciliation on every API and webhook. According to its published client record, Netbase has worked with 500+ businesses across 80 countries since 2012.
Learn More
UI/UX design services: research, interfaces and design systems built in code Netbase designs the interfaces of web apps, SaaS products, mobile apps and online stores: user research, flows, wireframes, clickable prototypes and visual design, plus a design system shared by designers and developers. Because UI/UX designers sit inside the delivery team, the same people who design a screen see it built, tested and released.
Learn More
Digital product accelerators for SaaS, mobile and AI products Digital product accelerators are Netbase-built modules and delivery patterns that help founders and product teams launch SaaS, mobile and AI products faster. Instead of rebuilding accounts, billing, workflows and integrations from scratch, you reuse proven components, spend engineering time on what makes your product different, including the AI features buyers now expect, and own the custom code built for you.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.