Editorial workflow
Draft → review → publish loop with approval workflows. Custom roles for editors, sub-editors, legal review. Field-level RBAC on the parts that need it.
— solutions · publishers
The CMS for regulated publishers.
Financial-news outlets, legal-tech publications, healthcare media, sectoral trade press. The common thread: editorial workflow that has to hold against a regulator's scrutiny, plus a developer team that wants TypeScript-first ergonomics. Estøkad gives both halves the experience they expect.
— the regulators in scope
What you're held to.
| Framework | What it requires |
|---|---|
EMFA | European Media Freedom Act — independence of editorial decisions, transparency of media ownership. Audit chain proves the editorial-decision path. |
DSA | Digital Services Act — content moderation transparency, takedown notices, recommender-system disclosures. Workflow + audit chain make this surface-able. |
GDPR + ePrivacy | Subscriber data, comment moderation, personalisation. Cookie banners, consent records, and granular access logs. |
Sectoral codes | Financial-news outlets follow CMVM / FCA / BaFin attribution rules. Healthcare publishers follow EMA labelling. Legal-tech follows local bar regulations. |
— the workflows
What ships through Estøkad.
Multi-edition
Per-locale publish state across French / Dutch / German / Italian / Spanish editions. Cross-references between editions for shared assets and resources.
Embargo + scheduling
Future-dated publish via the API. Audit chain captures the schedule + the actual publish moment. Webhook subscribers fire at publish time.
Source archives
Link to source documents via the asset pipeline. imgproxy variants for hero images, OG cards, and thumbnail sets. Assets carry residency-proof signatures.
— why Estøkad fits
The wedge for this industry.
Where publishers diverge from insurance and banking is the editorial workflow. The content production pipeline is the daily reality, not a once-a-year compliance event. Approval workflows with the four-eyes rule, audit-chained publish, and custom roles per desk are operational tools, not procurement checkboxes.
The typed SDK matters here more than in most segments. Publishers run experiments — new sections, new editorial formats, new monetisation surfaces. @estokad/next keeps the renderer in lockstep with the schema; renaming a field in the schema produces a TypeScript error in the call sites until you handle it. The pace of iteration accelerates rather than slows because of the safety net.
Multi-locale + multi-space lets a single newsroom run editions across countries with shared resources but separate editorial chains. Per-country residency satisfies the local sectoral code without forcing the publisher to operate multiple CMS instances.
— how to start
The path to production.
Publisher customers typically start on Studio (€499/mo) for a single-edition setup, then move to Enterprise (€2,999/mo) when they bring in multi-edition + multi-locale requirements. The Regulated preset (€1,699/mo) is the right starting tier for any publisher in financial-news or healthcare segments where DORA / sectoral compliance is in scope from day one.
For investigative journalism + leak handling, the Sovereign preset (€4,299/mo) plus sovereign-cloud hosting (€1,299/mo) provides customer-dedicated infrastructure. That tier is overkill for general-interest outlets and well-suited for outlets where source protection is a workflow constraint.