Air-gapped infrastructure has no route to the public internet, which rules out any tool that depends on a SaaS backend, telemetry, or cloud-based license checks to function. Operating it well means running an operations layer entirely inside the network perimeter - with zero outbound connections required - rather than adapting a cloud-first tool after the fact. OptimusHub is built air-gap native: it installs inside your network, and a fully disconnected deployment works with zero required outbound connectivity.
Talk to us about your operating environment →OptimusHub is designed to work with your existing environment, not take ownership of it. Here's exactly what that means.
OptimusHub runs entirely inside your network. There is no public SaaS backend and no vendor cloud in the request path.
A fully air-gapped install works with zero outbound connections. Optional integrations - a Git remote, a registry, SMTP - are opt-in, never required for the platform to run.
Operational data, configuration, credentials, and audit logs live in a database you deploy and control, inside your perimeter. Nothing is mirrored to us.
OptimusHub connects to the endpoints, clusters, and hosts you already run, using the credentials and network paths you configure - no VPNs or trust boundaries to rebuild.
OptimusHub is a management layer, not a request-path component. Your applications don't call it, depend on it, or route traffic through it to run.
Moving off OptimusHub is an operational migration, like retiring any management tool: export configuration and audit history, repoint CI/CD and access controls, decommission the instance.
No telemetry, no phone-home, no license-check callbacks.
RBAC, SSO (LDAP / OIDC / SAML), and an internal PKI enforced inside your network.
Every action - who, what, when, from where - recorded in a database you control.
Built for teams that face real audits, not teams that just say they do.
Running air-gapped is not only a security posture - it changes how deployment, access, and audit actually get done day to day. Without a shared operational layer, disconnected sites tend to be managed through whatever the last engineer on-site set up: local scripts, manual change logs, and access granted by memory rather than policy.
With one operating model applied consistently, deployment, access control, and audit logging work the same way whether the environment has internet access or none at all - so a disconnected site isn't a special case your team has to remember how to handle.
Bring the details of your disconnected or restricted environment. We'll help map where this fits.
Talk to us about your operating environment →