A few things worth knowing.Before your first cluster.

A managed Kubernetes platform that brings the cluster foundation, GitOps, observability and security tooling together. You deploy and operate your workloads through standard Kubernetes tools.

You should be comfortable with, or ready to learn, workloads, services, routing, resource settings and storage. Kupe removes platform assembly work, but your application is still running on Kubernetes.

You have admin access to your tenant Kubernetes API and can use kubectl and Helm. Test operators against the tenant model: integrations that need host access or changes to shared infrastructure may not fit.

Kupe gives you a Kubernetes cluster with connected platform services. It does not give you root access to a virtual machine. Your deployment workflow uses Kubernetes resources rather than assuming a repository-to-app build process.

Not during alpha. There is no SLA, uptime guarantee or service credit, and the platform is still changing. Use disposable environments and non-critical workloads to evaluate it.

No. Workload data, including persistent volumes, is not backed up by Kupe. Your team owns running backups and testing restores. GitOps can recreate workload definitions; it cannot recreate data that was only in cluster storage.

Standard alpha clusters run a single control-plane replica. HA is available as an opt-in for tenant clusters. Clusters without HA may have short API interruptions during maintenance. This does not change the alpha’s lack of an SLA.

The alpha is free to try. General availability pricing is not set out here; contact the team about your expected workload and plans before making a long-term cost comparison.

Use the access action in the header. If invite codes are required, request access or redeem your existing code on the signup page. Read the Alpha Notice before creating workloads.

Kubernetes manifests, container images and Helm charts use familiar interfaces. Moving still requires planning for storage, secrets, routing and provider-specific integrations. Test the migration path your app actually needs.