Hetzner Self-hosted Kubernetes
Connect your server from Hetzner and Wodby will spin up a ready-to-run self-hosted Kubernetes environment for you. We will install all necessary infrastructure, so you can deploy your app using one of our stacks in a few clicks.
Specific to this provider
What Wodby sets up on a Hetzner server
On Hetzner, Wodby runs Kubernetes on a server you rent yourself. You run one installation command on the server, and Wodby installs K3s, a certified lightweight Kubernetes distribution, with pod networking and app routing.
What the server needs
The server must have dedicated, non-shared CPU and run Ubuntu or Debian, Fedora or CentOS, or openSUSE. Only amd64 machines are supported at present.
One command, valid for a short time
After you create the cluster, Wodby shows a one-time installation command to run as root. Its download token expires quickly, and reloading the cluster page produces a fresh command.
A single-server cluster
A K3s cluster connected to Wodby is one server. More nodes cannot be joined and the cluster cannot be scaled from Wodby, so choose a server large enough for everything it will run.
Volumes use the server's disk
Persistent volumes are stored on the host disk. Before an app is saved, and again before it is deployed, Wodby checks that the requested volumes fit into the free space with a safety reserve.
You patch the operating system
Wodby updates K3s and the cluster infrastructure, never the operating system, and it never reboots your server. Kernel and system updates, and the reboot they need, are yours to schedule.
Read the self-hosted Kubernetes guide for requirements, setup steps, and limits.
Infrastructure we install and maintain
A cluster ready to run your apps
Wodby installs and connects the services for app traffic, resource monitoring, and provider integrations. Start deploying with these essentials in place, and keep them and the Kubernetes version current with Wodby.
Application routing
Publish HTTP and HTTPS endpoints for your apps. Wodby configures the gateway and routes requests to the appropriate service.
- Envoy Gateway
Know how your cluster is performing
View CPU, memory, and storage metrics in Wodby to understand resource usage and investigate capacity issues without assembling your own monitoring stack.
- Monitoring
- Node exporter
- Kubernetes state metrics
Keep your cluster current with less manual work
Wodby upgrades its infrastructure and the infrastructure app stacks automatically, and can upgrade the Kubernetes version too, each with its own version policy and maintenance window. You choose what may change and when, and every upgrade is a task you can follow.
Automatic infrastructure upgrades
Keep Wodby's cluster networking and routing setup current. Enable automatic upgrades and choose which patch, minor, and major changes your cluster may receive.
Automatic infrastructure app updates
Update gateway, monitoring, and controller stacks automatically with their own version policy, including newer revisions of the same version.
Automatic Kubernetes upgrades
Wodby moves the cluster to new K3s patch releases and keeps Cilium networking current, in your maintenance window by default. Each Cilium update is health-checked and rolled back if it fails.
Maintenance on your schedule
Set separate weekdays, hours, and time zones for automatic infrastructure, infrastructure app, and Kubernetes upgrades, so routine maintenance starts when it suits your team.
Reviewable, traceable updates
Review infrastructure app changelogs, Kubernetes upgrade plans, and available release notes. Follow upgrade tasks, retry failed operations, and receive success or failure emails for automatic infrastructure and Kubernetes upgrades.
App environment network isolation
On supported clusters, network policies isolate incoming traffic between app environments while keeping services in the same environment connected.
Budget self-hosted Kubernetes on one server
Hetzner offers dedicated servers, which means if you're looking for a budget-friendly setup and do not need Kubernetes scaling, you can run single-server self-hosted Kubernetes on your own hardware instead of paying for a managed control plane and node pools. This is a practical way to keep Kubernetes costs down while still using Wodby-managed application stacks. Read more on the self-hosted Kubernetes page.
Popular stacks
Browse common Wodby stacks and open the stack page for setup, services, integrations, and deployment options.
Prefer not to use your own cloud account or server?
If you want the Wodby Kubernetes workflow without a provider account or server of your own, deploy with Wodby Cloud. It gives you the same managed stacks and deployment model without requiring a cluster in your own cloud account or on your own server.
No separate provider account
Start deploying without creating and wiring AWS, GCP, Azure, DigitalOcean, or dedicated server infrastructure first.
Less infrastructure hassle
Wodby provides the cluster and platform foundation so your team can focus on applications instead of setting up and owning the infrastructure itself.
Simple pay-as-you-go model
Wodby Cloud pricing provides a simpler way to get started with a managed Kubernetes environment and predictable platform costs.
Deploy on Hetzner self-hosted Kubernetes with Wodby
Launch a production-ready environment faster with Wodby-managed infrastructure, deployment workflows, and application stacks.