Sanity is a beautiful piece of structured content infrastructure. It is also, for a blog, a significant amount of work. You define every content type as code, you spin up Sanity Studio as a React app you have to host and maintain, you learn GROQ to query anything, and the moment you want a second language you discover that multilingual is something you implement yourself. If the deliverable is a marketing blog, that is the wrong shape of effort. This article shows when Sanity is the right tool, when it stops being the right tool, and what a no-config alternative looks like.
Quick takeaways
- Sanity is excellent for structured content domains (product catalogs, editorial systems with custom workflows), and overkill for a blog.
- Schema-as-code means every content type lives in a TypeScript-shaped config file you commit, review, and migrate.
- Sanity Studio is a React application you host, deploy, and update.
- Multilingual content is bring-your-own: pick a plugin, model fields per locale, build the routing.
- Kamaan is a blog-first CMS with no schema config, no Studio to maintain, and 99+ languages on publish.
The friction with Sanity, for a blog
The first time you set up Sanity for a blog, the experience is fine. You install the CLI, run sanity init, get a starter schema, deploy Studio. Two months in, the friction starts to show.
Every new field is a code change. Want a second author byline, an FAQ block, a reading-time field, a category taxonomy with parent categories? Each of those is an edit to a schema file, a pull request, a deploy of Studio, and often a content migration script to backfill existing documents. For a team where the editor and the developer are the same person, that is fine. For a marketing team that just wants to publish posts, it is friction in the wrong place.
GROQ is the next surprise. It is a good query language. It is also a query language nobody on your team knows. Every "show three related posts" or "list posts by tag, excluding drafts" requires somebody to write GROQ, test it in the Vision tool, and ship the query into the front-end. Compared with a CMS that hands you a REST endpoint returning posts?tag=launch, GROQ is a learning tax you pay forever.
Multilingual is where most teams hit the wall. Sanity does not ship multilingual out of the box. You choose between field-level translation (one document, locale-suffixed fields) and document-level translation (one document per locale, linked by reference). Then you install a plugin, model your schema around the choice, build the language switcher, configure the router, and decide what happens when a translation is missing. None of that is hard. All of it is work that has nothing to do with publishing a blog post.
Sanity Studio is the last piece. It is a React app. You host it. You update it. When the Sanity packages release, you upgrade. When a content modeler changes a schema, you redeploy. For a blog, you are running a small front-end project for the privilege of editing text.
Where Sanity is genuinely the right choice
Before going further, the honest case for Sanity. If your content is structurally rich and reused across many surfaces (a product catalog with variants, a learning platform with lessons and modules and tracks, an editorial site with custom workflows and approval gates), Sanity is exceptional. Portable Text, references, custom input components, real-time collaboration in Studio, and the ability to query the same content from web, app, and email templates with GROQ all pay back the configuration cost.
For a blog, none of that is the bottleneck. The bottleneck is "we want to publish a post and have it appear, ranked, in five languages." Sanity does not optimize for that. Kamaan does.
Here is the short version of the alternative on a single card.
How Kamaan handles the same job
Kamaan is a blog CMS. The opinions are deliberate. Posts have a title, a body, a featured image, tags, an author, SEO fields, and translations. You do not configure that schema. It is the product.
Publishing a post is a single action. Auto-Multilingual Delivery generates translations in 99+ languages within seconds of publish, with hreflang wired correctly, parent and child article links handled for you, and no plugin to install. REST API Delivery exposes the same content as plain JSON with query parameters for tag, language, and pagination. No new query language to learn. Multi-Site Management lets one workspace serve several brand sites with shared media and per-site SEO. AI publishing through the MCP Server and ChatGPT Actions means you can draft and publish from Claude or ChatGPT directly into the CMS.
The pricing model is one flat $19 a month, with the first month free and a lifetime plan available if you would rather pay once. AI translation credits are only used when you ask Kamaan to translate for you; bring translations from Claude or ChatGPT and you spend nothing extra. Kamaan is currently in private beta, opening 50 founder slots in Q3 2026.
The trade-off is honest. You give up the ability to model arbitrary structured content. You get back the ability to publish today, in every language you sell in, without a developer in the loop.
Sanity vs Kamaan vs Contentful, for a blog
| Capability | Sanity | Kamaan | Contentful |
|---|---|---|---|
| Schema setup | Code-defined, per content type | None required, blog model built in | UI builder with content types |
| Editing UI | Sanity Studio (React app you host) | Hosted editor, no install | Hosted web app |
| Query language | GROQ | REST with query params | REST and GraphQL |
| Multilingual on publish | Bring-your-own plugin and modeling | Auto-Multilingual Delivery, 99+ languages | Locale-aware fields, manual translation |
| Multi-site model | One project per site or shared dataset patterns | Multi-Site Management built in | Spaces, with seat costs |
| AI publishing | Plugin work required | MCP Server and ChatGPT Actions native | Third-party integrations |
| Time to first published post | Days, with developer time | Same day, no developer | Days |
| Pricing surprise risk | API call limits on growth tiers | Flat plans, no per-call meter | Per-seat and per-record limits |
A real publishing scenario
A two-person founder team picks Sanity because a friend recommended it. Week one, they get a starter blog running. Week two, they want categories, an author bio, and a related-posts block. Two pull requests, a Studio redeploy, a small migration to fill in missing fields on existing posts. Week three, they want Spanish and German versions because their early customers are in Madrid and Berlin. They evaluate two i18n plugins, pick one, refactor the schema, redo the routing in their Next.js app, and write a fallback strategy for missing translations. Week four, they have a Spanish version of three out of nine posts.
The same team on Kamaan would have published nine posts in English on day one, generated Spanish and German on publish, and spent week two writing more posts instead of building i18n. The structural difference is not effort. It is what the effort buys.
A different scenario. An e-commerce brand has a product catalog with three hundred SKUs, custom merchandising rules, region-specific descriptions, and a marketing blog. For the product catalog, Sanity is the correct tool. For the blog, run it on Kamaan and let the catalog have its own home. Two systems is not a defeat; it is honest separation of concerns. The product team gets Sanity's Portable Text and Studio extensions for the catalog; the marketing team gets a CMS that publishes posts in five languages without a ticket to engineering. Each tool earns its place by doing one job well.
A third scenario worth naming. A solo founder running a SaaS wants to publish one post a week, in English plus the four languages where customers actually buy. On Sanity, that is a multi-week setup before the first post ships. On Kamaan, it is a sign-up, a post, and a publish. The founder spends the saved week writing the next three posts instead of configuring an i18n plugin.
A side-by-side view of how the two systems differ on the dimensions that matter for a blog is below.
FAQ
Is Kamaan a fork of Sanity or a wrapper around it?
No. Kamaan is its own CMS. It is not built on Sanity, does not use GROQ, and does not require Sanity Studio. The content model, the API shape, and the editor are independent.
What about Sanity's real-time collaboration?
Real-time multi-cursor editing in Studio is a genuine strength of Sanity for editorial teams that work on the same document at the same time. Kamaan focuses on solo and small-team blog workflows, where conflicts are rare and the autosave-and-history model is enough.
Can I export from Sanity to Kamaan?
Yes. Kamaan supports imports from common CMS export formats and from a JSON dump of your Sanity dataset. The migration script maps fields, brings over images, and preserves slugs so existing URLs keep working.
Do I lose Portable Text features when I move?
Some. Portable Text is great for custom block types (inline references, callouts, custom embeds). Kamaan uses a simpler block model focused on blog content: paragraphs, headings, lists, images, quotes, code, and embeds. If your blog leans on a long tail of custom block types, that is a flag to evaluate before moving.
How does Kamaan handle SEO compared with Sanity?
Sanity gives you the fields if you model them. Kamaan ships them: meta title, meta description, focus keyword, slug, OG fields, Twitter card fields, canonical URL, and hreflang across locales. Sitemap and robots are handled at the site level. The point is not that Sanity cannot do it; it is that you do not have to build it.
What is the pricing difference in practice?
Sanity's free tier is generous for prototypes; the cost curve appears as your API requests, dataset size, and seats grow. Kamaan uses flat per-site plans with no per-API-call meter. For a high-traffic blog with frequent re-fetches, that difference compounds.
Can I use Kamaan with Next.js, Nuxt, SvelteKit, or Astro?
Yes. Kamaan's REST API Delivery returns JSON; the front-end framework is your choice. Sample integrations exist for Next.js, Nuxt, SvelteKit, and Astro.
What if I outgrow Kamaan?
You export. Kamaan ships a full content export to JSON, including translations and media URLs. That is a deliberate commitment: if the fit changes, the door is open.
Related on Kamaan
-
Storyblok vs Kamaan: Multi-Site Pricing Compared. The per-space vs tier-bundled-sites comparison, applied to Storyblok.
For a head-to-head specifically on multilingual support, see Ghost vs Kamaan: Native Multilingual Support Head-to-Head. Ghost runs one language per install; Kamaan ships native multilingual on Growth and up.
Start building with Kamaan
If your job is a blog and your team is small, the schema-as-code path is paying a developer tax that does not buy anything you need. Kamaan ships the blog model, the multilingual pipeline, and the AI publishing integrations as the product. Start a site, paste in a post, and watch it appear in 99+ languages in one publish.
