— a sovereign-by-design headless CMS
A French, Belgian, German, Dutch, Luxembourgish, or Swiss data plane the customer can choose. Audit chain hash signing, residency proofs, sub-processor register, exit plan export — all auto-generated. Storyblok-grade visual editing alongside Sanity-grade schema-as-code, in one product.
— the wedge
Estøkad is a category of one because of the combination, not any single feature. Each pillar holds independently; the three together are why regulated buyers pick us over Contentful, Storyblok, or Sanity.
01
Pick Brussels, Frankfurt, Paris, Amsterdam, Luxembourg, or Zurich. Customer content never leaves the chosen country. No cross-region replication. No Cloud Act exposure. The brand promise, not a region label.
02
Audit chain with hash signing and daily Merkle roots. Residency proofs every UTC day. Sub-processor register. Exit plan export. The DORA evidence pack assembles from these on demand — not from a Confluence page maintained by a consulting partner.
03
defineType() in TypeScript for the engineering team. Visual schema builder + structured editor + visual edit overlay for content designers. One product, not two licences. The Storyblok experience, the Sanity ergonomics.
— who Estøkad is for
Insurance, banking, government, regulated publishers. Buyers who can't accept a US-headquartered vendor and won't spend two months explaining their CMS to a DORA auditor. We meet them where they already work.
insurance
Policy documents, regulatory disclosures, customer portals. Per-country residency that satisfies the EIOPA + national supervisors in one move.
See the use case →banking
T&C surfaces, MiFID II disclosures, customer-facing portals. DORA evidence pack ships with every workspace; the audit chain is the spine of the compliance posture.
See the use case →government
Multi-language ministerial sites, citizen-portal content, FOI request handling. Per-country residency that holds across every devolved authority.
See the use case →publishers
Financial-news outlets, legal-tech publications, healthcare media. Editorial workflow with four-eyes approvals and a typed SDK that won't age out.
See the use case →— what ships in the box
No gated features behind "contact sales." Modules unlock advanced requirements; the platform fee covers what every workspace needs.
schema-as-code
Schemas live in Git. Push with estokad push; the Studio renders the same definitions for content designers. Visual schema builder writes back through GitHub PRs.
visual edit
The Storyblok-grade overlay protocol. Editors click a headline in your preview, edit inline, the structured field updates. Works with Next.js, Nuxt, SvelteKit out of the box.
typed SDK
@estokad/next generates types from your schema. Renaming a field in the schema produces a TypeScript error in your call sites. The safety net you'd build yourself.
field-level RBAC
Read and write grants per (content_type, field). The enum role is the floor; custom roles restrict, never expand. Approval workflows for regulated publishes.
residency proofs
Cryptographically signed proof per workspace per UTC day. Bundled into the DORA evidence pack; verifiable end-to-end against the workspace's JWKS.
webhooks
HMAC-signed payloads, exponential-backoff retries, per-delivery audit history. Auto-disable on permanent failure so a broken endpoint doesn't bury the queue.
— team fit
— vs the incumbents
Each comparison covers the incumbent on its own terms — where they're still better, where Estøkad wins. No generic feature checklists, no banned-words puffery.
Same headless API surface, country-level residency, 30 to 40 percent less than Contentful Premium.
Read the comparison →Their visual edit alongside Sanity-grade schema-as-code. Country-level EU residency. DORA evidence pack on demand.
Read the comparison →Schema-in-code parity. EU jurisdiction end-to-end. DORA evidence as a product feature, not a Confluence page.
Read the comparison →— ready when you are
Pick a preset, enter your work email, you're in production by the end of the week. Or talk to us first — every email gets a human reply.