Sanity occupies a peculiar position in the content platform landscape. It is, by almost every measure, the developer's CMS. And the Scorecard confirms that reputation with data. But data has a way of telling you things the marketing page won't, and Sanity's full profile on the DXP Scorecard reveals a platform with extraordinary strengths, genuine blind spots, and a very specific audience that it serves better than anyone.
Let's dig into the numbers.
Disclaimer before reading any further, the DXP Scorecard is incredibly dynamic day to day as scores refresh, so these scores are based on today March 14, 2026.
The Scores Tell a Clear Story
Sanity earned a Capability Score of 64.3, which places it in the middle of the pack among the 27 platforms we evaluated. AEM leads at 76.6. SitecoreAI sits at 69.6. Contentstack comes in at 67.9. On raw capability alone, Sanity is not the most feature-rich platform in the market.
But capability is only one dimension. Sanity's Cost Efficiency score is 76.2, third highest among all platforms behind Payload CMS (78.4) and Strapi (77.0). Platform Velocity is 75.1, reflecting a product that ships frequently and maintains genuine momentum. Customer Sentiment hits 89, the highest of any platform in the Scorecard. Developers don't just use Sanity, they actively advocate for it.
The composite picture shows a platform that trades breadth for depth. When you look at the Scorecard's scatter plot, Sanity sits firmly in the "Best Value" quadrant: high capability relative to cost, strong efficiency, and genuine cost to feature alignment. That's a deliberate positioning, and it explains both what makes Sanity compelling and where it will frustrate you.
Where Sanity Genuinely Excels
Content Modeling Is Best in Class
This is not hyperbole. Sanity scored 95 for Content Type Flexibility and 95 for Structured Content Support. Those are the highest scores in the entire Scorecard for those criteria.
Schema-as-code with 20+ field types, unlimited nesting depth, and fully programmatic type composition means you define your content model in JavaScript or TypeScript. You version control it. You test it. You deploy it through your existing CI/CD pipeline. No clicking through a web UI to define fields. No exporting JSON configs. The content model is code, and it behaves like code.
Portable Text is the other differentiator worth understanding. Rich text stored as a structured JSON AST, not an HTML blob. Custom block types, inline objects, annotations. Content that is genuinely portable across any output format: web, mobile, email, PDF, kiosk, conversational AI. For teams delivering content to multiple channels from a single source of truth, this matters more than almost anything else a CMS can offer.
Content Relationships scored 82 with strong reference types, filtered references, and GROQ's ability to do reverse lookups. Content Validation scored 88 with synchronous and async custom validation functions that can access the full document context. These aren't headline features, but they're the kind of deep content modeling infrastructure that compound over time.
Real-Time Collaboration Is Architecturally Native
Sanity scored 90 for Real-Time Collaboration. This is a score most platforms can only envy. AEM scores 54. Contentful comes in higher than most traditional platforms but below Sanity.
The difference is that real-time collaboration isn't a feature that was bolted onto the Content Lake after the fact. It's a foundational architectural decision. Multiple editors work on the same document simultaneously with automatic conflict resolution and presence indicators. No page locking. No "someone else is editing this" warnings. It works the way Google Docs taught everyone to expect collaborative editing should work.
For content teams that move fast and don't have time to coordinate who's editing what, this eliminates an entire category of operational friction.
The Developer Experience Is the Product
Sanity scored 88 for Local Development, 88 for TypeScript Support, 88 for API Design Quality, and 85 for Documentation Quality. The Scorecard's Technical Architecture category came in at 77.1 overall.
From CLI scaffolding (npm create sanity@latest) to a working Studio in minutes, from GROQ's expressive query power to automatic TypeScript type generation from your schema, Sanity provides one of the most streamlined development experiences in the CMS market. The SDK ecosystem scored 82, covering JavaScript, React, Next.js, Svelte, and more.
The React-based Studio itself is the platform's secret weapon. Extensibility scored 92, the highest of any CMS we evaluated. Custom input components, document actions, views, tools, and structure can all be built with standard React patterns. If you can build a React component, you can extend Sanity Studio. That single fact makes it more extensible than platforms that require learning proprietary plugin systems or writing Java bundles.
Cost Efficiency That Actually Holds Up
The TCO scores paint a positive picture. Pricing Transparency: 80. Sanity publishes its pricing on the website. Free tier, Growth at $15/user/month, Enterprise with custom pricing. You can estimate costs before talking to sales. Free/Hobby Tier: 80. The free plan includes up to 20 users, 2 public datasets, unlimited content types, and a generous usage quota. A developer can build a complete working prototype without spending anything.
Time-to-First-Value: 85. From npm create sanity@latest to a working Studio with content is measured in minutes, not weeks. Hosting Costs: 88. The Content Lake is fully managed SaaS. No databases to provision. No servers to patch. No scaling decisions. Ops Team Requirements: 85. A small team, even a solo developer, can run a production Sanity implementation.
For organizations where budget discipline matters, Sanity's cost profile is meaningfully different from traditional DXPs. The three-year TCO for a Sanity implementation is typically 10 to 20 percent of what an equivalent AEM or Sitecore engagement would cost.
Where Sanity Overpromises
"Content Operating System" Is Aspirational
Sanity's marketing positions it as a "Content Operating System," which implies a platform that orchestrates content operations end to end. The Scorecard tells a different story for DXP use cases.
Audience Segmentation: 10. Content Personalization: 15. A/B and Multivariate Testing: 5. Campaign Management: 35. These aren't scores that got rounded down. These are scores that reflect capabilities that effectively don't exist. Sanity has zero native tooling for personalizing content based on audience, testing content variations, or managing marketing campaigns.
The "Content Operating System" label is accurate in the sense that Sanity provides infrastructure for content. It stores it, models it, delivers it, and makes it queryable. But it does not operate on content in the way that marketing teams expect a content platform to operate. No segments. No experiments. No campaign workflows. If your buying decision is driven by a marketing team expecting self-service personalization, the gap between the positioning and the product will surface quickly.
Visual Editing Is Improved but Still Developer Dependent
Sanity scored 72 for Visual/WYSIWYG Editing, which reflects meaningful progress with the Presentation tool. Click-to-edit overlays on a live frontend preview are genuinely useful. But Sanity's primary editing paradigm remains form-based with structured fields.
There is no drag-and-drop page builder. No marketer-facing layout editor. No component palette that a content author can rearrange without developer support. Landing Page Tooling scored 62. Cross-Functional Complexity scored 28, meaning that non-technical team members face a steep learning curve.
For teams where the developer builds the page structure and the content author fills in the fields, this works well. For teams where marketing needs to create new page layouts, rearrange components, and launch landing pages independently, Sanity will create a dependency on engineering that platforms like Storyblok (which scored 85 for visual editing) handle natively.
The "Headless" Promise Has a Marketing Gap
Being headless is Sanity's architecture. It's also the source of its biggest gap for marketing teams. SEO Tooling: 55. No built-in sitemap generation, no meta tag management UI, no SEO scoring. Performance Marketing: 35. No form builder, no CTA management, no conversion tracking. Built-in Analytics: 30. No content performance dashboards, no page view tracking, no engagement metrics.
These capabilities exist in the DXP world that Sanity competes adjacent to, and their absence means that marketing teams need to assemble and integrate third-party tools for capabilities that platforms like Optimizely or AEM include out of the box. The headless architecture makes all of this possible through integration, but "possible through integration" is very different from "included."
Where Sanity Underpromises
Platform Velocity Is Quietly Impressive
Sanity scored 75.1 for Platform Velocity, which includes a Release Frequency of 82, Changelog Quality of 80, and Customer Momentum of 78. The Studio ships weekly updates. The auto-update system means your Studio stays current without redeployment. Content Releases (shipped in late 2024) added coordinated multi-document scheduling that was a genuine gap. Content Agent (GA in early 2026) brings AI-powered content operations with schema awareness.
The velocity story doesn't get enough attention because Sanity doesn't do splashy annual product launches. It ships continuously, and the cumulative effect over a year is significant. The platform in March 2026 is meaningfully more capable than the platform in March 2025.
Compliance Is Stronger Than Expected
Sanity scored 65.7 for Compliance Trust, which includes SOC 2 Type II at 82, GDPR at 80, and Data Residency at 75. For a platform that started as a developer tool, that's a serious compliance posture. SOC 2 Type II is independently audited. GDPR compliance includes data residency in the EU (Belgium, GCP europe-west1). HIPAA scored 55, reflecting BAA availability under enterprise agreements.
These scores won't satisfy the most stringent regulated industries, where AEM (76.8) and Salesforce (87.4) lead. But they're more than adequate for most commercial enterprise use cases, and they're significantly ahead of open-source alternatives like Strapi (43.9) or Payload CMS (29.1).
The Content Lake Architecture Is Genuinely Differentiated
Sanity's real-time, document-oriented Content Lake is not just a database with an API on top. Scalability Architecture scored 82. API Performance scored 80 with 32ms response times and CDN-cached GROQ queries. Multi-Channel Output scored 90, reflecting the genuine portability of Portable Text and structured JSON content across any delivery surface.
The architecture enables use cases that traditional CMS platforms struggle with: real-time content syndication, headless commerce content layers, AI-powered content pipelines, and content-as-data applications that treat the CMS as infrastructure rather than a destination. This is the "Content Operating System" vision delivered at the infrastructure level, even when the application-level tooling doesn't fully realize it yet.
Critical Cautions
Content Workflows Need Significant Improvement
Sanity scored 55 for Content Workflows. The draft/published binary state is insufficient for enterprise content operations. There are no multi-step approval chains, no configurable workflow stages, no visual workflow builder, and limited audit trails beyond basic document history.
Content Releases (Enterprise only) address the scheduling and coordination gap, but they don't solve the governance gap. If your organization requires "author submits, editor reviews, legal approves, publisher schedules" workflows, you will need to build that logic yourself or use third-party tooling.
This is Sanity's most conspicuous enterprise gap. Platforms like AEM (88 for workflows), Contentstack (strong workflow tooling), and even WordPress VIP provide more mature editorial governance out of the box.
Concept Complexity Is Real
Sanity scored 28 for Concept Complexity, which might surprise people who think of it as a "simple" platform. The concepts aren't hard individually, but the total surface area is real: schema-as-code, GROQ query language, Portable Text serialization, Studio customization patterns, Content Lake architecture, webhook/function event system, and the Presentation tool's overlay model.
For experienced JavaScript/TypeScript developers, the ramp-up is fast. For teams without frontend engineering depth, or for content authors being introduced to structured content for the first time, the learning curve is steeper than marketing implies. Cross-Functional Complexity at 28 confirms that getting non-technical team members productive in Sanity requires deliberate onboarding.
Enterprise Support Tiers Are a Known Weakness
Sanity scored 28 for Support Tier Quality and 58 for Issue Resolution Velocity. Community support is strong (80), reflecting an active and helpful developer community. But enterprise-grade support with dedicated account management, guaranteed response times, and priority escalation requires Enterprise plan pricing that isn't publicly disclosed.
For teams that can self-serve through documentation and community channels, this isn't a problem. For enterprise buyers accustomed to the support tiers that come with AEM or Sitecore engagements, the gap is noticeable.
Localization Is Plugin-Dependent
Sanity scored 60 for Localization Framework and 55 for Translation Integration. There is no native field-level localization. Document-level localization via the @sanity/document-internationalization plugin works but creates content duplication. Translation management relies on third-party connectors rather than built-in TMS integration.
For teams managing content in 2 to 3 languages, the plugin approach is workable. For enterprises managing 20+ locales with complex translation workflows, Sanity's localization story is less mature than Contentful, Contentstack, or AEM.
Why You Would Select Sanity
Sanity is the right choice when these conditions align:
Your team has strong frontend engineering capability, ideally working in React, Next.js, or a modern JavaScript framework. Sanity's value multiplies when developers can leverage the schema-as-code model, extend Studio, and integrate GROQ into their data layer.
Your content model is complex and needs to serve multiple channels. Portable Text and structured content modeling are genuinely best in class, and they matter most when content flows to web, mobile, email, and other surfaces from a single source.
You value developer experience and operational simplicity over turnkey marketing features. Sanity will not give you drag-and-drop page building or built-in personalization. It will give you the fastest path from idea to production for content-driven applications.
Budget discipline matters. At $15/user/month for Growth and a generous free tier, Sanity's cost profile makes enterprise-class content infrastructure accessible to teams that can't justify six-figure annual licensing.
Content collaboration is a daily workflow. Real-time co-editing, comments, and the Content Agent bring a collaborative model that most enterprise CMS platforms can't match.
What You Should Consider Instead
For Marketing Team Autonomy
Storyblok (Capability: 56.2, Cost Efficiency: 72.7) provides the drag-and-drop visual editing that Sanity lacks. If your primary users are marketers who need to build and modify pages without developer involvement, Storyblok's visual editor is a core feature, not an afterthought.
HubSpot CMS (check the Scorecard for current scores) offers integrated marketing automation, landing pages, forms, and analytics in a single platform. For marketing teams that want everything in one place, HubSpot eliminates the integration overhead that Sanity requires.
For Enterprise Governance and Workflows
Contentstack (Capability: 67.9, Cost Efficiency: 55.9) delivers stronger enterprise workflow management, more robust localization, deeper commerce integrations, and a more mature partner ecosystem. If you need headless architecture with enterprise governance, Contentstack bridges the gap that Sanity leaves open.
Contentful (Capability: 63.8, Cost Efficiency: 65.3) offers a more mature enterprise headless CMS with a larger marketplace of integrations and broader enterprise adoption. The content modeling is less flexible than Sanity's, but the overall platform maturity is higher for enterprise operational needs.
For Full DXP Capabilities
SitecoreAI (Capability: 69.6, Cost Efficiency: 36.4) provides personalization, experimentation, analytics, and marketing automation that Sanity cannot match. If your requirements include audience targeting and content testing, SitecoreAI delivers those capabilities natively.
AEM (Capability: 76.6, Cost Efficiency: 20.2) remains the most capable platform in the market for organizations that need the full Adobe ecosystem. As we covered in our AEM Scorecard Analysis, the cost is significant, but so is the capability.
The Bottom Line
Sanity earned the highest customer sentiment score of any platform in the DXP Scorecard at 89 out of 100. That score reflects something important: the people who choose Sanity tend to be the right people for Sanity, and they're deeply satisfied with what they get.
The platform delivers best-in-class content modeling, real-time collaboration, developer experience, and cost efficiency. It does not deliver personalization, marketing automation, enterprise workflows, or visual page building. That's not a gap that Sanity is trying to close. It's a deliberate scope decision that defines who the platform serves.
The organizations that thrive on Sanity are engineering-led teams building content-driven applications where the content model matters, the frontend is custom, and the team has the technical depth to leverage what Sanity uniquely provides. For those teams, nothing else in the market matches the combination of flexibility, velocity, and cost efficiency.
The organizations that struggle on Sanity are the ones that expected a traditional CMS with modern architecture. They wanted drag-and-drop for marketers, built-in personalization, and turnkey campaign management, and they found a platform that assumes someone will build those things rather than providing them.
The best platform decisions come from honest alignment between what you need and what a platform actually provides. Sanity is honest about what it is. The question is whether you're honest about what you need.
The full scoring breakdown, including all 104 criteria and peer comparisons, is available at dxpscorecard.com/platform/sanity.
