The question hits every OpenClaw user eventually: should I run this myself or let someone else handle the infrastructure?

After Anthropic's April 4, 2026 subscription change — which cut API credit coverage for third-party tools — thousands of users suddenly needed to think about hosting for the first time. If you were on a subscription plan that included Claude API access, that coverage is gone. You now need your own API key and a place to run OpenClaw.

This guide covers both paths in full detail. Self-hosting with Docker is technically achievable if you know your way around a server. Managed hosting is faster and cheaper for almost everyone else. We'll show you exactly what each involves so you can make the call.

Self-hosting vs managed hosting — what's the real tradeoff?

The debate usually starts with "self-hosting is free." That's wrong. Here's what the comparison actually looks like:

Factor Self-Hosting Managed Hosting
Setup time 4–8 hours (first time) Under 60 seconds
Monthly server cost $4–$12/mo VPS $3.99/mo all-in
Monthly maintenance time 2–5 hours Zero
SSL / HTTPS Manual (Let's Encrypt) Included
Updates Manual pulls + redeploys Automatic
Uptime monitoring Set up yourself Included
Backups Set up yourself Included
Skills / Marketplace Not available Full marketplace access
Technical knowledge required Docker, Linux, DNS, SSL None
Control over configuration Full Standard config

The honest summary: self-hosting gives you full control at the cost of significant time investment. Managed hosting gives you a running instance in under a minute at a lower monthly cost. For most users, the control benefit of self-hosting doesn't justify the time cost.

What you need to self-host OpenClaw

Before you start, make sure you have all of this:

Technical prerequisites

⚠ Heads up on VPS sizing: OpenClaw's background processes (memory indexing, tool execution) are CPU-bound. A $4/mo shared vCPU instance will struggle under real workloads. $6–$8/mo for a dedicated vCPU is the practical floor.

Self-hosting step by step

This is the full setup path. Budget 4–6 hours the first time.

1

Provision a VPS and configure SSH

Create a new Ubuntu 22.04 droplet/instance. Set up SSH key authentication — disable password auth. Create a non-root user with sudo privileges. Do not run as root.

2

Install Docker and Docker Compose

Use Docker's official install script for Ubuntu. Verify with docker --version and docker compose version. Add your user to the docker group (usermod -aG docker $USER).

3

Clone the OpenClaw repository

Pull the latest release tag from the OpenClaw GitHub repo. Do not run off main — use a versioned release tag for stability.

4

Configure your environment file

Copy .env.example to .env. Set your Anthropic API key, a strong secret key, your domain, and any optional integrations (GitHub, Slack, etc.). This file must never be committed to source control.

5

Configure DNS

In your DNS provider, create an A record pointing your subdomain (e.g. ai.yourdomain.com) to your VPS IP. Wait for propagation — typically 5–60 minutes. Verify with dig or a DNS checker.

6

Set up Caddy as a reverse proxy with SSL

Caddy auto-provisions a Let's Encrypt certificate for your domain. Write a minimal Caddyfile that proxies port 443 to OpenClaw's internal port. Start Caddy as a system service.

7

Start the application stack

Run docker compose up -d from the project directory. Check container health with docker compose ps. Tail logs with docker compose logs -f to catch any startup errors.

8

Verify and harden

Confirm HTTPS is working. Set up UFW firewall rules (allow 22, 80, 443 — block everything else). Enable automatic security updates. Test that OpenClaw loads and your API key works.

After step 8, you have a working OpenClaw instance. Congratulations — you now own a small piece of infrastructure that needs ongoing attention.

The Caddyfile (minimal example)

Caddyfile
ai.yourdomain.com { reverse_proxy localhost:3000 encode gzip header { Strict-Transport-Security "max-age=31536000; includeSubDomains" X-Content-Type-Options nosniff X-Frame-Options DENY } }

The docker-compose.yml (minimal example)

docker-compose.yml
services: openclaw: image: openclaw/openclaw:latest restart: unless-stopped ports: - "3000:3000" env_file: .env volumes: - openclaw_data:/app/data redis: image: redis:7-alpine restart: unless-stopped volumes: - redis_data:/data volumes: openclaw_data: redis_data:
🔴 Security note: Never expose OpenClaw's port 3000 directly to the internet. Always route through Caddy or Nginx with SSL. Exposed HTTP ports have been exploited in the wild — your API key will be compromised within hours on a misconfigured server.

The ongoing work nobody warns you about

The setup is a one-time cost. Maintenance is the recurring one. Here's what you'll be doing every month:

Updates

OpenClaw ships updates — new features, bug fixes, security patches. On managed hosting, these apply automatically. On self-hosted, you need to: watch the release feed, pull the new image, test locally if you're careful, redeploy with docker compose pull && docker compose up -d, and verify nothing broke. A new release every 2–3 weeks means this is a regular task, not a one-off.

SSL certificate renewal

Let's Encrypt certificates expire every 90 days. Caddy renews automatically as long as your server is reachable and DNS is pointing correctly. Nginx requires a cron job for Certbot. If renewal fails for any reason (DNS propagation issue, server restart, Certbot bug), your instance goes HTTPS-broken and users see a certificate error.

Incident response

Servers go down. Docker crashes. Memory fills up. Redis gets corrupted. When this happens at 2am, it's your problem. You'll want uptime monitoring (UptimeRobot free tier works), alerting to your phone, and enough familiarity with the stack to diagnose and fix under pressure.

Security patches

Ubuntu/Debian release security updates continuously. unattended-upgrades handles OS-level patches automatically, but Docker images, npm dependencies, and application-level vulnerabilities require manual attention. Running an outdated Node.js or Redis image is a real exposure.

Backups

OpenClaw stores conversations, memory, configuration, and installed skills in its data volume. If your server fails and you haven't backed this up, it's gone. You need a backup strategy: automated volume snapshots (most VPS providers offer this at $1–2/mo), or rsync to object storage, or both.

💡 Real time estimate: Experienced DevOps engineer maintaining a single OpenClaw self-hosted instance: ~2–3 hours/month. Non-specialist developer: ~4–6 hours/month, with occasional multi-hour incidents. Factor this into your cost calculation.

None of this is your problem on managed hosting. Agent37 handles updates, SSL, monitoring, and backups automatically.

Start Free →

True cost breakdown: self-hosting vs managed

The "self-hosting is free" myth persists because people count server costs but not time costs. Here's the honest math:

Self-hosting costs

At $10/hr (a very conservative rate), 3 hours/month of maintenance = $30/mo in time cost alone, before server fees. At $40/hr, it's $120+/mo. The "free" option is rarely free.

Managed hosting costs (Agent37)

The math is straightforward. Unless you genuinely enjoy running infrastructure — and some people do — managed hosting is the economically rational choice for every knowledge worker using OpenClaw as a tool, not as a project.

Scenario Self-Hosting ($/mo) Managed ($/mo)
Server + infra costs $7–$15 $3.99
Time cost (3 hrs @ $10/hr) $30 $0
Time cost (3 hrs @ $50/hr) $150 $0
Total (low estimate) ~$37–45/mo $3.99/mo
Total (professional rate) ~$157–165/mo $3.99/mo

Managed hosting setup (the easy path)

If you've read this far and decided managed hosting is the right call, here's how to get running on Agent37 — the lowest-cost managed OpenClaw option at $3.99/mo.

1

Create your account

Go to agent37.polsia.app/signup. Enter your email and set a password. No credit card required for the free account.

2

Provision an instance

From the dashboard, click "New Instance." Pick a region. Your isolated OpenClaw runtime provisions in under 60 seconds — no configuration required.

3

Add your Anthropic API key

Paste your key into the instance settings. It's stored encrypted. This is the only credential you manage — everything else is handled for you.

4

Start using OpenClaw

Your instance is live at a dedicated URL. Browse the skills marketplace to add capabilities. No Docker, no DNS, no SSL — done.

If you want to compare Agent37 against other managed providers before committing, see our full breakdown: Best OpenClaw Hosting Alternatives in 2026. Short version: Agent37 starts at $3.99/mo — the next cheapest alternative (xCloud) starts at $24/mo.

Which option is right for you?

Self-host if:

Use managed hosting if:

The second list describes the majority of OpenClaw users. The skills marketplace alone is a meaningful advantage: Agent37's marketplace has pre-built integrations for GitHub, Slack, Google Workspace, and more — deploy them to your instance in minutes instead of building them yourself.

Frequently asked questions

How long does it take to self-host OpenClaw?

Realistically, 4–8 hours for an initial working setup — and that assumes you're comfortable with Docker, reverse proxies, and Linux server administration. Ongoing maintenance (updates, SSL renewals, incident response) adds 2–5 hours per month. Managed hosting on Agent37 provisions in under 60 seconds.

What is the cheapest way to host OpenClaw?

Agent37 managed hosting starts at $3.99/mo — the cheapest option available in 2026. Self-hosting on a VPS costs $6–$15/mo in server costs alone, before your time. When you factor in maintenance time, managed hosting is almost always the lower total cost. See our full pricing comparison.

Do I need technical skills to host OpenClaw?

Self-hosting requires comfort with Docker, command-line Linux, DNS configuration, and SSL certificates. If any of those are unfamiliar, managed hosting is the better path — no technical knowledge required on Agent37, just sign up and you're running.

Can I migrate from self-hosted to managed hosting later?

Yes. OpenClaw supports exporting your data (conversations, memory, settings) as a standard backup file. You can import this into any managed hosting provider. The migration takes about 15 minutes.

Do I need my own Anthropic API key?

Yes, on both self-hosted and managed setups. Since Anthropic's April 4 change removed subscription credit coverage for third-party tools, every hosting approach requires you to bring your own API key. Get one at console.anthropic.com.

What happens if Agent37 goes down?

Agent37 runs on Render's infrastructure with 99.9% uptime SLA, automated failover, and real-time monitoring. In the rare case of downtime, your data is always intact — nothing is stored ephemerally. Compare this to a self-hosted instance: if your VPS provider has an outage or your server crashes, recovery time depends entirely on how well you've set up backups and monitoring.

Skip the setup. Just run OpenClaw.

Agent37 provisions your isolated instance in under 60 seconds. No Docker, no SSL, no maintenance. Updates happen automatically. The skills marketplace is included.

Try Agent37 for $3.99/mo →
Start free · No credit card required · Upgrade when ready