Keep your Kubernetes workflow.Start further along.

For teams that want direct Kubernetes access and a maintained baseline for GitOps, observability and security tooling.

Evaluate Kupe as an opinionated foundation. Start by checking where your workload and operational requirements meet the platform’s boundaries.

Spend your evaluation on the right questions

Check compatibility

Test your charts, custom resources and operators against a tenant cluster. Identify anything that requires host access or changes to shared infrastructure.

Bring your delivery definitions

Use your Kubernetes manifests and Helm charts, and evaluate the included GitOps workflow with a representative repository.

Inspect the operating model

Look at tenant boundaries, platform alerts, application instrumentation and the maintenance scope. Decide how your team will respond to workload issues.

A good fit if…

You want the standard Kubernetes API and a consistent set of platform services without owning every shared component’s lifecycle.

Build your own if…

You need to control host configuration, replace core networking or prescribe every platform component. Kupe’s managed services and tenant boundaries may not match those requirements.

Use alpha to validate the model

Rehearse deployment, recovery and maintenance with disposable workloads. Confirm the limits that matter with the Kupe team before planning broader adoption.

Keep exploring

A cluster is the beginning.

Bare Kubernetes, managed cloud clusters and Kupe all give you Kubernetes. The difference is how much of the surrounding platform your team assembles and operates.

Kubernetes, assembled.

Your own Kubernetes API, familiar deployment tools, and a connected stack for GitOps, observability and security. Kupe keeps the platform running.

We run the platform.

A clear operating boundary helps you decide whether Kupe is right for your team, and what you need to prepare before deploying.

Find your starting point

Bring a workload. See how it fits.

Try a non-critical environment, explore the platform and tell us what you need next.

Talk to the Kupe team Read the docs

Kupe is in alpha. No SLA. Your team owns workload backups. Read the Alpha Notice.