DocsEvaluateSelf-hosting · Coming soon
Loading documentation, please wait.
NEMORIONDocsNEMORIONDocsSelf-hosting means running Sovereign in an environment your organization operates, such as your own servers or cloud resources. It gives you responsibility for the installation as well as control over where it runs.
The supported step-by-step guide for standing up Sovereign locally is being prepared. Validated Docker Compose instructions and Kubernetes guidance will be published as their respective deployment paths are ready.
Your organization may need to keep application data in a particular environment, connect to private services, or manage deployment and upgrades on its own schedule.
A self-hosted installation still needs an operating plan: access management, backups, monitoring, updates, and recovery.
Separate administration and troubleshooting sections will explain ongoing operation. This introduction does not substitute for those validated instructions.
A self-hosted instance has its own authentication boundary. Its owner setup and identity configuration must work for the installed platform, independently of the managed alpha environment.
OIDC federation is the current identity provider integration path. SAML support is planned separately and should not be assumed available.
If your immediate goal is to understand Orbit, start with the managed alpha access options. If your goal is to validate an installation in your own environment, check back for the self-hosting manual.