Deploy your own OpenClaw in the EU in 5 minutes (no VPS)
You want your own OpenClaw: an agent gateway with its Control UI on your own URL, your own model keys and your data in the EU. The usual way is to rent a VPS, install Docker, set up a reverse proxy, get a TLS certificate
You want your own OpenClaw: an agent gateway with its Control UI on your own URL, your own model keys and your data in the EU. The usual way is to rent a VPS, install Docker, set up a reverse proxy, get a TLS certificate, mount a volume and keep the box patched. That takes an evening before you even sign in.
This guide does it on QuickTane, an EU container platform, from a ready-made OpenClaw template. You don't touch a server.
What you get
- Your own OpenClaw instance (the upstream
ghcr.io/openclaw/openclawimage) on an HTTPS URL - A generated gateway token: the Control UI and every client need it
- A persistent volume at
/home/node/.openclawwith nightly backups (the last 7 are kept) - A health check, live logs and a browser console for the service
- Hosting in the EU
It runs on the Large size (1 vCPU guaranteed, bursts to 4, 2 GiB RAM). That's €16/month on the Hobby plan, excl. VAT.
1. Pick the OpenClaw template
Open quicktane.com/openclaw-hosting and click Deploy OpenClaw. After you sign up, the create page opens with the template already selected: image, port, volume, health check and a fresh gateway token. You can change any of it before you create.
Give the service a name, for example openclaw.
2. Copy the gateway token
The template generates OPENCLAW_GATEWAY_TOKEN for you. Copy it now. Environment values are stored encrypted and never shown again after you save. If you lose the token, set a new value in the service's settings and redeploy.
3. Create and wait for the first start
Click Create service. The first start takes a few minutes while OpenClaw prepares its state. You can watch it in the Logs tab. The service shows Running once the health check passes.
4. Open your URL and sign in
Open the service's URL (https://<name>-<id>.quicktane.app) and sign in with the gateway token.
You don't need to configure allowed origins: the service's own URL, and any custom domains you add, are already allowed for the Control UI.
5. Approve your browser, once
OpenClaw asks each new browser to be approved once. Open the service's Console tab and run:
node /app/openclaw.mjs devices list
node /app/openclaw.mjs devices approve <requestId>
Back in the browser, the Control UI connects. That's it: your own OpenClaw, in the EU.
6. Add your model keys
OpenClaw doesn't come with a model. Add your provider keys (OpenAI, Anthropic, …) as environment variables in the service's settings, or configure them in the Control UI. They are your keys and your usage.
A few tips
- Keep the token secret. It grants full operator access to the gateway, and the agent can run commands inside the service.
- Only using chat channels (Telegram, Discord, …)? Make the service internal, so the Control UI isn't on the public internet.
- Upgrades: deploy a newer image tag from the dashboard, or from CI with one step. The volume keeps your state.
-
Your own domain: add
agent.yourdomain.comwith a CNAME and the certificate is issued automatically (custom domains, paid plans).
Why not a VPS?
A VPS is cheaper per CPU if you enjoy running servers. Here you skip the reverse proxy, the certificates, the backups and the OS updates. You pay a flat price per size, and the instance is up in a few minutes.
OpenClaw is MIT-licensed; QuickTane is not affiliated with the OpenClaw project.
Disclosure: this post was written by the team behind QuickTane.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.