RESOURCES

Notes from the project

Short public briefs on document sovereignty, deployment, compliance, DOCX compatibility, migration, backup testing, and European regulatory context.

ALL POSTS

Public briefs

Why we picked OnlyOffice as the engine

An honest comparison of the open document engines considered for Sovereign, and why DOCX fidelity, inspectability, and deployment control mattered most.

NIS2 Article 21, mapped to Sovereign in one page

A short control-mapping brief for how document workflows can support risk analysis, incident handling, continuity, supply chain review, and cryptography obligations.

DOCX compatibility methodology for sovereign document workflows

How Project Sovereign thinks about DOCX compatibility, regression testing, macro boundaries, visual fidelity, and safe document handling.

Migration brief for regulated organisations

A practical migration outline for teams moving sensitive document workflows into a sovereign deployment boundary.

What we chose not to build, and why

Why Sovereign prioritizes document fidelity, auditability, deployment control, and quiet daily workflows over novelty features.

Backups, restores, and the Friday afternoon test

A short operations brief for proving that document backups can be restored when a real institution needs them.

Schrems II and office software risk

Why transfer risk still matters when the software holding contracts, case files, and confidential memoranda is treated as ordinary cloud productivity tooling.

Sovereign 0.4 release brief

A public release-style brief for comments, mentions, audit-log search, and compatibility guardrails.