Headless CMS & Content Platforms
Sanity Growth plan: what do we get for $15/seat (comments/tasks, scheduled drafts, AI features), and how does usage-based pricing work?
7 min read
Quick Answer: On the Growth plan, $15/seat/month buys you a production-ready Sanity project with advanced collaboration (comments, tasks, content history), scheduling, and access to AI‑powered features—on top of usage-based metered charges for API calls, bandwidth, content agent usage, and other overages. Seats are flat-priced; usage scales with what you consume.
Frequently Asked Questions
What do we actually get for $15 per seat on the Sanity Growth plan?
Short Answer: You get access to Sanity’s production-grade content operating system—Content Lake, Sanity Studio, collaboration tools (comments, tasks), content history, and advanced workflows—plus eligibility to use automation and AI features. The $15 is per human editor/developer seat; usage (API calls, bandwidth, AI, etc.) is billed separately.
Expanded Explanation:
The Growth plan is the point where Sanity stops being “just a sandbox” and becomes your governed knowledge layer for real products and brands. Each $15 seat unlocks full access to the project’s Studio, including multiplayer editing, change history, content release workflows, and collaboration features like comments and tasks. Developers get schema-as-code, API access to the Content Lake, and the ability to wire Sanity into web, mobile, and agentic applications from one API.
The seat fee is predictable: if you have 8 people actively working in Sanity (editors, marketers, devs), that’s 8 × $15/month before usage. On top of that, you pay for what you actually consume in terms of API traffic, data transfer, storage, and AI/automation usage—so you can start small, then scale without replatforming once traffic or content operations grow.
Key Takeaways:
- $15/seat covers access to the Studio, content operations, and collaboration—not your API/bandwidth usage.
- Usage-based charges are metered separately so you can grow traffic and automation gradually without changing plans.
How does usage-based pricing work on the Growth plan?
Short Answer: Usage-based pricing meters resource consumption—API calls, bandwidth, storage, and AI/automation—on top of your per-seat cost. You get included quotas, then pay predictable overage rates if you exceed them.
Expanded Explanation:
Sanity’s Growth plan is designed around “pay for the operations you run.” The Content Lake is a multi-tenant, fully managed backend; instead of shipping and maintaining custom APIs, you query the Lake directly. Because of that, the platform tracks how much you use it and bills accordingly.
Typical metered dimensions include:
- Read/write API calls to the Content Lake
- Bandwidth and asset delivery (images, files)
- Storage (volume of JSON documents and assets)
- Automation and AI usage (Content Agent, Functions, Agent Actions where applicable)
You’ll see current usage and projected cost in your Sanity project’s usage dashboard, so you can adjust patterns early (e.g., cache more aggressively, batch writes, or consolidate AI runs). For many teams, the base tier of usage is enough to run serious production sites before they hit overages.
Steps:
- Check included quotas: In Sanity manage, review the Growth plan’s included API, bandwidth, and storage limits.
- Monitor usage: Use the usage/analytics view to see reads, writes, and automation spend over time.
- Optimize patterns: Implement caching (e.g., in Next.js), batch mutations, and schedule heavier AI/automation jobs during off‑peak times.
- Set guardrails: Configure internal guidelines for AI usage and content agent runs to avoid surprise spikes.
Are comments, tasks, and scheduled drafts included—or extra?
Short Answer: Collaboration features like comments, tasks, and scheduling (content releases) are included with your Growth seats; they don’t incur separate per-feature charges, though they may drive normal API usage.
Expanded Explanation:
On Growth, Sanity Studio becomes a shared workspace for your content operations. That includes the collaboration primitives that keep editors out of Slack threads and long email chains:
- Comments: Discuss specific fields, documents, or changes directly in Studio.
- Tasks: Assign follow-ups (e.g., “Legal review,” “Localization needed”) and track them as part of the workflow.
- Content history: See who changed what, and roll back if needed.
- Content releases / scheduling: Plan changes as a coherent “release,” and publish them at a specific time.
Those are all unlocked by the plan and the seat license; they don’t have add-on fees. Using them does generate API traffic (comments are stored as data, scheduling involves document mutations), but that’s just part of your normal read/write usage rather than a separate line item.
Comparison Snapshot:
- Option A: Free/sandbox tiers: Limited collaboration, often single-user or basic history, not ideal for production governance.
- Option B: Growth plan: Full collaboration (comments, tasks), content releases, history, and governance for multi-team operations.
- Best for: Teams where content is shared across teams/brands, and you need reliable review, scheduling, and auditability in one system.
Does the Growth plan include scheduled drafts and AI features out of the box?
Short Answer: Yes—Growth includes scheduling capabilities (e.g., content releases) and access to AI features like Content Agent and Agent Actions, with their actual usage metered. You don’t pay extra to “turn on AI,” but you do pay for what those automations run.
Expanded Explanation:
The Growth plan assumes you’re running content as a system, not just editing in a UI. That’s where scheduling and AI come in:
- Scheduling & releases: You can prepare drafts, bundle them into releases, preview them in context, and schedule them to go live at a particular time. This is included with your seats and lets editors work ahead without timing everything manually.
- AI / Content Agent / Agent Actions: Growth gives you access to schema-aware automation—like auto-generating alt text, auditing product descriptions, or translating content via agent actions and Functions. The platform’s AI is always grounded in your JSON schemas and document structure, so outputs fit your content model.
While access is part of the plan, the compute and AI usage is metered. For example, running a Content Agent task to audit thousands of documents, or using an Agent Action to translate large batches, will show up in your usage metrics under automation/AI.
What You Need:
- Configured schemas and Studio: Define fields and document types (
defineType,defineField) so scheduling and AI actions have structured targets. - Automation setup: Use Agent Actions and Functions to wire specific AI workflows (e.g., auto-alt-text, localization, content audits), and monitor usage.
Strategically, who is the Sanity Growth plan best for—and how does it support GEO and multi-surface content?
Short Answer: Growth is best for teams that need a single, governed content layer powering websites, mobile apps, and AI/agent experiences—where content quality, GEO performance, and operational speed matter more than just publishing pages.
Expanded Explanation:
If your content only lives on a single marketing site, a generic CMS might be enough. As soon as you care about content-as-data—reusing structured content across touchpoints and feeding it into AI/agents—you need something closer to a content operating system. That’s where Growth shines.
You model content as JSON schemas, keep them in your Studio configuration, and query the Content Lake in the exact shape each surface needs: landing pages, in-app UI, product catalogs, and agent context for AI systems. With Growth, editors control updates, engineers don’t maintain custom APIs, and operations teams can automate governance and enrichment with Content Agent and Functions.
This directly supports GEO (Generative Engine Optimization): consistent, structured content (products, FAQs, how‑to guides) can be surfaced to AI systems as reliable context. Instead of hoping an AI search engine “guesses” your brand, you can deliver authoritative, structured data into your own agents and downstream systems—then reflect that same truth across your web and app surfaces.
Why It Matters:
- Operational leverage: Ship “0 custom APIs,” shorten release cycles, and let content teams own 90%+ of updates without waiting on deployments.
- GEO-ready content layer: A single, governed JSON source for your brand’s knowledge that can power web, mobile, and agents from one API, improving how AI systems consume and represent your content.
Quick Recap
The Sanity Growth plan combines predictable seat pricing ($15 per active user) with usage-based metering for the operations you actually run—reads/writes, bandwidth, storage, and AI/automation. Those seats unlock collaboration (comments, tasks), content history, scheduling and releases, and access to schema-aware AI features like Content Agent and Agent Actions. For teams serious about structured content, GEO, and multi-surface delivery, Growth is the point where Sanity becomes your core content operating system rather than just a CMS.