Deployment Options
Choose how to run your OpenClaw AI assistant. From local development to production cloud deployment, find the setup that fits your needs.
Local Deployment
EasyRun OpenClaw Gateway locally on your own machine (macOS, Linux, or Windows via WSL2). The Gateway binds to loopback (127.0.0.1) by default for security, accessible only from the local machine.
Advantages
- Simplest setup
- No network exposure
- Full control
Considerations
- Must be running locally
- No remote access by default
Requirements
VPS Deployment
MediumDeploy OpenClaw on a Virtual Private Server for always-on availability. Run as a systemd service on any Linux VPS with persistent state and remote access via SSH tunnel or Tailscale.
Advantages
- Always-on availability
- Accessible from anywhere
- Cheap hosting options
Considerations
- Requires server management
- Monthly hosting cost
Requirements
Cloud Deployment
MediumDeploy OpenClaw on containerized cloud platforms like Fly.io for managed infrastructure, automatic scaling, and global edge locations. Persistent volumes store state across deployments.
Advantages
- Managed infrastructure
- Global edge locations
- Automatic TLS
Considerations
- Higher cost
- Vendor lock-in
Requirements
Docker Deployment
MediumRun OpenClaw in a Docker container for portable, reproducible deployments. Use Docker Compose for easy orchestration with persistent volumes.
Advantages
- Portable
- Reproducible
- Isolation
Considerations
- Docker overhead
- Additional complexity
Requirements
Deployment Comparison
| Feature | Local Deployment | VPS Deployment | Cloud Deployment | Docker Deployment |
|---|---|---|---|---|
| Difficulty | Easy | Medium | Medium | Medium |
| Cost | Free | $5-20/mo | Pay per use | Hosting cost |
| 24/7 Availability | — | ✓ | ✓ | ✓ |
| Scalability | — | Manual | Auto | Container |
| Best For | Personal AI assistant | 24/7 AI assistant | Production deployments | Self-hosted infrastructure |