App-first workflows
Many developer platforms focus on repositories, builds and services. This can be an excellent fit when your app matches their supported workflow.
App hosting is a great start.Sometimes you need a cluster.
Developer platforms make shipping an app straightforward. Kupe is for teams that want a managed foundation while working directly with Kubernetes.
Choose around the way you want to work: an app-focused deployment model, or a Kubernetes API you can extend with standard tooling.
Choose the abstraction that fits
Kubernetes-first workflows
Kupe gives you a cluster. Deploy containers using manifests, Helm or GitOps, and use the Kubernetes resources your workload needs.
Responsibility comes with control
More control means more decisions about resources, health checks, application configuration and recovery. Kupe handles platform operations, not every application decision.
The practical differences
A comparison of typical operating models. Features differ by provider and configuration.
| What to consider | An app-focused developer platform | Kupe Cloud |
|---|---|---|
| Primary unit | Usually an app or service. | Your tenant Kubernetes cluster. |
| Deployment model | Provider-defined builds and service configuration. | Kubernetes manifests, Helm and GitOps. |
| Extensions | Integrations and features supported by the provider. | Kubernetes APIs, charts and operators within platform boundaries. |
| Infrastructure access | Depends on the provider and plan. | Admin access to your tenant API; no host access. |
| Observability | Available features and retention vary by provider. | A connected logs, metrics, dashboards and alerting stack. |
| Learning curve | Often simpler for supported app patterns. | You need to understand Kubernetes workloads. |
Kupe is currently in alpha: no SLA, and workload backups remain your responsibility. Read the current service terms.
Choose an app platform when…
Your priority is a short path from repository to running service, and the available runtimes, networking and integrations cover your needs. You may not need Kubernetes at all.
Explore Kupe when…
You want to bring existing Helm charts, run operators, or manage Kubernetes resources directly. Kupe supplies a connected foundation without asking you to build the whole platform first.
Compare the actual workload
Build pipelines, storage, routing, supported resources, limits and billing models differ. Try your app’s deployment path and dependencies before making a choice. This comparison describes categories, not every provider or plan.
Keep exploring
Compare your options
VPS, developer platforms and Kubernetes.
Read moreA small team.
For product teams evaluating Kubernetes who want repeatable deployments and shared visibility without first assembling an internal platform.
Read moreKubernetes, assembled.
Your own Kubernetes API, familiar deployment tools, and a connected stack for GitOps, observability and security. Kupe keeps the platform running.
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.