FAQ
What is Sanity, and who is it for?
Short answer
Sanity is a hosted content platform: the Content Lake database stores structured content, Sanity Studio is the editing app, and libraries deliver it to websites, apps and AI agents (Sanity Docs, October 2026). It fits teams with developers who model content in code, because Studio is configured in code, and it is the wrong tool for a small site with no developer.
- Sanity's own category
- Content Operating SystemA hosted content database (the Content Lake), an editing app (Sanity Studio) and libraries, not a website builderSources: Sanity (Take control of your content operations, in one place, Sanity Studio); Sanity Docs (A very short introduction, Content Lake (Datastore))
- What you build yourself
- The content model and the front endThe content model is TypeScript in your repository, and Sanity ships no front end, so headless sites usually need front end developersSources: Sanity (Sanity Studio, The benefits of headless CMSes)
- What Sanity hosts
- The Studio and the Content LakeStudio hosting is free on every plan as of October 2026; the backend is closed and hosted by SanitySources: Sanity Docs (Hosting and deployment); Sanity (Plans that scale with you, Self-hosting is only free if your time is worth nothing)
- Customer scale, per Sanity
- PUMA: 55,000+ reusable content piecesVendor-reported: more than 500 category landing pages and over 4,000 hero banners, with regions sharing one multi-tenant instanceSource: Sanity Customers (PUMA moves fast and gets global teams in sync with Sanity)
Deploi’s call
Sanity is for teams that treat content as a system a developer owns and editors use. Decide on who will own the content model and the front end, not on the feature list. If that owner exists, Sanity fits; if not, it is the wrong tool.
YesSanity fits when
- A developer will model the content in code and build the front end, because Sanity ships the Content Lake and Sanity Studio but no website.
- Several brands, sites or channels should read one structured content source, so each piece of content is written once and delivered everywhere.
- Editors need a Sanity Studio workspace shaped to your content model, which a developer configures in code.
NoSanity is the wrong choice when
- No developer will own the content model and the front end after launch, so no one can add a field or a page type.
- A small site would be served by a built-in theme and editor, so a separate front end is cost with no return.
- Policy requires you to host the content database yourself, because the Content Lake runs only as Sanity's hosted service.
What is Sanity?
Sanity is a content platform built from a hosted content database, developer libraries and AI tools, with apps such as the editing app Sanity Studio on top (Sanity Docs, A very short introduction, October 2026). The database is the Content Lake, which stores content as structured data that you can query and deliver to any channel (Sanity Docs, Content Lake, October 2026). The editing app is Sanity Studio, configured by your developers to fit your team (Sanity, Sanity Studio, October 2026). Sanity calls the whole set a Content Operating System (Sanity, Take control of your content operations, in one place, October 2026). It ships no website: Sanity's Next.js docs say Sanity provides the content infrastructure while Next.js handles rendering and routing (Sanity Docs, Sanity and Next.js, October 2026).
| Layer | What it does | Who works in it |
|---|---|---|
| Content Lake | Hosted database that stores content as structured data | Developers query it |
| Sanity Studio | Open-source editing app, configured in code | Editors and developers |
| Developer libraries | Deliver content to websites, apps and agents | Developers |
| Front end | The website or app that shows the content; you build it | Developers |
How is Sanity different from a traditional CMS like WordPress?
Sanity keeps content apart from the website, while WordPress ships themes that display content in the browser. WordPress says its themes "take the content stored by WordPress and display it in the browser" (WordPress Developer Resources, October 2026). Sanity's own page calls WordPress a decoupled CMS (content management system): it has an API (application programming interface) for other channels and a built-in presentation layer (Sanity, Decoupled CMS vs Headless CMS, October 2026). Sanity has no built-in presentation layer, so the site is a separate build, and the content model is TypeScript in your repository (Sanity, Sanity Studio, October 2026).
| Question | Sanity | WordPress |
|---|---|---|
| Built-in presentation layer | No, the front end is a separate build | Yes, through themes |
| Content for other channels | Through APIs and libraries | Through its API |
| Who builds the site | Your developers, in a separate build | A theme, or your developers through its API |
Deploi's view of WordPress comes from long use: Martin Dejnicki has worked with content management systems for more than 20 years and built and managed hundreds of WordPress sites between 2005 and 2017 (Deploi, WordPress to Sanity Migration, October 2026). The full Sanity and WordPress comparison covers the trade-offs.
Who uses Sanity?
Sanity's customer stories include retail and media companies, and several run multiple brands, regions or products from one content system. The figures below come from Sanity's own stories, so read them as vendor claims:
- PUMA (the sports brand). Regions and subsidiaries share one multi-tenant Sanity instance, and the team has built more than 500 category landing pages and 55,000 pieces of reusable content (Sanity Customers, PUMA, October 2026).
- Morning Brew. Six engineers run 13 brands on a single Content Operating System, through three tailored Studios (Sanity Customers, Morning Brew, October 2026).
- Tecovas. Product launches take under 20 minutes, and 10,000 SKUs (stock-keeping units) update in seconds (Sanity Customers, Tecovas, October 2026).
Deploi isn't a customer story. We run deploi.ca's Shopify sections on Sanity ourselves, from one Studio with three workspaces and two datasets (counted 24 October 2026).
What does a team need to run Sanity?
A team needs a developer to model the content and build the front end, because Sanity ships no front end and headless sites usually require front end development skills (Sanity, The benefits of headless CMSes, October 2026).
What a first Sanity project needs
- Model the content. A developer writes the content types as TypeScript in the Studio project, and
npm create sanity@latestproduces a working Studio (Sanity, Sanity Studio, October 2026). - Deploy the Studio. One command hosts it at a Sanity address, and hosting is free on every plan as of October 2026 (Sanity Docs, Hosting and deployment, Sanity pricing).
- Build the front end. A front-end developer builds the site or app that queries the Content Lake; see how Sanity works with Next.js.
- Train the editors. Editors work in the Studio your developers configured, so they need a walkthrough of your content model, not of Sanity in general (Deploi's judgment).
Cost starts at $0 on the Free plan (Sanity pricing, October 2026), and Is Sanity free? compares it with the paid Growth plan.
When is Sanity the wrong choice?
Sanity is the wrong choice when no developer will own it, when the site is simple, or when you must run the whole stack on your own servers. Three cases:
- No developer. Headless sites usually require front end development skills (Sanity, The benefits of headless CMSes, October 2026).
- A simple site. Sanity's own guide says that for no-frills sites for local businesses and hobbyist blogs, the benefits of conventional content management system (CMS) architectures can outweigh the drawbacks (Sanity, The benefits of headless CMSes, October 2026).
- Self-hosting required. Sanity's own post says it closed off the backend and explains why you can't bring your own database, so the Content Lake runs as Sanity's hosted service (Sanity blog, March 2025; Sanity pricing, as of October 2026).
If none of these applies, see the full Sanity review.
Deploi’s point of view
- Where we disagree
- AI answers call Sanity 'a headless CMS' and stop there. That hides what buyers actually pay for: the content model and the front end are projects, not settings. The opposite error is calling Sanity an editor-friendly website builder. Its editing app is configured in code, so the quality of the editing experience depends on the developer who built it.
- What we’ve seen
- We run deploi.ca's Shopify sections on Sanity from one hosted Studio with three workspaces over two datasets in a single project, counted on 24 October 2026. That keeps hosting to one Studio, and it is an agency using Sanity on its own sites.
- Where we would push back
- Sanity's home page leads with "The Content Operations Platform" and AI workflows. Start with the content model. Automation on a weak model repeats the weakness faster, and an editor who can't find the field won't use the agent either.
- How we scope it
- Before we say yes to a Sanity build we ask who will own the front end after launch, how many brands or channels share content, and whether any content must be private. Those answers decide the plan and the team before they decide the schema.
When this answer changes
- Sanity changes how it describes itself, for example the name Content Operating System
- Sanity ships a built-in website or page-builder front end
- Sanity opens the Content Lake for self-hosting
- The customer figures for PUMA, Morning Brew or Tecovas change on Sanity's customer pages
- Free Studio hosting changes on any plan
Sources
Every source opened and checked on 25 October 2026.
- Sanity Docs, A very short introduction
- Sanity Docs, Content Lake (Datastore)
- Sanity, Sanity Studio
- Sanity Docs, Hosting and deployment
- Sanity, The benefits of headless CMSes
- Sanity, Decoupled CMS vs Headless CMS: What Are The Differences?
- WordPress Developer Resources, What Is a Theme?
- Sanity Customers, PUMA moves fast and gets global teams in sync with Sanity
- Sanity Customers, How Morning Brew powers a $50M+ media business with six engineers and Sanity
- Sanity Customers, Built to scale, not maintain
- Sanity, Plans that scale with you
- Deploi, WordPress to Sanity Migration
- Sanity, Self-hosting is only free if your time is worth nothing
- Sanity Docs, Sanity and Next.js
- Sanity, Take control of your content operations, in one place