Documentation

Estokad is a sovereign-by-design headless CMS for European publishers, regulators, and enterprises. The docs cover every customer-facing surface — the schema authoring API, the runtime SDK, the Studio editor, the compliance pack, the CLI.

What is in scope here

• Schema — defineType(), embedded types, validators, locales.
• API — REST, GraphQL, draft mode, the typed TypeScript SDK.
• Visual edit — overlay protocol, preview tokens, framework adapters.
• Compliance — DORA evidence pack, residency proofs, audit chain, sub-processor register.
• Auth — magic links, passkeys, API keys, custom roles with field-level permissions.
• CLI — estokad init, push, status, diff.

What is out of scope

These docs are public. Operational runbooks for self-hosters live in docs/runbook.md in the source repository; engineering decision logs live alongside in docs/architecture.md, docs/data-model.md, etc. Customer audit-pack samples live in /settings/compliance of the Studio itself, not here.

Where to start

If you are evaluating Estokad, start with Getting started. It walks the full loop from sign-up through pushing a schema, creating an entry, and fetching it from a Next.js app.

If you are migrating from Contentful, Storyblok, or Sanity, the comparison pages on the marketing site cover the gaps and overlaps: /vs/contentful, /vs/storyblok, /vs/sanity.