# Directus vs Storyblok: self-hosted data platform or hosted content platform

*Source: https://www.editorstack.cc/compare/directus-vs-storyblok — last updated 2026-08-19. Licensed CC BY 4.0 with attribution to EditorStack.*

## Summary

- Directus is self-hosted and database-shaped: it wraps an existing SQL schema and is free below $5M annual revenue under a BSL 1.1 licence.
- Storyblok is hosted and content-shaped, with a visual editor that is more mature than Directus's preview and overlay features.
- If data must stay on your infrastructure, Storyblok is not a candidate; if editorial experience is the priority, Directus is the weaker tool.

## At a glance

| Product | Type | Licence | Frameworks | Bundle (min+gzip) | Price from | Self-hosted | White label | Score |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| [Directus](https://www.editorstack.cc/libraries/directus) | cms | BSL-1.1 | Any (framework-agnostic) | Not measurable | from $99/mo | Yes | Yes | not scored |
| [Storyblok](https://www.editorstack.cc/libraries/storyblok) | cms | Proprietary | Any (framework-agnostic) | Not measurable | Free tier, paid plans undisclosed | No | No | not scored |

## The constraint that usually decides

Ask whether content may leave your infrastructure.

If the answer is no — health, finance, government, or a procurement process that treats every new
sub-processor as a project — Storyblok is out and the comparison is over. Directus is one of the few
products in this dataset that clears that bar.

If the answer is yes, the comparison becomes about editorial experience, and Storyblok is the
stronger product.

## Where Directus wins

**Self-hosting.** The whole platform on infrastructure you control.

**Your existing database.** Directus wraps a SQL schema you already have rather than requiring
migration into a vendor content model.

**White-label admin.** The interface can carry your customer's branding, which matters for agencies
and embedded-admin scenarios.

**Free below the revenue threshold**, with the full product rather than a cut-down tier.

**No per-space or per-seat meter**, which changes the arithmetic for teams with many projects.

## Where Storyblok wins

**A mature visual editor.** This is the feature Directus is still growing into.

**Editorial workflow.** Roles, drafts, releases, scheduling — designed for content teams.

**Managed translations**, which Directus expects you to model.

**Nothing to operate.** No upgrades, no backups, no uptime responsibility.

**Content-shaped modelling** rather than schema-shaped, which is more forgiving when your database
was designed for an application rather than for content.

## The licence question

Directus is BSL 1.1: source-available with a usage restriction, converting to GPLv2 three years after
each release. Below $5M in total annual revenue and funding, self-hosting is free. Above it, you need
a commercial licence with no published price.

This is a legitimate model and it is not open source in the OSI sense. Establish which side of the
threshold you are on, and whether you expect to cross it during the project's life, before anything
technical is discussed.

## The operational cost nobody budgets

Self-hosting is the feature and the cost. Someone upgrades Directus, someone runs the database
backups, someone is on call when the admin is down at month-end close.

For organisations that already operate infrastructure, that is marginal. For a five-person startup, it
is a real distraction from the product, and the hosted option is usually the better trade even when
the licence is free.

## Migration

Directus to Storyblok means exporting your tables and modelling them as stories — a genuine content
migration, and the moment you discover how much of your schema was application-shaped rather than
content-shaped.

Storyblok to Directus means designing a schema and transforming stories into rows, which is the easier
direction technically and loses the editorial workflow.

## Verdict

Data residency or an existing SQL database as the starting point: Directus, with the licence threshold
checked first.

Editorial experience and translation workflow as the priority, with no self-hosting requirement:
Storyblok — and compare it with [Sanity](/compare/storyblok-vs-sanity) if developer control matters
as much as editor experience.

## Decision checklist

1. **May content leave our infrastructure?** A no ends the comparison in Directus's favour.
2. **Which side of the $5M revenue threshold are we on, now and in two years?**
3. **Do we already have a SQL schema worth wrapping?** That is Directus's strongest case.
4. **Who operates the deployment?** Self-hosting is a standing commitment, not a one-off.
5. **How mature does the visual editing need to be?** Storyblok's is further along.

## The number that matters

$5 million — the total annual revenue and funding threshold in Directus's BSL 1.1 licence. Below it,
you have a capable self-hosted platform for free. Above it, you have a vendor negotiation with no
published price, and teams that assumed "open source" discover this at exactly the wrong moment.


## Frequently asked questions

### Is Directus free?

Free to self-host below $5M in total annual revenue and funding, under BSL 1.1 — a source-available licence, not OSI open source. Above that threshold a commercial licence is required and priced through sales.

### Which has better visual editing?

Storyblok. Its visual editor is a mature part of the product; Directus's preview and editable overlays are newer and less complete.

### Can Storyblok be self-hosted?

No. It is a hosted platform, which is the point at which many regulated organisations stop considering it.