On-premiseOn request, as a custom plan
orboto in your own data centre.
When your procurement or security team requires running it in-house, on-premise is part of a custom plan: say hello and we will figure out the shape together. It is the same product as in the Cloud, with the same code on the same schema.
Technically it is the same installation as self-host, which ships after Cloud goes GA. Ask now and we will work out requirements and timing together.
What you can plan with
- The same containers as self-hostWith PostgreSQL and an S3-compatible object store; the images are built for several CPU architectures.
- A licence without an outbound connectionWhere the installation cannot reach orboto's licensing service, it accepts an offline licence file.
- Sign-in through your identity providerSingle sign-on via SAML and OIDC and user provisioning via SCIM 2.0, both part of Enterprise.
- Your keys, your SIEMCustomer-managed keys (BYOK) and audit-log forwarding to your SIEM are part of the Enterprise plan.
- No operator but youCloud content encryption protects storage, backups and the hosting layer, but not against the operator of a running instance. When orboto runs on your hardware, that operator is you.
- Evidence for your auditExport for your own BSI C5, ISO 27001 or SOC 2 audit. orboto itself is not certified.
- Agreed in a custom planSLA, training, multi-region hosting and support for your BSI C5 audit.
Everything here is published on orboto.io, in the pricing overview and in the docs; contract details are settled in your custom plan.