Contentful vs Payload

Update, 3 September 2026: Salesforce completed its acquisition of Contentful on 1 September 2026. See what the close changes.

The choice between Contentful and Payload is mostly one decision wearing two hats: do you want a managed service that someone else runs, or a platform you own and host yourself. Almost every difference below follows from that one fork. This page lays out where each side genuinely wins, then breaks the differences down feature by feature.

The core difference

Contentful is a headless content platform delivered as software-as-a-service. You model content in a hosted interface, editors work in a mature admin, and Contentful runs the infrastructure, the uptime, and the upgrades. You consume the content over an API and never think about servers.

Payload is a headless CMS on hosting you choose. The content model is TypeScript in your repository, the data sits in a database you control, and the admin is a React application. Deployment and maintenance can be handled by your team, a managed hosting provider or a partner such as WAYF. Its open-source core has no per-seat licence.

The distinction is the service arrangement and control over the stack. Contentful bundles its platform and hosting; Payload lets you choose both the infrastructure and who operates it.

Where Contentful is the stronger choice

Contentful is a strong fit when its hosted admin, existing integrations and plan entitlements match the organisation’s needs. Contentful operates the platform, with a contractual SLA of up to 99.99% on Enterprise. Its roles and permissions are mature, and publishing workflows come with a paid space. Procurement teams can evaluate the enterprise compliance certifications and support commitments alongside that quote.

Contentful includes vendor-operated hosting in the platform contract. Payload can also be delivered with managed hosting and ongoing support, including through WAYF, while keeping control of the code and data with the client. Neither choice requires the editorial team to operate infrastructure.

Where Payload is the stronger choice

Payload earns its keep when ownership and fit matter. Your content sits in your own database, on infrastructure you control, with no plan tier or space quota that steps up as records, locales, or API calls grow. For a TypeScript and React team, the content model living as version-controlled code means schema changes go through pull requests and code review like everything else.

It also reaches places a hosted CMS cannot. Payload can run inside the same Next.js application as your frontend, share its authentication, and be extended with custom React components and server-side logic. When the CMS is part of the product rather than a separate service, that closeness is the whole point.

Pricing and total cost of ownership

Contentful combines a plan fee, space quotas and paid-plan API and bandwidth overages. Payload’s open-source core is free; its operating cost includes hosting, storage, traffic and engineering, plus any enterprise licence needed for the governance features above. Self-hosting removes Contentful’s plan quotas, not the cost of serving a growing estate.

For a small site with a few editors, the engineering time needed to operate a deployment can outweigh the hosted subscription. For a large platform with many locales, heavy API traffic or a lot of records, compare the vendor quote against the infrastructure, support and maintenance needed for that workload. Self-hosting can reduce total cost, but scale alone does not guarantee savings.

This page weighs one destination. If the open question is whether to leave Contentful at all, or which other platform to weigh, our guide to Contentful alternatives works through that decision by motive.

If the comparison has become a delivery brief, WAYF’s content-platform service covers the model, application and handover around a Payload build. The Ingersoll Rand case study shows a complex multi-brand platform in production.

The plan and space gates named above were rechecked at the source on 14 September 2026: user, role and locale counts, the Spaces table’s workflow quotas and Lite Space price, overage rates, SCIM provisioning, localized workflows and the uptime SLA against Contentful’s published pricing, SSO and publishing workflows against Payload’s enterprise page, and the system-wide audit log against Payload’s enterprise audit-log page. Neither vendor publishes a price for the enterprise tier that carries them.

A note on our position

WAYF is a Payload Partner agency and a top contributor to its open source, so we have an interest here. We pick Payload often because self-hosting, code-first modeling, and no lock-in fit how we and our clients build. When a team is better served by a managed SaaS, that is the recommendation we give, and Contentful is a strong one.

Decided on Payload? Read the Contentful-to-Payload migration guide →