Stet vs WordPress

Side by side.

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

Question	Stet	WWordPress
Who models the content	Stet Marketing, in the UI. Collections, maps and fields with no deploy.	WordPress Marketing, in the admin, though custom fields usually need a plugin and often a developer to register them.
Types in your app	Stet A typed client generated from the live model by a Vite plugin.	WordPress None by default. The REST API is untyped; teams add WPGraphQL and a code generator to get types.
When the model changes	Stet A removed field becomes a deprecation in the types. The build stays green.	WordPress Nothing warns anyone. A renamed field surfaces as an empty region at runtime.
Analytics	Stet Included. First-party and cookieless, through your own infrastructure.	WordPress A plugin, or a third-party script and the consent banner that comes with it.
AI	Stet Included. Drafting, suggestions and delegated tasks, approving every write.	WordPress Plugins, of widely varying quality.
Hosting and licence	Stet Hosted cloud or self-hosted. Open source.	WordPress Self-hosted or managed hosting. Open source, GPL.
How pricing works	Stet $10 per user per month. Free to self-host.	WordPress Free software. You pay in hosting, plugins and maintenance.

What WordPress does better.

The ecosystem has no equal, hosting is a commodity, and hiring someone who already knows the admin takes an afternoon.

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 WordPress instead.

Stay on WordPress if your site depends on its ecosystem, or if your team is large, non-technical and already fluent in it. Moving is a real project, and it should buy you something.

Other comparisons.

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