Managed vs Self-Hosted OpenClaw
A practical comparison for teams deciding how to run OpenClaw in production.
Security
| Risk | Self-Hosted | Curate-Me Managed |
|---|---|---|
| CVE patching | You monitor NVD, test patches, deploy manually | Auto-patched within hours of disclosure |
| Sandbox isolation | Docker only (known escape vectors) | 4-tier sandbox: READ_ONLY → FULL_ACCESS |
| Network isolation | Configure iptables/firewall yourself | Network phase separation built-in |
| Skill scanning | No scanning — install anything from ClawHub | ClawHavoc scanner: VirusTotal + YARA + dependency audit |
| PII protection | None by default | 14 regex patterns + Presidio NER, blocks before provider |
| Exposed surface | 42,665 instances found on Shodan | Zero public surface — agents behind gateway auth |
| Audit trail | Manual logging setup | Immutable audit trail for every action |
Recent CVEs
| CVE | CVSS | Impact | Self-Hosted | Curate-Me |
|---|---|---|---|---|
| CVE-2026-25253 | 8.8 | One-click RCE via WebSocket hijacking | Must patch manually | Auto-patched |
| CVE-2026-24763 | 7.5 | Server-Side Request Forgery | Must patch manually | Blocked by network phases |
| CVE-2026-25593 | 7.2 | Sandbox escape via symlink traversal | Must patch manually | Blocked by deny patterns |
| CVE-2026-25475 | 6.8 | MCP skill privilege escalation | Must patch manually | Blocked by vetted allowlist |
| CVE-2026-26322 | 6.5 | Information disclosure via logs | Must patch manually | PII scanning intercepts |
Cost
| Dimension | Self-Hosted | Curate-Me Managed |
|---|---|---|
| Infrastructure | $20-80/mo VPS + Docker + monitoring | Included in plan |
| Engineering time | 4-8 hrs/mo patching, updating, debugging | Zero maintenance |
| LLM API costs | No budget caps — runaway risk | Per-request limits + daily caps |
| Cost visibility | Build your own dashboard | Real-time per-model, per-runner tracking |
| Overspend protection | None | Auto-deny on budget breach + kill switch |
| Total (typical) | $200-500/mo + engineering time | $49/mo (Starter) with governance included |
Real-World Cost Scenarios
Scenario 1: Runaway Agent Loop
- Self-hosted: Agent enters infinite loop overnight → $3,600 OpenAI bill
- Curate-Me: Daily budget cap triggers at $50 → request denied → $50 total
Scenario 2: Model Misuse
- Self-hosted: Developer accidentally uses GPT-4o for logging → $800/mo waste
- Curate-Me: Model allowlist blocks expensive models for non-critical agents
Scenario 3: Security Incident
- Self-hosted: CVE disclosed Friday evening → scramble to patch over weekend
- Curate-Me: Auto-patched before you see the advisory
Setup & Maintenance
| Task | Self-Hosted | Curate-Me Managed |
|---|---|---|
| Initial setup | Hours to days (Docker, gateway, auth, SSL, firewall, monitoring) | 5 minutes (one URL change) |
| Updates | Pull, test, restart manually | Rolling updates, zero downtime |
| Monitoring | Set up Prometheus/Grafana yourself | 41-page ops console included |
| Channel auth | Configure OAuth per channel | Guided setup wizard per channel |
| Scaling | Manual VM provisioning | Auto-provisioned VPS capacity |
| Backups | Configure cron jobs | Automated daily snapshots |
When Self-Hosted Makes Sense
Self-hosting is right for you if:
- You have a dedicated DevOps team with OpenClaw expertise
- You need full control over the execution environment
- You have strict data residency requirements (consider connecting your own machine as a middle ground)
- You’re running in an air-gapped environment
When Managed Makes Sense
Curate-Me managed hosting is right for you if:
- You want to ship agents, not manage infrastructure
- Security patching speed matters to your compliance posture
- You need cost governance and budget enforcement
- You want a full ops console without building one
- Your team is < 20 engineers and DevOps isn’t your core competency
Migration
Switching from self-hosted to managed takes one environment variable change:
# Replace your provider URL with the Curate-Me gateway
OPENAI_BASE_URL=https://api.curate-me.ai/v1/openai
X-CM-API-Key=cm_sk_xxxYour OpenClaw configuration, skills, prompts, and workflows stay exactly the same.