Stet vs Contentful

Side by side.

The same seven questions, asked of both. Checked against published documentation in July 2026.

Question	Stet	CContentful
Who models the content	Stet Marketing, in the UI. Collections, maps and fields with no deploy.	Contentful Marketing, in the web app. Content types are configured in the UI.
Types in your app	Stet A typed client generated from the live model by a Vite plugin.	Contentful Generated by a separate CLI or community tools, wired up and kept current by you.
When the model changes	Stet A removed field becomes a deprecation in the types. The build stays green.	Contentful No deprecation path. Removing a field is a breaking change you coordinate by hand.
Analytics	Stet Included. First-party and cookieless, through your own infrastructure.	Contentful Not included.
AI	Stet Included. Drafting, suggestions and delegated tasks, approving every write.	Contentful AI Actions, on Enterprise plans.
Hosting and licence	Stet Hosted cloud or self-hosted. Open source.	Contentful Hosted only. Not open source, not self-hostable.
How pricing works	Stet $10 per user per month. Free to self-host.	Contentful Free tier, then $300 per month for Lite, then Enterprise pricing on request. Locales and content types are capped per tier.

What Contentful does better.

Environments, roles and workflow governance are genuinely enterprise-grade, and the ecosystem of apps and integrations is the largest here.

1import { stet } from '@stetcms/client';2 3const post = await stet.posts.get('hello-world');4 5post.

The fields from that collection, arriving in the editor as typed properties on the generated client.

When to pick Contentful instead.

Pick Contentful if you need multi-environment governance today, or if your organisation requires a vendor with that scale of compliance and support behind it.

Other comparisons.

The same seven questions, asked of everything else teams weigh Stet against.