Deploy OpenClaw on Kubernetes

Run OpenClaw on Wodby with a managed stack built for private gateway access, repeatable environments, and a simpler deployment workflow on Kubernetes or self-hosted Kubernetes.

Deploy OpenClaw faster with a managed stack

Start from an OpenClaw stack designed for Wodby instead of wiring together runtime services, networking, and infrastructure settings by hand.

Keep gateway access private by default

Use Tailscale integration to keep your OpenClaw gateway available inside your tailnet instead of exposing it directly to the public internet.

Run on your infrastructure or Wodby Cloud

Choose managed Kubernetes, budget self-hosted Kubernetes, or Wodby Cloud while keeping the same operating model.

Build and release

What a OpenClaw deployment does on Wodby

Deploying OpenClaw on Wodby begins with a choice that cannot be changed later: the private access integration for the whole app. After the first successful deployment Wodby sets up the gateway's private address.

Choose the access integration first

For this stack the whole app must use Protected access, and its network type must be Private. A compatible Private App Access integration, such as Tailscale or Cloudflare, is selected while the app is created.

Approve each browser once

A browser that connects for the first time waits until you approve it from a web terminal, after which the page connects by itself. A private window asks again once it has been closed.

Configuration is rewritten on start

On every start OpenClaw writes its configuration file from the environment variables of the service. Anything those variables do not cover is changed in the config template on the service, followed by a deployment.

Keys and tokens are variables

Provider keys and bot tokens are added as environment variables on the OpenClaw service and take effect with the next deployment. With no provider key at all, the configuration contains no agent list.

Read the OpenClaw stack guide for setup steps, settings, and limits.

Step-by-step guide

Step-by-step OpenClaw deployment guide

If you want the exact flow for setting up Tailscale, deploying the OpenClaw stack, copying the gateway token, and approving devices, use the full walkthrough guide.

It covers deploying OpenClaw privately with Tailscale on Wodby from the first integration step through connecting your local CLI and nodes.

A practical deployment model for OpenClaw gateways

OpenClaw workloads benefit from predictable deployments, private network access, and an always-on runtime that is not tied to a developer laptop or workstation.

Wodby makes that practical by packaging OpenClaw as a managed stack with Tailscale integration on top of Kubernetes and self-hosted Kubernetes, so teams can deploy gateways cleanly without building the hosting layer from scratch.

A practical fit for OpenClaw workloads

  • Keep OpenClaw gateway access private inside your tailnet.
  • Run always-on gateways on dedicated servers, VMs, or managed clusters.
  • Reuse the same deployment flow across development and production environments.
  • Reduce custom work around provider integrations and infrastructure setup.

What you get with OpenClaw on Wodby

How OpenClaw deployment works on Wodby

  1. 1

    Choose the infrastructure model that fits: managed Kubernetes from your preferred provider, Wodby Cloud, or self-hosted Kubernetes on your own servers for budget hosting.

  2. 2

    Create a new app from the OpenClaw stack and add the required integrations such as Tailscale and your preferred AI provider.

  3. 3

    Configure networking, environment variables, and access settings for your gateway.

  4. 4

    Deploy the app, connect through your tailnet, and approve devices from the gateway workflow.


Read more about stack management in our documentation.

Suitable for private gateway and agent workloads

If you want to run OpenClaw in an always-on environment with tighter network access and a repeatable deployment process, this setup is built for that model.

Wodby gives you a managed OpenClaw gateway stack with the small set of integrations that actually matter for this workload.

Still choosing where to run it? Compare the options on the OpenClaw hosting page.

Start deploying

Want to launch OpenClaw with less setup overhead?

Start with Wodby's managed OpenClaw stack, connect your repo, and handle deployments, environments, and operations in one place.

Hosting options

Run your apps where it suits you

In your own cloud account, on a server you already rent, or on Wodby Cloud. The stacks and the deployment workflow are the same on all three, and Wodby maintains the cluster.

Lowest cost

Kubernetes on your own server

Use a dedicated server or VM you already rent, from Hetzner, OVH, or any other host. Wodby installs Kubernetes on it, keeps it up to date, and deploys your apps.

  • No managed control plane to pay for
  • One command installs Kubernetes on the server
  • Join more servers as worker nodes when you need capacity
  • Operating system updates install when you choose
Explore self-hosted Kubernetes

We handle everything

Wodby Cloud

Deploy without a cloud account or a server of your own. Wodby creates and operates the cluster, and you pay for the nodes and storage you run.

  • Nothing to connect or set up before your first deploy
  • A free demo cluster to try the workflow first
  • Scales between the node counts you set
  • The same stacks and deployment workflow as your own cluster
See Wodby Cloud
Stack preview

OpenClaw stack preview

Stack serviceBase serviceRole
OpenClaw
OpenClawPrimary

Keep moving

Explore the OpenClaw setup, then start your own deployment

Once you've reviewed the stack structure, create an account to launch OpenClaw, connect your repository, and keep delivery inside the same workflow.

Trusted by developers and businesses worldwide since 2015

Wodby is a reliable cloud infrastructure partner for your business.
See what our customers say about their experience with Wodby.

  • We moved our Drupal hosting to use Wodby and changed our development workflow to use Docker at the same time. Now we can concentrate on Drupal development and we're not losing time configuring servers etc. When a site needs additional resources or hosting in a different region we can be way more responsive as deploying a new instance takes no time at all.

    Tony Miller
    Eighty Options
    Tony Miller, Eighty Options
  • Wodby’s innovative infrastructure helped us to increase the speed and simplify our app deployment, while also leaving us the freedom of handling our hosting and not locking us on a specific pattern. We are now much more robust for future growth and will be able to innovate faster.

    Martin Normann Lund
    Ramsalt Lab
    Martin Normann Lund, Ramsalt Lab
FAQ

Frequently Asked Questions

Have questions? We've got answers. If you don't see your question here, feel free to reach out.

Get started

Ready to deploy OpenClaw?

Choose Wodby Cloud, managed Kubernetes, or your own server, then deploy stacks with CI/CD, backups, SSL, integrations, and environment management in the same platform.

  • Run the same stack workflow on Wodby Cloud, managed Kubernetes, or your own server
  • Deploy app environments for production, staging, previews, and development
  • Use Wodby CI or your existing pipeline with the Wodby CLI
  • Keep backups, certificates, integrations, and access control in the platform

Start for free

No credit card required
$0/month
  • 10 app services
  • 30 minutes of integrated CI
  • 5 GB of private registry
  • Stacks & integrations
  • Technical domains with SSL
Create free account
Upgrade when you need more capacity