Stet vs Sanity

Side by side.

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

Question	Stet	SSanity
Who models the content	Stet Marketing, in the UI. Collections, maps and fields with no deploy.	Sanity Developers, in code. The schema is a file in the Studio repository, so a new field is a pull request and a deploy.
Types in your app	Stet A typed client generated from the live model by a Vite plugin.	Sanity Generated from your schema and your GROQ queries with the CLI, as a step you own and run.
When the model changes	Stet A removed field becomes a deprecation in the types. The build stays green.	Sanity Your own schema change, in your own repository, released on your own schedule.
Analytics	Stet Included. First-party and cookieless, through your own infrastructure.	Sanity Not included.
AI	Stet Included. Drafting, suggestions and delegated tasks, approving every write.	Sanity AI Assist on paid plans.
Hosting and licence	Stet Hosted cloud or self-hosted. Open source.	Sanity Hosted only. The Studio is open source, the content backend is not self-hostable.
How pricing works	Stet $10 per user per month. Free to self-host.	Sanity Free for 20 seats, then $15 per seat per month with usage-based overages.

What Sanity does better.

GROQ is the best query language in this category, the free tier is unusually generous at twenty seats, and Studio customisation goes further than any comparable UI.

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

Pick Sanity if your content model is genuinely owned by engineering and you want it reviewed like code, or if you need querying more expressive than get-and-list.

Other comparisons.

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