Sanity CMS – content lake, studio, GROQ and when we recommend it

Definition

Sanity is a headless CMS launched in 2017 that stands out for being structured from the ground up – content is defined as schemas in code, and editorial work happens in a customisable Studio.

In depth

Sanity is a headless CMS launched in 2017 by the Norwegian team behind the design studio Bengler. The platform stands out for being structured from the ground up – content is defined as schemas in code, editorial work happens in a framework called Sanity Studio (which you extend yourself), and content is fetched through a purpose-built query language called GROQ. For teams that want full control over the data model and the editorial interface, Sanity is often the first choice.

The appeal of Sanity is not speed or price – it is the structure. The platform makes you think through how the content should be organised before you start producing it. For some teams that is a feature; for others it is overkill.

How Sanity is built

Sanity consists of three layers:

• Content Lake. Centralised cloud storage where all content lives as JSON documents. Every document has an ID, a type and a set of fields defined by your schema.
• Sanity Studio. The editorial interface where content creators work. The Studio is a React application that you configure yourself and can run locally or deploy wherever you like. It is open source and fully customisable.
• APIs. GROQ for flexible queries (like SQL for JSON), GraphQL as an alternative, plus a webhook system and the Live Content API for real-time updates.

The data model is defined in code – typically TypeScript – so the schema is versioned along with the rest of the codebase. That is one of the big differences from CMSs where the data model lives in an admin panel separate from the code.

What Sanity is good at

• Structured data. Sanity enforces clear data models. An article is not just "rich text" – it is a title, an author reference, a publication date, a number of blocks of portable text, and so on. So the frontend can render the content however it likes, and the same content can be used on the web, in a mobile app, in a newsletter pipeline and in an AI assistant.
• Portable Text. Sanity introduced the concept of "portable text" – a structured representation of rich text that is not HTML but a JSON format. That means rich text can be rendered with correct semantics in any channel.
• A customisable Studio. Need a client-specific view for editors? An unusual field? A preview that matches production? You can extend the Studio without leaving the React ecosystem you already know.
• Real-time functionality. Sanity has built-in real-time collaboration via websockets – several editors can work at the same time and see each other's changes live, and the Live Content API delivers updates straight to the frontend.
• GROQ. The query language – which stands for Graph-Relational Object Queries – is powerful: joins between document types, projections and filtering on deeply nested fields. It is also an open specification that Sanity open-sourced in 2019. For developers tired of REST endpoints, GROQ is often a revelation.
• Versioning and Content Releases. Sanity has solid revision history and versioning. Content Releases – previewed in 2024 and generally available in 2025 – let you group several changes and publish them together. The feature is included in some Enterprise plans and suits large campaigns or product launches.

Where Sanity is not always the right choice

• The initial setup needs developers. There are no "Sanity templates" in the way there are WordPress themes or Webflow templates. A Sanity project is a code project from day one.
• A learning curve for editors. Sanity Studio is very capable, but for an editor used to WordPress or the Webflow CMS it can feel unfamiliar.
• Schema migrations. When you change the data model – rename a field, change a type, add a new required field – you have to think through the consequences for existing content.
• Price at scale. Sanity has a generous free tier and reasonable prices for small to mid-sized projects. With many users, heavy bandwidth or large document volumes, however, costs can climb.

When we recommend Sanity

At SEOS Design we are happy to bring in Sanity when:

• The content model is complex and needs to be versioned together with the code.
• The frontend is built with Next.js, Astro, Nuxt or a similar modern stack.
• The content will be used in several channels (web + app + newsletter + integrations).
• The team has developers in the loop on an ongoing basis, not just at the initial delivery.
• Editors want a fine-tuned workspace rather than a standard admin panel.

We usually do not recommend Sanity when the editor wants to change the design themselves, when there is no budget or process for continued development after launch, or when an established template in Webflow or WordPress already meets the need.

For a deeper look at how a headless CMS like Sanity works together with AI-assisted development and a modern frontend, see AI-assisted web development: Claude Code, Next.js & headless CMS. If you are looking for a partner to help you choose and set up the right CMS, read more about how we work as a headless CMS agency.

Sanity vs Contentful vs Storyblok

• Sanity is the most developer-friendly and flexible, needs code to set up, and has the most customisable Studio and the best query language.
• Contentful is the most mature for enterprise use, has the strongest roles and permissions and the best documentation for large teams, but feels less flexible in frontend rendering.
• Storyblok has the best editor experience thanks to a visual editor with live preview, which makes it particularly pleasant for teams where marketing owns publishing.

‍

There is no "best" in absolute terms. In a Swedish agency setting with a modern frontend and developers on hand, we often end up choosing Sanity. For larger international organisations, we more often end up with Contentful. Where the marketing or content team wants to be self-sufficient, we often go with Storyblok. We look at choosing a platform for growing and larger companies in more depth in Website platform for large and growing companies.

Sanity and MCP – AI agents that work directly on the content

One of the strongest reasons to look at Sanity in 2026 is how well the platform works with AI agents. Sanity has an official MCP server, which means an agent such as Claude can connect directly to the Content Lake and read, create, update and publish content – without a developer as a go-between.

What makes Sanity unusually well suited to this is that the foundation is already in place: the data model is schema-as-code, the content is structured and typed, and GROQ gives the agent a precise way to fetch exactly the right document. An AI agent does not have to guess its way forward – it works with a known structure. Compared with a CMS where the content is unstructured HTML, the difference is marked.

In practice, a marketing department can ask an agent to update a price list, publish a new article or correct metadata across hundreds of pages – and have it done in minutes. The same caveat applies as always: the agent is only as good as the structure it works with. Consistent naming, complete CMS fields and a documented architecture are what separate a website AI can manage from one it makes a mess of.

We go through what MCP means for content management in more depth in MCP agency for websites. That work often happens in close collaboration with our sister brand AI Partner when AI agents and automation workflows need to be integrated more deeply into an organisation.

Sanity and SEO

As a rule, headless CMSs are SEO-neutral – it is the frontend implementation that determines the SEO outcome. Even so, Sanity has a direct bearing on SEO in a few areas:

• Structured data is trivial. Because the content is structured from the start, it is easy to generate schema markup, correct canonical tags, hreflang and sitemap.xml automatically from the Content Lake.
• Internationalisation. Sanity has good patterns for multilingual content, but you need to make design choices early – fields per language or documents per language.
• Preview. One area where Sanity shines is preview flows. Editors can preview pages before publishing, which reduces the risk of incorrect SEO elements in production.
• Content reuse. Because the same content can be used in several contexts, the risk of duplicate content is reduced if you handle canonicals and variant links correctly.

Summary

Sanity is a headless CMS for teams that want full control over their data model, their editor interface and their frontend. It is not the fastest way to start, but it is often the most scalable way to continue. For modern frontend stacks with ongoing development, it is one of the best choices on the market. For simple brochure websites, it is typically overkill. Base the decision on how complex your content is and how stable your development team is, and you will make the right call.