Contentful is a SaaS headless CMS: the vendor hosts the platform, editors work in its web app, and your frontends read content through REST and GraphQL APIs. We build on Contentful for teams that want a managed platform with strong governance, and we tell you when its plan limits or licence cost point to another CMS.
What is Contentful in October 2026?
Contentful is a closed source, fully hosted content platform. There is nothing to install or patch. Content lives in spaces, each space has environments for development and testing, and each environment holds content types, entries and assets. Developers use the Content Delivery API for published content, the Content Preview API for drafts, the Content Management API for writes, plus a GraphQL API, an Image API and a CLI.
Around that core, Contentful sells several products:
- App Framework and Marketplace. Custom apps extend the editor with your own fields, sidebars and pages. Marketplace apps connect common tools without code.
- Studio. A visual editor where marketers assemble pages from your design system’s components, built with the Experiences SDK.
- Personalization and AI Actions. Audience-based content variants, and AI tasks for generating and translating content.
Plans and limits, as listed on Contentful’s pricing page as of October 2026:
| Plan | Price | Users | Roles | Locales | API calls per month | Notes |
|---|---|---|---|---|---|---|
| Free | $0 | 10 | 2 | 2 | 100K | 1 Starter Space: 25 content types, 2 environments, 10,000 records |
| Lite | $300 per month | 20 | 3 | 3 | 1M | Adds scheduled publishing, comments and tasks; one extra Lite Space can be bought |
| Enterprise | Custom | Custom | Custom | Custom | Unlimited | Studio, Personalization and AI Actions available as add-ons |
When we recommend Contentful
Contentful fits when several teams publish to several channels and governance matters as much as speed. We recommend it when:
- You want no CMS servers to run and are happy to pay a vendor for uptime, security and upgrades.
- Several brands, regions or business units need separate spaces with shared rules, roles and single sign-on.
- Your content is structured and reused: products, policies, locations, authors referenced across many pages.
- Your team already uses Marketplace apps for tools such as commerce, DAM or translation.
When we do not recommend it
Contentful is the wrong choice in a few common cases, and we say so in the audit:
- Small budgets with growing needs. The jump from the free plan to $300 per month is steep, and the Enterprise plan is where many larger features sit.
- Many locales or content types on a lower plan. Locales are capped at 2 on Free and 3 on Lite, and the Starter Space allows 25 content types. A multilingual site or a rich model hits those limits early.
- Teams that want the CMS in their codebase. If engineers want the schema, access rules and hooks in TypeScript in their own repository, an open source CMS fits better. See Strapi vs Contentful for that trade-off.
- Marketing-led page building on a mid-size budget. Studio sits in the Enterprise tier. If visual editing is the main need, read Storyblok vs Contentful.
If you are weighing Contentful against the other large hosted option, our Contentful vs Sanity comparison looks at modelling, editor experience and lock-in, and our list of SaaS headless CMS platforms shows the wider field.
What we build on Contentful
Content models. We design types, references and validations with your editors, and decide early what is shared across spaces and what stays local. Every model change goes into a migration script, run through the CLI against a sandbox environment first and then promoted. Nobody edits the production model by hand.
Frontends. We build Next.js or Astro frontends that read the Delivery API or GraphQL, render static pages, and revalidate them from Contentful webhooks when an editor publishes. Drafts use the Preview API and live preview, so editors see the page before it goes out.
Apps and integrations. We write custom apps with the App Framework for fields and workflows the editor lacks, and connect the space to commerce, search, DAM and translation services.
Migrating into and off Contentful
Into Contentful. Most of our migrations come from WordPress, Drupal or an older SaaS CMS. We map old templates to the new content model, script the import through the Management API, move assets, convert rich text into Contentful’s rich text format, and write the redirect map before launch. We check limits per plan before the import, since a model that needs 40 content types will not fit a Starter Space.
Off Contentful. Teams leave when licence cost or plan limits outgrow the value. Content exports through the API and CLI, so the data itself is portable. The work is in remapping references and rich text to the new platform and rebuilding the apps you depended on. We usually move teams to Strapi, Payload or Sanity, chosen after the same audit we run for any new platform.
Team and stack around Contentful
A typical Contentful project needs a lead who owns the content model and migrations, a frontend developer in Next.js or Astro, and sometimes an integration developer for apps and webhooks. The hosting side is small: the frontend runs on Vercel, Netlify or your own cloud, and Contentful runs itself.
If you need someone inside your team rather than a project, you can hire Contentful developers who have shipped on the platform. For how Contentful fits next to the other platforms we use, see our headless CMS development page.
