Self-managed Kubernetes
You choose the infrastructure and operate the cluster lifecycle, networking and platform tools. This gives you broad control and a broad maintenance responsibility.
A cluster is the beginning.Kupe connects the platform.
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.
Managed Kubernetes can remove control-plane work. Kupe also brings GitOps, observability and security tooling together as a maintained platform.
Look beyond the control plane
Managed cloud Kubernetes
The provider manages defined parts of the cluster. Add-ons and service integrations vary; your team still decides how the surrounding platform fits together.
The Kupe approach
Start with a tenant Kubernetes API and connected GitOps, logs, metrics, alerts and guardrails. Kupe operates the foundation and the shared platform services.
The practical differences
A comparison of typical operating models. Features differ by provider and configuration.
| What to consider | A managed cluster you extend | Kupe Cloud |
|---|---|---|
| Starting point | A managed cluster; included add-ons vary. | A cluster with an assembled platform stack. |
| GitOps | Choose, configure and maintain your delivery setup. | GitOps delivery is part of the platform. |
| Observability | Select provider services or integrate your own stack. | Monitoring, logging and alerting are connected. |
| Security tooling | Choose and integrate policies, scanning and runtime tools. | Security policies, vulnerability scanning and runtime protection are included. |
| Platform upgrades | Provider handles its scope; you handle your additions. | Kupe maintains the included platform components. |
| Customisation | Choose a provider and stack around your requirements. | Extend your tenant cluster within Kupe’s platform boundaries. |
Kupe is currently in alpha: no SLA, and workload backups remain your responsibility. Read the current service terms.
Build your own when…
Your requirements depend on particular cloud services, host-level changes, specific networking, or a platform stack you need to control end to end. A mature platform team may already have this work well covered.
Explore Kupe when…
Your team wants Kubernetes tooling without owning every integration and upgrade in the surrounding stack. Check workload compatibility, resource needs and the tenant model before adopting it.
A tenant cluster has boundaries
Admin access to your tenant API does not mean control of the underlying hosts or shared services. Review the architecture and test any operator or cluster-wide integration you rely on.
Keep exploring
Compare your options
VPS, developer platforms and Kubernetes.
Read moreKeep your Kubernetes workflow.
For teams that want direct Kubernetes access and a maintained baseline for GitOps, observability and security tooling.
Read moreWe 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.
Read moreFind 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.
Kupe is in alpha. No SLA. Your team owns workload backups. Read the Alpha Notice.