Storyblok Pricing 2026: Free Starter, Growth $99, Growth Plus

Storyblok pricing trips up teams because the free tier is genuinely usable — until one specific limit hits and suddenly you're looking at a four-figure annual bill. This post breaks down every tier as of October 2026: what's included, what the hard ceilings are, and which usage pattern pushes you past each one.

If you're comparing across the whole headless CMS landscape, I've already written a Headless CMS Pricing Comparison 2026 covering Sanity, Contentful, Payload, and Strapi side-by-side. This post zooms in on Storyblok specifically.

How Storyblok structures its pricing

Storyblok sells on several axes: seats (users who log into the editor), locales (languages per space), API requests (calls to their Content Delivery API), and traffic (asset and API bandwidth). There's also a soft limit that catches people by surprise: the number of spaces (separate CMS projects). Self-serve plans are priced per space, not per organisation, which matters for agencies managing multiple clients.

Paid plans are billed per space per month, and annual billing gets you roughly one month free.

Storyblok tier breakdown

Prices reflect Storyblok's pricing page as of October 2026. Storyblok has reshuffled its plans before, so check storyblok.com/pricing before you quote a client.

Starter (free) tier: the real limits

The free Starter plan is genuinely useful for a personal project or a proof of concept: one editor seat (two at most), two locales, 100,000 API requests, and 100 GB of traffic per month. The API request limit is the thing people tend to underestimate.

Every uncached request to Storyblok's Content Delivery API counts. If your Next.js site fetches 12 stories on the homepage with no caching, that's 12 requests per page view. At 10,000 page views a month you've burned through 120,000 requests — already over the free limit. ISR and caching at the Vercel or CDN layer help a lot, because cached pages don't hit Storyblok again until they revalidate. Anyone building a production site with real traffic and no caching strategy will exhaust the free tier quickly.

The seat cap is the other hard wall. Starter tops out at two seats, so the moment a client team of three needs logins, you're on Growth.

Growth at $99: the real starting point for client work

Growth is where Storyblok becomes viable for most agency and product team projects. Five included seats cover a small team (developer, editors, manager), and extra seats at $15 each go up to a maximum of 10. The 1M API request allowance is enough for most mid-size sites, and you can buy more up to 5M.

The missing feature at this tier is custom roles. If a client needs a content reviewer role that can publish but not delete, or a translator role locked to specific locales, that's a Premium feature, not a self-serve one. This is a common reason teams outgrow the self-serve plans earlier than expected.

Locales are an add-on here: Growth includes two, and each extra locale is $20/month. A product targeting EN, DE, FR, ES, and PT pays for three extra locales.

Growth Plus at $349: what you're actually buying

Growth Plus is the fixed-price bundle: 15 seats, 10 locales, 4M API requests, and 1 TB of traffic, with no add-ons to calculate. It's the better deal once a Growth space would need several extra seats and locales — but it still doesn't include custom roles, environments, or release management. Those sit on the custom-priced Premium and Elite plans.

For a content-heavy site with a large editorial team and many locales but simple permissions, Growth Plus is the honest starting point — not Growth.

Premium and Elite: what triggers the call

Premium and Elite pricing is custom and negotiated. The features that push you there are: custom roles and workflows, environments, release management, GraphQL, SSO and SCIM, multiple spaces, and higher uptime SLAs. If any of those are on your requirements list, you're in sales territory.

Storyblok doesn't publish these prices. Expect a significant step up from Growth Plus, and get a quote early if any of those features are requirements.

The costs that don't appear in the table

Multiple spaces. If you're an agency running three client projects, you pay per space. Three Growth spaces is $297/month at monthly billing — almost the price of one Growth Plus space. Multi-space access is a Premium/Elite feature. This makes Storyblok materially more expensive for agencies than for product companies running one space.

Traffic. Storyblok's image service (resizing, format conversion, focal-point crops) is bundled, but asset delivery counts toward your monthly traffic allowance. On Growth, extra traffic is $75 per 250 GB. Most small sites never hit it, but check it if you're serving heavy media.

API request ceilings. Each plan has a maximum monthly request count. Check with Storyblok how your plan handles traffic spikes over that limit before you launch, so a spike doesn't degrade your site until you upgrade or the month resets.

Which tier fits which project

For a solo developer's portfolio or small blog: Starter is fine. For a client handoff with one or two editors and light traffic: Starter can work, but expect to upgrade once the team grows. For a product team with three to ten editors and one or two locales: Growth, budgeting for seat and locale add-ons. For a larger team needing many seats and locales: Growth Plus. Anything with custom roles, staging environments, SSO, or compliance requirements: Premium or Elite.

The comparison that surprises most teams is Storyblok against Sanity's Growth tier ($15 per seat/month with a generous free API allowance). At five editors, Sanity's total is $75/month versus Storyblok Growth's $99 base — though Storyblok bundles a visual editor experience that Sanity provides differently (through its Presentation tool). That trade-off deserves its own comparison post.

---

Evaluating a CMS for your project?

If you're comparing Storyblok against Sanity or Contentful and want a developer's honest take on what fits your use case, I'm available for a scoping call. I specialise in Sanity + Next.js builds and can help you pick the right stack before you commit.