From server setup to workloads
Use Kubernetes manifests or Helm charts to describe your app. Kupe operates the underlying platform; you still own how your application runs.
More than a server.Less to assemble.
A VPS gives you a machine to run. Kupe gives you a Kubernetes platform with deployment, observability and guardrails already connected.
A VPS can be the right choice for a simple app. Kupe becomes interesting when maintaining the machinery around your app takes more time than building it.
Where the work changes
See more from the start
Logs, metrics, dashboards and alerts arrive connected, rather than becoming another stack to install alongside your services.
Keep the trade-off visible
Kubernetes has its own concepts to learn. If SSH and a small Compose file cover everything you need, a VPS may remain simpler.
The practical differences
A comparison of typical operating models. Features differ by provider and configuration.
| What to consider | A typical self-managed VPS | Kupe Cloud |
|---|---|---|
| Starting point | A virtual machine and operating system. | A cluster with platform services connected. |
| Deployment | Your scripts, processes or container tooling. | kubectl, Helm or GitOps. |
| Platform maintenance | You patch the OS and the tools you install. | Kupe maintains the platform; you maintain your workloads. |
| Visibility | You choose and operate your monitoring stack. | Central logs, metrics, dashboards and alerts. |
| Control | Root access to the machine. | Admin access to your tenant Kubernetes API, not the host. |
| Data recovery | You arrange and test application backups. | You arrange and test workload and persistent-volume backups. |
Kupe is currently in alpha: no SLA, and workload backups remain your responsibility. Read the current service terms.
Stay with a VPS when…
You have a straightforward workload, need host-level access, or are comfortable maintaining one machine. A low server bill can make sense when the operations work is small and well understood.
Explore Kupe when…
Several services, repeatable deployments and shared visibility are making server upkeep a distraction. Try a disposable environment first, and check that the Kubernetes model suits your team.
Plan the move around your data
Containerise the application, map ports and secrets, and decide how storage will work. Test backups and a restore before moving any important data. A container image is portable; your data migration still needs a plan.
Keep exploring
Compare your options
VPS, developer platforms and Kubernetes.
Read moreBuild the app you have in mind.
For developers who want to explore Kubernetes with a platform underneath them, rather than a long list of infrastructure tools to connect first.
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.