SELF-HOST

Run document workflows where your institution can govern them

Project Sovereign deployments are prepared with each institution so residency, keys, identity, network requirements, backups, and audit evidence are captured before handover.

PREPARATION

Three checks before deployment

A serious deployment starts with the operating boundary. Sovereign planning confirms the target environment, identity model, key custody, backup topology, network requirements, and evidence pack before production use.

01

Confirm on-prem, private-cloud, or European-cloud target.

02

Map SAML/OIDC, roles, administrative boundaries, and audit owners.

03

Document key custody, backup/restore plan, TLS, domains, and sub-processors.

TARGETS

Deployment paths

01

On-prem

Institution-controlled infrastructure with handover and operations review.

02

Private cloud

Dedicated European cloud environments with customer-managed controls.

03

Air-gapped

Offline-bundle planning for environments that cannot rely on internet access.