Sovereign deployment

Keep the platform inside your boundary.

For organisations that need the portal, identity, orchestration and evidence to remain in a controlled estate—not just the test environment.

Deployment design · implementation by agreement

Sovereign installation, disconnected operation and release parity require implementation and acceptance testing. They are not generally available deployment capabilities today.

Your controlled estate

One local management and evidence boundaryThe customer owns every runtime component shown. Optional update/licensing exchange is separate from workload operation.
  1. Your users and IdPLocal portalCustomer identity and organisation policy.
  2. Your runtimeAPI & orchestrationSingle-customer enforcement; local jobs and approvals.
  3. Your source and targetCollectors & runnersRead selected sources; test in bounded target environments.
  4. Your stores and keysEvidence & auditPostgreSQL-compatible records and S3-compatible objects.

Identity and keys

The design uses your identity provider, secrets manager, encryption keys, logs and access controls. A local installation must reject access from other customer organisations.

Connected updates

A customer-controlled update process verifies signed release manifests and immutable images. You approve maintenance windows, permission changes and migrations.

Disconnected operation

The design supports transferred release bundles and locally checked entitlements. No workload inventory or evidence should be required by a licensing exchange.

Acceptance is part of the deployment

Agree the hosting substrate, identity integration, database/object adapters, backup and restore, offline dependency supply, update/rollback path and supported capabilities. Prove these in your boundary before relying on parity with the managed product.

Today’s managed implementation uses WorkOS and AWS-specific database/event transports. Portable identity and infrastructure adapters, signed release delivery and disconnected acceptance remain implementation work. A diagram alone cannot establish sovereignty.

Compare all deployment options

Plan a sovereign deployment.

Use the evaluation discussion to establish the boundary, delivery work and acceptance evidence your organisation requires.

Request early access →