OpenClaw Setup Guide: Self-Hosted vs Managed Hosting (2026)
Two ways to set up OpenClaw
There is no single "right" way. Self-hosting gives you full control; managed hosting saves you time. This guide walks through both paths side by side so you can see exactly what each involves.
Disclosure: ClawAgora is our product. We include both paths honestly.
Path 1: Self-hosted on a VPS
What you need before starting
- A VPS provider account (DigitalOcean, AWS, Linode, etc.)
- Basic Linux command-line skills (SSH, package management, file editing)
- A domain name (recommended, ~$12/year)
- A payment method for the VPS ($6–$48/month)
- AI API keys if you want agent messaging (separate from hosting cost)
Step 1: Provision a VPS
On your provider, create a new server:
- OS: Ubuntu 22.04 LTS
- Specs: At least 1 vCPU, 2 GB RAM (4 GB+ recommended)
- Region: Closest to your users
Configure SSH access. Set up a firewall allowing ports 22 (SSH), 80 (HTTP), and 443 (HTTPS).
Step 2: Install dependencies
SSH into your server and install the required software:
# Update system packages
sudo apt update && sudo apt upgrade -y
# Install Node.js v18+
curl -fsSL https://deb.nodesource.com/setup_18.x | sudo -E bash -
sudo apt install -y nodejs
# Install Python 3 and pip
sudo apt install -y python3 python3-pip
# Install nginx
sudo apt install -y nginx
# Install Certbot for SSL
sudo apt install -y certbot python3-certbot-nginx
Step 3: Install OpenClaw
Clone the OpenClaw repository, install dependencies, and configure environment variables:
git clone https://github.com/openclaw/openclaw.git /opt/openclaw
cd /opt/openclaw
npm install
cp .env.example .env
# Edit .env with your configuration
Step 4: Configure nginx and SSL
Point your domain's DNS A record to your server's IP address. Then configure nginx:
server {
server_name your-domain.com;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
}
}
Run Certbot to get a free SSL certificate:
sudo certbot --nginx -d your-domain.com
Step 5: Set up process management
Create a systemd service so OpenClaw starts automatically:
# /etc/systemd/system/openclaw.service
[Unit]
Description=OpenClaw Runtime
After=network.target
[Service]
Type=simple
User=www-data
WorkingDirectory=/opt/openclaw
ExecStart=/usr/bin/node server.js
Restart=on-failure
Environment=NODE_ENV=production
[Install]
WantedBy=multi-user.target
Enable and start:
sudo systemctl enable openclaw
sudo systemctl start openclaw
Self-hosted total setup time
- Experienced Linux user: 2–4 hours
- Learning as you go: 4–8 hours
- Ongoing maintenance: 2–4 hours/month
Path 2: Managed hosting
Several platforms offer managed OpenClaw hosting so you can skip the infrastructure work. The two main options in 2026 are ClawAgora and MyClaw.ai.
ClawAgora
ClawAgora is a managed hosting platform and community-driven template library. You get dedicated compute, AI agent messaging, and access to share and discover workspace templates.
What you need before starting
- An email address
- A payment method
That's it.
Step 1: Sign up and subscribe
Go to clawagora.com and create an account. Navigate to Pricing and choose a plan:
| Plan | Monthly | Compute | RAM | AI Messages |
|---|---|---|---|---|
| Spark | $29.90 | 1 OCPU | 4 GB | 300 |
| Forge | $59.90 | 2 OCPU | 8 GB | 1,500 |
| Blaze | $109 | 4 OCPU | 16 GB | 5,000 |
| Inferno | $239 | 4 OCPU | 16 GB | 15,000 |
Complete payment through Stripe.
Step 2: Provision and start using
Go to the Instance page. Click Provision. Your workspace environment is created automatically:
- Compute instance on Oracle Cloud Infrastructure
- Networking and firewall configured
- SSL certificates issued and managed
- OpenClaw runtime installed
- AI messaging system connected
Install skills from the community library or from external registries, and start using the chat interface.
ClawAgora total setup time
- Under 10 minutes from signup to a running workspace
- Zero ongoing maintenance — updates, SSL, backups handled automatically
MyClaw.ai
MyClaw.ai is a simpler managed option focused on personal AI assistants. It offers a more streamlined experience with less configuration.
Plans start at ~$15/month. MyClaw.ai focuses on ease of use rather than workspace customization — think of it as a turnkey personal assistant rather than a full workspace environment.
Best for: People who want a simple personal AI assistant without the workspace customization, community template library, or dedicated compute resources that ClawAgora provides. If you need a quick, affordable way to run a personal OpenClaw-based agent and don't need advanced skills or workspace templates, MyClaw.ai is worth considering.
Tradeoffs vs. ClawAgora: MyClaw.ai has a lower entry price but does not include dedicated compute resources, a community template library, or the same level of workspace customization. ClawAgora gives you a full environment you can extend; MyClaw.ai gives you a simpler, more constrained experience.
Side-by-side comparison
| Aspect | Self-hosted | ClawAgora | MyClaw.ai |
|---|---|---|---|
| Initial setup time | 2–8 hours | Under 10 minutes | Under 10 minutes |
| Monthly cost | $6–$48 + API keys | $29.90–$239 (all-inclusive) | ~$15+/month |
| AI messaging | BYO API keys ($20–$100+/mo) | Included in plan | Included |
| SSL certificates | Manual (Certbot) | Automatic | Automatic |
| Updates | Manual | Automatic | Automatic |
| Workspace customization | Full | Full | Limited |
| Template library | No | Yes | No |
| Dedicated compute | Yes (your server) | Yes (1–4 OCPU) | Shared |
| Infrastructure control | Full | Limited | Minimal |
Which path should you choose?
Choose self-hosted if you have Linux skills, want full control, need a specific cloud provider, or have compliance requirements.
Choose ClawAgora if you want dedicated compute, a community template library, full workspace customization, and included AI messaging — without managing infrastructure.
Choose MyClaw.ai if you want a simple, affordable personal AI assistant and don't need advanced workspace customization or a template library.
All three paths give you a working OpenClaw environment. The difference is what you spend your time on and how much control you need.
Want the managed path? See ClawAgora plans and subscribe, or check out MyClaw.ai for a simpler option. Prefer self-hosting? The OpenClaw docs have detailed installation instructions.
For a detailed cost breakdown of both paths, see ClawAgora vs Self-Hosting OpenClaw. For a broader comparison of all hosting options including ClawHub, ClawMart, and OpenClaw Marketplace, check out Best OpenClaw Hosting Platforms Compared. Once your workspace is running, our skills installation guide covers how to add capabilities.
Frequently Asked Questions
What is the easiest way to set up OpenClaw in 2026?
The easiest way is using a managed platform. ClawAgora ($29.90/month minimum) provides dedicated compute, a community template library, and full customization. MyClaw.ai (~$15/month) offers a simpler personal assistant experience. Both eliminate server setup entirely. Self-hosting is cheaper in raw server costs but requires Linux skills and 2–6 hours of initial setup.
What are the system requirements for self-hosting OpenClaw?
At minimum: 1 vCPU, 2 GB RAM, 25 GB storage, Ubuntu 22.04 LTS (or similar Linux distribution), Node.js v18+, Python 3, and a domain name with DNS configured. For production use with multiple skills, 2+ vCPU and 4+ GB RAM is recommended.
How long does it take to set up OpenClaw?
On ClawAgora (managed): under 10 minutes from signup to a running workspace. Self-hosted: 2–4 hours for someone experienced with Linux, 4–8 hours for someone learning as they go. The self-hosted time does not include ongoing maintenance.
Can I start with managed hosting and switch to self-hosting later?
Yes. OpenClaw workspace configurations are portable. You can export skill definitions and settings from ClawAgora and set them up on your own server. The reverse is also true — you can migrate from self-hosted to managed.
Do I need a domain name for self-hosted OpenClaw?
Technically no — you can access it by IP address. But for SSL certificates (required for secure connections) and a professional setup, a domain name is strongly recommended. Domains cost about $12/year from most registrars.
Frequently Asked Questions
- What is the easiest way to set up OpenClaw in 2026?
- The easiest way is using a managed platform. ClawAgora ($29.90/month minimum) provides dedicated compute, a community template library, and full customization. MyClaw.ai (~$15/month) offers a simpler personal assistant experience. Both eliminate server setup entirely. Self-hosting is cheaper in raw server costs but requires Linux skills and 2–6 hours of initial setup.
- What are the system requirements for self-hosting OpenClaw?
- At minimum: 1 vCPU, 2 GB RAM, 25 GB storage, Ubuntu 22.04 LTS (or similar Linux distribution), Node.js v18+, Python 3, and a domain name with DNS configured. For production use with multiple skills, 2+ vCPU and 4+ GB RAM is recommended.
- How long does it take to set up OpenClaw?
- On ClawAgora (managed): under 10 minutes from signup to a running workspace. Self-hosted: 2–4 hours for someone experienced with Linux, 4–8 hours for someone learning as they go. The self-hosted time does not include ongoing maintenance.
- Can I start with managed hosting and switch to self-hosting later?
- Yes. OpenClaw workspace configurations are portable. You can export skill definitions and settings from ClawAgora and set them up on your own server. The reverse is also true — you can migrate from self-hosted to managed.
- Do I need a domain name for self-hosted OpenClaw?
- Technically no — you can access it by IP address. But for SSL certificates (required for secure connections) and a professional setup, a domain name is strongly recommended. Domains cost about $12/year from most registrars.