01
Ambition
A serious office/document suite, not a second-best compliance compromise.
Project Sovereign is a self-hostable European document suite for institutions that need DOCX-compatible editing, EEA-resident deployments, auditability, and control over the infrastructure that holds their documents.
Contracts, case files, ministerial briefings, hospital records, legal memos, and scientific papers should not be treated as disposable SaaS data. Project Sovereign exists so European institutions can run daily document work inside boundaries they understand and control.
A serious office/document suite, not a second-best compliance compromise.
Deployment paths designed for institutional control, review, and portability.
EEA-resident data-flow planning, customer-managed key custody, and short sub-processor review.
Sovereign combines familiar document editing with deployment patterns that security, legal, and operations teams can inspect before handover.
Keyboard-first document editing, comments, review workflows, and real-time collaboration.
On-prem, private-cloud, and European-cloud planning for institutions that need control.
Access logs, deployment evidence, sub-processor review, and compliance mapping by design.
Model provider and data flow remain controlled by the deploying institution.
Project Sovereign is aimed at institutions where document workflows cannot be treated as ordinary SaaS.
Federal and regional teams replacing external productivity tooling with reviewed deployments.
DORA-scope teams that need exit strategy, audit rights, and operational resilience.
Sensitive drafting workflows that require controlled regions, roles, and records.
Document collaboration for environments with strong supply-chain and deployment constraints.
Federated identity, research consortia, and portable document formats.
Client-sensitive document work with custody, auditability, and export discipline.
Project Sovereign is a self-hostable European document suite for institutions that need document workflows under their own operational, legal, and security control.
No. The public site describes a prepared deployment path for qualified institutions. Deployment details, evidence packs, and target environments are confirmed during review.
The intended deployment posture is EEA-resident by design. Each production deployment confirms regions, sub-processors, key custody, and data flow before handover.
No. AI is presented as optional and provider-controlled by the deploying institution. There is no default cloud AI provider in the public positioning.
The deployment model supports on-prem and private-cloud planning, with air-gapped deployments handled through prepared offline bundles and operations review.