Sanity vs Payload CMS vs Keystatic: Pricing Comparison 2026
By Nayan Kyada · · 6 min read
Part of The Sanity + Next.js Guide
Choosing between Sanity, Payload CMS, and Keystatic almost always comes down to pricing at some point in the conversation. All three have free paths to production, but the cost curves diverge sharply once you add seats, environments, or serious traffic. Here is what you actually pay at each tier in 2026.
Why this comparison matters
Sanity is API-first, fully hosted, and charges by usage and seats. Payload is open-source and self-hosted by default, shifting cost to infrastructure. Keystatic is Git-based and pushes most cost to your Git host and optional Keystatic Cloud. They solve overlapping problems — structured content for Next.js apps — but they are not interchangeable once you account for team size, deployment complexity, and who pays the ops bill.
I've scoped projects on all three in the last twelve months. The sticker price rarely tells the full story.
Free tier limits side by side
| Feature | Sanity Free | Payload Free (self-hosted) | Keystatic Free |
|---|---|---|---|
| Hosted by vendor | Yes | No | Optional (Cloud) |
| Datasets / projects | 2 projects | Unlimited (self-host) | Unlimited repos |
| Users / editors | 3 non-admin users | Unlimited | Unlimited |
| API requests | 250k CDN req/month | Unlimited (your server) | Git API limits apply |
| Assets / storage | 5 GB assets | Your own storage | Git LFS or external |
| GROQ / query API | Included | REST + GraphQL included | N/A (Git reads) |
| Environments (staging) | 1 (single dataset) | Separate deploys | Branch-based |
| Sanity Studio hosting | Included | Self-host | Self-host |
Sanity's free tier is genuinely useful for a single small project. Three non-admin users covers most founder-plus-one-editor setups. The 250k CDN request ceiling sounds large but a Next.js ISR site with moderate traffic and preview calls can brush against it faster than expected — especially once you add live preview sessions.
Payload's free tier is unlimited in every meaningful sense because you own the server. But "free" here means you are running a Node.js process somewhere. A Railway Hobby plan ($5/month), a Render free-tier instance (with cold starts), or a VPS at $6/month from Hetzner — that's your baseline, not zero.
Keystatic's free tier is genuinely zero if you stay on the open-source path and store content in your Git repo. GitHub or GitLab is the database. For most small sites, this is fine. For large content libraries (hundreds of documents with media), Git history bloat becomes a real problem.
Paid tier thresholds
| Plan | Sanity | Payload Cloud | Keystatic Cloud |
|---|---|---|---|
| Entry paid | $15/month (Growth) | $25/month (Starter) | $19/month (Team) |
| What triggers upgrade | >3 non-admin users, >250k CDN req, >5 GB assets | Wanting managed hosting | Wanting managed hosting beyond GitHub |
| Per-seat cost | $15/seat above included | Flat project pricing | Flat team pricing |
| Staging environment | $15/month extra dataset | Separate project deploy | Branch-based (free) |
| API rate limits | Generous on Growth | Your server limits | Git API limits |
| Enterprise | Custom (typically $1k+/month) | Custom | Not yet a clear path |
Sanity's growth plan at $15/month per seat is the most common pain point I hear about. A five-person editorial team — three editors, one PM, one developer — sits at $45–60/month before you've counted bandwidth or asset storage overages. Add a staging dataset and you're at $75/month. That's not outrageous for a professional content operation, but it surprises teams coming from self-hosted WordPress.
Payload Cloud launched properly in 2024 and has matured. The Starter tier at $25/month gives you a managed MongoDB Atlas instance, file storage, and a hosted admin UI. It removes the ops burden without the per-seat cost structure. If your team is four developers with no non-technical editors, Payload Cloud is often cheaper than Sanity Growth.
Keystatic Cloud is the newest entrant. At $19/month for teams it's competitive, but Keystatic's architecture means it only makes sense for content that lives happily in a Git repo — flat Markdown or YAML files, reasonable document counts, no heavy asset management. For a developer blog or docs site it's excellent. For a marketing team managing hundreds of landing pages with hotspot images and scheduled publishing, it's the wrong tool regardless of price.
Self-hosted cost reality for Payload
Payload's self-hosted path deserves its own accounting. At minimum:
- Compute: Railway Pro ($20/month), Render Starter ($7/month), or a $6 Hetzner VPS
- Database: MongoDB Atlas free tier covers small projects; M10 cluster (production-appropriate) starts at ~$57/month
- File storage: AWS S3 free tier for the first year, then ~$0.023/GB/month
- Backups, monitoring: optional but real costs in any serious deployment
A realistic production Payload setup runs $30–100/month before you hire anyone to maintain it. That's still competitive with Sanity Growth for large teams, but it's not free infrastructure.
Total cost of ownership at three scales
| Team size | Sanity | Payload (self-hosted) | Payload Cloud | Keystatic |
|---|---|---|---|---|
| Solo dev, personal project | $0 | ~$6–12/month | $25/month | $0 |
| 3-person startup (2 editors) | $0–15/month | ~$30–60/month | $25/month | $0–19/month |
| 8-person team (5 editors) | ~$75/month | ~$60–100/month | Custom | $19/month |
| 20+ editors, multi-locale | $200+/month | $100–150/month infra | Custom | Not recommended |
Which one to pick based on budget
Sanity wins on editor experience and GROQ flexibility. The cost is predictable once you've settled your seat count. For teams where non-technical editors are the majority of users, the per-seat model is worth it — the Studio quality keeps support tickets low.
Payload wins on total cost for developer-heavy teams or when you need full control of your data layer. Self-hosting has a real ops cost, but if you're already running infrastructure (many product teams are), adding Payload is marginal. Payload Cloud closes the ops gap at a flat rate.
Keystatic wins for content-in-Git workflows — docs sites, developer blogs, small marketing sites where a developer is close to the content. The pricing is lowest, the architecture is simplest, and branch-based staging is built in for free. It is the wrong choice when editors outnumber developers or when content is too large for a Git repo.
None of these is universally cheapest. The gap between them matters most at the 5–20 editor range, where Sanity's per-seat cost accumulates and Payload's self-hosting complexity starts to feel justified.