Choose the Kubernetes infrastructure model that fits your team
Start with the infrastructure model that matches your team. Managed Kubernetes comes first when you want control in your own cloud account, self-hosted Kubernetes with K3s is the lower-cost single-server option, and Wodby Cloud is the simplest fully managed path.
Managed Kubernetes in your own cloud account
Best when you want the Wodby platform on top of a managed cluster from AWS, GCP, Azure, DigitalOcean, or another supported provider.
See managed providersSelf-hosted Kubernetes on your own server
Best when you want budget single-server hosting, do not need Kubernetes scaling, and are comfortable running on a server you control.
See self-hosted optionWodby Cloud
Best when you do not want a cluster in your own cloud account or on your own server and want the lowest-hassle start.
See Wodby CloudWhy teams choose Kubernetes as the foundation
Kubernetes is not just about containers. It gives growing teams a more durable way to run applications with better consistency, clearer scaling, and more freedom in how infrastructure evolves.
Built on an industry standard
Kubernetes is a widely adopted foundation for modern application infrastructure, which makes it a safer long-term choice than relying on a narrower proprietary hosting model.
Access a broad ecosystem of integrations
Because Kubernetes is so widely used, it works well with a large ecosystem of tools for ingress, databases, observability, security, automation, and other infrastructure needs.
Keep environments more consistent
Run the same application model across development, staging, and production to reduce configuration drift and lower the risk of release-time surprises.
Improve resilience for real applications
Kubernetes is designed to keep workloads running, replace failed containers, and make rolling updates safer for customer-facing apps and long-running services.
Avoid getting trapped in one provider model
Because Kubernetes is a widely adopted standard, it gives your team more portability across managed clouds, self-hosted servers, and future infrastructure decisions.
Scale without rebuilding your hosting model
Kubernetes gives you a cleaner path from smaller environments to larger production workloads, so you can grow traffic, services, and team usage without replatforming later.
Managed Kubernetes
Connect a supported cloud provider account and let Wodby create and manage the Kubernetes cluster setup for you.
This is the strongest default when you want infrastructure in your own cloud account, cleaner upgrade paths, and a production setup that scales better than a single-server approach.
- Best fit for production workloads and team ownership.
- Wodby handles the cluster setup and platform infrastructure.
- Pairs well with configurable stacks, CI/CD, and repeatable environments.
Supported managed providers
Pick the provider you already use or want to standardize on. Wodby provisions the Kubernetes layer so you can move straight to deploying stacks.
Self-hosted Kubernetes on a dedicated server or VM
Use this option when you want a budget self-hosted Kubernetes path for workloads that fit on one server and do not need Kubernetes scaling across nodes.
K3s is a lightweight open-source Kubernetes distribution. Wodby uses it to prepare a single-server environment for smaller projects, agency portfolios, and cost-sensitive deployments.
- Best fit when infrastructure cost matters more than Kubernetes scaling capabilities.
- Works on dedicated servers, bare metal, or virtual machines.
- Good starting point if you want to host many apps on one server.
Need the tradeoff? Read our self-hosted Kubernetes with K3s page.
Common server starting points
If you want a proven budget-friendly route, start with Hetzner. Other providers work as well when you already have a preferred server vendor.
- Hetzner dedicated servers
- OVH dedicated servers
- DigitalOcean Droplets
- Azure Virtual Machines
- Google Cloud Compute Engine
- AWS AWS EC2
- Oracle Cloud bare metal
- Alibaba bare metal
- UpCloud
- Scaleway
- Custom provider (any other hosting provider)
Wodby Cloud
Choose Wodby Cloud when you want the simplest Kubernetes path and do not want to set up a separate provider account before you start.
Wodby Cloud keeps the cluster on Wodby-managed infrastructure and charges based on Wodby Cloud usage, which keeps this option easy to start with for teams that care more about application delivery than owning the cluster in their own account.
No provider setup
Start without opening and wiring a separate cloud account.
Fastest path
Wodby handles the cluster layer so your team can focus on stacks and apps instead of running a separate cluster in your own account.
Usage-based pricing
Pay for the Wodby Cloud resources you actually use.
Wodby Cloud is the best fit when you want the Kubernetes workflow and managed stacks, but do not want to keep the cluster in your own cloud account or on your own server. See Wodby Cloud and Wodby Cloud pricing.
Popular stacks
Browse common Wodby stacks and open the stack page for setup, services, integrations, and deployment options.
Start with the Kubernetes path that fits your team
Managed Kubernetes for cloud ownership, self-hosted Kubernetes for lower-cost single-server hosting, or Wodby Cloud for the simplest managed start.