Kubernetes hosting in your cloud, on your servers, or on Wodby Cloud

Wodby sets the cluster up, installs what your apps need to receive traffic and report metrics, and keeps that infrastructure current. You choose where it runs: a managed service in your own cloud account, a server you already rent, or infrastructure Wodby operates for you.

Choose a model

Three ways to run a cluster

The stacks, the deployments, and the day-to-day workflow are the same on all three. What changes is who owns the infrastructure, how it scales, and what you pay for.

Managed Kubernetes

A cluster on your cloud provider’s Kubernetes service, created and run from Wodby.

Runs on
Your own cloud account, so the infrastructure and its billing stay with you.
Choose it when
You run production workloads and want what your provider’s Kubernetes service offers, such as node autoscaling and clusters spread across zones.
What Wodby does
Creates the cluster and its network in your account, installs the cluster infrastructure, and removes the cluster from the account when you delete it in Wodby.
Trade-off
Autoscaling and high availability depend on the provider. Each provider page says what that provider offers.
You pay
Your cloud provider for the resources, plus your Wodby plan.
Pick a provider

Self-hosted Kubernetes

K3s, a certified lightweight Kubernetes distribution, installed on a server you already rent or own.

Runs on
A dedicated server, a bare-metal machine, or a virtual machine from any hosting provider.
Choose it when
Infrastructure cost matters more than autoscaling, for example when you host many small apps on one server.
What Wodby does
Installs Kubernetes with one command, updates it, checks the server’s packages for known vulnerabilities, and installs operating system updates when you start them.
Trade-off
One server runs Kubernetes and takes public traffic, so the cluster is not highly available. You add capacity by joining more servers as worker nodes.
You pay
Your hosting provider for the server, plus your Wodby plan. There is no managed control plane on the bill.
How self-hosted Kubernetes works

Wodby Cloud

A cluster that Wodby creates and operates for you, with no cloud account or server of your own.

Runs on
Infrastructure that Wodby manages. There is no provider account to open or connect first.
Choose it when
You want to deploy today and leave the cluster to Wodby, or you want to try the workflow first on a free temporary demo cluster.
What Wodby does
Creates and operates the cluster, keeps its infrastructure upgraded, and scales it between the minimum and maximum node counts you set.
Trade-off
The cluster does not live in an account you own. Choose managed Kubernetes when it has to.
You pay
Wodby Cloud usage for the nodes and storage you run. A lasting cluster needs a paid Wodby plan.
See Wodby Cloud

Included infrastructure

The cluster arrives with the parts an application needs

A Kubernetes cluster on its own does not route traffic, report metrics, or isolate workloads. Wodby deploys those capabilities as infrastructure apps when the cluster is created, so adopting Kubernetes does not start with a platform engineering project and you can use the cluster as a Kubernetes PaaS from the first deployment. Which ones a cluster runs depends on its provider and the infrastructure features you select.

  • A public entrypoint for your apps

    Envoy Gateway is the cluster’s single public load balancer, serving HTTP and HTTPS, plus TCP and UDP where the cluster’s Gateway API bundle supports those route types. Each app environment gets its own routing release underneath it, so routes, TLS certificates, and HTTP authentication can be deployed without redeploying application workloads.

  • Monitoring behind the metrics you read

    Monitoring components are deployed with the cluster unless you turn them off. They are what makes cluster, node, namespace, app environment, and per-service metrics available in Wodby, rather than a monitoring stack you assemble and maintain yourself.

  • Network isolation between app environments

    On supported providers, Wodby installs Kubernetes network policies in each app environment namespace that deny ingress by default, allow traffic within the environment, and allow the public edge in. App environments stay isolated from one another.

  • A secure path to the Kubernetes API

    An FRPC proxy tunnel connects Wodby to your cluster’s Kubernetes API, so the cluster does not need to expose its control plane to operate through Wodby.

  • Provider-specific controllers where they are needed

    Clusters get the extra controllers their provider requires, such as the AWS Load Balancer Controller on EKS, so provider load balancing works without a separate installation step.

  • Upgraded like the rest of the platform

    Infrastructure apps follow the same stack-and-version model as your applications, and cluster-level wiring is tracked separately as an infrastructure version. Both are upgraded from Wodby, on a version policy and maintenance window you set.

Open a provider page to see the infrastructure services a cluster on it runs, or read the cluster infrastructure documentation.

Why Kubernetes

A standard foundation you can take with you

  • Not tied to one provider

    Your apps run on standard Kubernetes, so the same stacks deploy to a managed cloud, your own server, or Wodby Cloud. Changing where you host does not mean rebuilding how you deploy.

  • The same model in every environment

    Development, staging, and production run the same services in the same way, which removes the configuration drift behind most release-day surprises.

  • Room to grow without replatforming

    Start on one small node and move to more replicas, larger clusters, and rolling updates as traffic grows, without changing platforms along the way.

Start from a ready-made stack

A stack is everything an app runs on, such as the runtime, web server, database, and cache, set up to work together. Pick the one for your framework, or for an app you want to host yourself.

Configurable
Choose the components, their versions, and the settings each environment runs with.
Kept up to date
Wodby maintains the software in every stack. Security fixes and new versions arrive as updates you apply on your own schedule.
Reusable
Reuse a stack across applications and environments, from development to production.

Get started

Start with the cluster option that fits your team

Try the workflow on a free demo cluster, or connect your own cloud account or server and deploy your first stack.