The infrastructure, service versions and interfaces the platform supports today, and what each one needs from your side.
Updated November 2, 2026
Infrastructure providers
The platform reaches each cloud platform through a provider, and an organization can connect several infrastructures, each registered in a region and zone. Each provider available today has its own rows below.
OpenStackConnected through its standard APIs. Nothing is forked or replaced: each infrastructure is one OpenStack project the platform signs in to, and your operators keep their existing tooling.
OpenStack identityKeystone v3, with a password or an unrestricted application credential.
OpenStack servicesNova compute, Neutron networking with an external network, Cinder block storage, Glance images and Octavia load balancing.
OpenStack rolesThe member role, plus the role your load balancer policy requires (often load-balancer_member).
Existing Kubernetes clustersAny cluster you register with a kubeconfig becomes a deployment target for applications, on its own or grouped into a fleet.
Managed services
What teams and clients provision. The exact versions offered are listed in the platform documentation.
KubernetesCNCF-conformant clusters on current upstream Kubernetes releases, with dedicated or hosted control planes and in-place upgrades between versions. Your platform operator chooses which versions are offered.
PostgreSQLCurrent PostgreSQL major versions, kept on their latest minor release, optionally highly available with three replicas. Your platform operator chooses which majors are offered.
Virtual machinesFrom the images and flavors you enable in each infrastructure’s catalog, with networks, routers, firewalls and SSH keys.
ApplicationsHelm charts and container images as versioned templates, deployed to one cluster or to every cluster of a fleet.
Interfaces and deployment
How people and automation reach the platform, and where it runs.
InterfacesWeb console, REST API and Terraform provider, all working on the same objects.
Sign-inPlatform accounts, invited by email, with a password and optional authenticator-app two-factor authentication.
Where it runsEntirely inside your perimeter, including fully air-gapped sites, or with a hosted control plane.
Many sitesRegions and zones across many infrastructures. One agent per site reconciles desired state locally, so a site keeps running through a link outage and resyncs afterwards.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Preferences
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.