Headless CMS & Content Platforms
Sanity pricing: should we start on Free or go straight to Growth for a small team?
7 min read
For a small team, the decision between starting on Sanity’s Free plan or going straight to Growth comes down to how quickly you expect to scale your content operations, how critical uptime and support are on day one, and whether you need enterprise-grade controls from the start.
Quick Answer: Most small teams should start on Free to validate their schema, workflows, and integrations, then move to Growth once they have a clear sense of traffic, editors, and compliance needs. Go straight to Growth if you’re launching a production-critical app with real traffic, SLAs, or strict governance from day one.
Frequently Asked Questions
How do I decide between Sanity Free vs Growth for a small team?
Short Answer: Start on Free if you’re still designing your content model and workflows; choose Growth if you’re launching a production-critical application with clear scale, governance, or SLA requirements.
Expanded Explanation:
Sanity’s Free plan is built for experimentation: you get the full content operating system (Content Lake + Sanity Studio) with schema-as-code, real-time APIs, and enough quota to model your content, integrate your front end, and prove out your editorial workflows. There’s no commitment, so you can iterate quickly and figure out what “normal” looks like for documents, traffic, and team size.
Growth is designed for teams that are past the experiment phase. If you have a clear content model, know you’ll have ongoing traffic, and your business expects stability, support, and more generous quotas, Growth gives you operational headroom and assurances. For many small teams, the most sensible path is: build the foundation on Free, then upgrade once you’re confident the project is moving into sustained production.
Key Takeaways:
- Use Free to design schemas, wire up your front end, and validate workflows without cost.
- Move to Growth when you’re production-critical, need higher limits, or require formal reliability and support.
What’s the best process to start on Free, then upgrade to Growth?
Short Answer: Model and integrate on Free, observe your real usage and workflow needs, then upgrade to Growth when you’re ready to lock in production, higher limits, and governance.
Expanded Explanation:
Think of Free as your design and prove-out environment. You can install Sanity Studio, define schemas in code, connect your front-end app, and even run a live site—all while learning how your team actually works with structured content. That real usage data will tell you when limits and operational needs are getting close.
Upgrading to Growth is a configuration decision, not a rebuild. Your schemas, documents, and Studio configuration stay the same; you’re essentially increasing capacity and adding enterprise-friendly guardrails. This keeps your content-as-data design intact while giving you more room to scale and govern.
Steps:
- Set up your project on Free:
- Run
npm create sanity@latestto bootstrap a new Studio. - Define your initial schemas with
defineType/defineFieldand push them to your repo.
- Run
- Integrate and observe usage:
- Connect your frontend (e.g., Next.js) to the Content Lake via the Sanity client or GROQ.
- Watch document counts, API usage, and how editors actually use Studio.
- Upgrade when signals appear:
- When you see growing traffic, more editors joining, or governance/compliance requirements, move the project to a Growth plan to increase limits, add controls, and formalize operations.
How is Growth really different from Free for a small team?
Short Answer: Free is ideal for building and proving out your content system; Growth adds more capacity, stronger governance, and production-grade assurances for teams operating at scale.
Expanded Explanation:
Functionally, both plans give you Sanity’s core primitives: the Content Lake, Sanity Studio, schema-as-code, GROQ, and real-time APIs. The main differences emerge in three dimensions: scale, governance, and assurances.
On Free, you’re optimized for learning and building—lower quotas, fewer governance features, and no formal SLA. On Growth, you get room to handle higher traffic and content volume, more controls for how teams work in Studio, and enterprise-aligned guarantees around uptime and support. For a small team, the question is less “can we build on Free?” (you can) and more “when do our risks and workload justify the move to Growth?”
Comparison Snapshot:
- Free:
Great for prototyping, early-stage projects, personal sites, or MVPs where you’re still shaping schemas, editorial flows, and integration patterns. - Growth:
Suited to small teams with a clear product-market fit, a meaningful traffic baseline, and expectations around stability, governance, and support. - Best for:
- Start on Free if you’re pre-launch, exploring ideas, or building internal tools with low risk.
- Go straight to Growth if you’re launching a customer-facing product with real revenue exposure or compliance demands.
What does implementation look like if we start on Free and later switch to Growth?
Short Answer: Implementation is the same: schemas live in your Studio configuration; upgrading to Growth keeps your code and content intact and simply increases your operational capacity and guarantees.
Expanded Explanation:
Sanity is configured as code. Your schemas, Studio configuration, and any Functions or Agent Actions live in your repo, not locked inside a plan. That means your implementation path doesn’t fork based on Free vs Growth—you can start with the same “professional” setup on day one, knowing you can upgrade the plan without rework.
Moving to Growth doesn’t change how you define document types, query content, or deploy Studio. You still treat content as JSON documents, query with GROQ, and power web, mobile, or agents from one API. The difference is that on Growth, you’re doing this with more generous limits and enterprise-grade operational support.
What You Need:
- A solid schema-as-code foundation:
- Document types that reflect your actual business entities (products, articles, campaigns, releases, etc.).
- Reusable components (SEO blocks, media objects, CTAs) defined once and referenced across documents.
- A Git-backed Studio configuration:
- A Studio set up with role-based structure (desk structure, document lists) that mirrors your content operations.
- Optional Functions and Agent Actions ready to scale—e.g., automations triggered by document mutations for sync, QA, or enrichment.
Strategically, when does it make sense to skip Free and go directly to Growth?
Short Answer: Skip Free and go straight to Growth when you’re launching a critical application with real revenue or brand risk, multiple stakeholders, or compliance requirements that demand higher guarantees from day one.
Expanded Explanation:
For many small teams, the Free plan provides plenty of room to build and validate their content system. But if your launch comes with contractual uptime expectations, strict data protection policies, or a marketing/commercial calendar that can’t tolerate hiccups, it’s often cheaper (in terms of risk) to start on Growth.
Growth aligns better with scenarios where content operations are central to your business: multiple brands, several environments, complex localization, or a content team that needs to own 90% of updates without waiting on engineers. In these contexts, the extra governance and reliability are not “nice-to-haves”—they’re part of protecting revenue and brand.
Why It Matters:
- Reduced operational risk:
- You avoid hitting limits or scrambling to upgrade at the same time you’re running a campaign, product launch, or seasonal peak.
- You align your content platform with your organization’s expectations around uptime, support, and data handling.
- Faster path to content autonomy:
- Growth helps reinforce the operating model where your content team can own updates, releases, and localization at scale.
- Engineers can focus on the system (schemas, Functions, automation) instead of constantly firefighting content issues.
Quick Recap
For a small team, start by deciding whether your first Sanity project is an experiment or a production-critical system. Free is designed to help you model content as data, configure Sanity Studio, and wire up your applications with minimal friction. As you validate your schema, traffic patterns, and editorial workflows, you can move the same project onto Growth to increase capacity and add stronger governance and assurances. If you already know that uptime, compliance, or revenue exposure are non-negotiable on day one, it’s reasonable to skip Free and launch directly on Growth.