Overview
Kupe Cloud is a managed Kubernetes platform built around isolated tenant clusters with shared platform services. Your team works inside standard Kubernetes clusters and APIs, while Kupe operates the surrounding control plane, networking, observability, access, and cluster lifecycle.
The result is a platform that feels like Kubernetes, but removes the need to build and run the supporting stacks yourself.
The platform model
Section titled “The platform model”Each managed cluster gives you an isolated Kubernetes environment for your workloads. Kupe then layers shared platform capabilities around those clusters:
- Cluster lifecycle through the console, API, and Terraform
- GitOps delivery through centrally managed Argo CD
- Access and authentication through SSO-backed console and kubeconfig flows
- Networking through shared Gateway API infrastructure, DNS, and TLS
- Observability through managed Grafana, metrics, logs, alerts, and notifications
- Secrets through tenant-isolated vault-backed secret storage and sync
Your team still deploys standard Kubernetes resources. The platform is opinionated about how clusters are operated, not about the applications you run inside them.
What Kupe Cloud manages
Section titled “What Kupe Cloud manages”Kupe operates the underlying platform and control plane so teams can focus on workloads and delivery rather than building platform plumbing.
| Area | What Kupe manages |
|---|---|
| Cluster provisioning | Creates clusters, registers them in platform systems, and makes them available in the console and CLI |
| Kubernetes lifecycle | Supported versions, upgrade workflows, health checks, and platform-side coordination |
| Infrastructure | Host nodes, networking, storage integration, ingress infrastructure, and platform service deployment |
| Authentication and access | SSO integration, tenant roles, kubeconfig generation, and access boundaries |
| GitOps control plane | Shared Argo CD, tenant projects, and destination registration for managed clusters |
| Observability stack | Grafana, Loki, Mimir, Alertmanager, and baseline dashboards |
| Secret storage and sync | Tenant-isolated vault and cluster sync workflows |
What your team owns
Section titled “What your team owns”Your team owns the workloads and operating practices inside your clusters.
| Area | What your team owns |
|---|---|
| Application manifests | Helm charts, Kustomize overlays, or plain YAML stored in Git |
| Namespace design | How workloads are grouped, named, and separated inside a cluster |
| Delivery workflow | Promotion rules, repository layout, sync policies, and rollback practices |
| Runtime configuration | Environment variables, secrets usage, routing rules, and dependency configuration |
| Service health | SLOs, dashboards, alert rules, incident response, and capacity decisions |
How teams usually work with the platform
Section titled “How teams usually work with the platform”The normal flow looks like this:
- Create a cluster in the console, API, or Terraform.
- Download kubeconfig or use the console for day-to-day access.
- Register or connect a Git repository in Argo CD.
- Deploy workloads into the cluster through GitOps.
- Expose services with
HTTPRoute. - Monitor health in Grafana, logs, and alerts.
- Manage secrets, upgrades, and day-2 changes through the platform.
This keeps the operating model consistent across teams and clusters, which is one of the main reasons to use the platform in the first place.
Access paths
Section titled “Access paths”You can work with your clusters through several interfaces, depending on the task:
| Interface | Best for |
|---|---|
| Console | Cluster creation, inspection, workload troubleshooting, secret management, and operational tasks |
| CLI kubeconfig | kubectl, Helm, scripts, and local engineering workflows |
| Argo CD | GitOps application deployment and sync status |
| API | Programmatic cluster, member, secret, and API key management |
| Terraform | Declarative provisioning and platform changes as code |
Use the console and CLI for day-to-day cluster operations. Use the API and Terraform when you want repeatable automation around the same platform objects.
Good starting points in this section
Section titled “Good starting points in this section”- Concepts — the core platform ideas and how the main pieces fit together
- CLI Access — interactive and automation kubeconfig flows
- Secrets — store values once and sync them into one or more clusters
- Limits — practical bounds for clusters, secrets, and resource usage