Migrate from self-hosted OpenClaw in 5 minutes
One environment variable. Zero code changes. Your agents, prompts, skills, and workflows stay exactly the same. You just get governance on top.
# Step 1: Replace your provider URL
OPENAI_BASE_URL=https://api.openai.com/v1
OPENAI_BASE_URL=https://api.curate-me.ai/v1/openai
# Step 2: Add your Curate-Me API key
X-CM-API-Key=cm_sk_xxx
# Step 3: There is no step 3.
Migration Timeline
Sign up & get API key
Create account at dashboard.curate-me.ai. Copy your cm_sk_xxx key.
Swap one environment variable
Replace OPENAI_BASE_URL with our gateway endpoint. That's the only code change.
Configure governance policies
Set daily budget, enable PII scanning, choose sandbox tier. All from the dashboard.
Run your first governed session
Launch your agent. Watch cost tracking, audit logs, and security scores populate in real time.
Done. Ship with confidence.
Your agents now have sandbox isolation, cost caps, PII scanning, HITL approvals, and a 41-page ops console.
Zero Disruption, Full Governance
What stays the same
- Your OpenClaw configuration files
- Custom prompts and system messages
- Skill definitions and MCP servers
- Workflow files and automation
- Agent code and business logic
- Git repositories and worktrees
What you gain
- 4-tier sandbox isolation (READ_ONLY → FULL_ACCESS)
- Network phase separation (no exfiltration during execution)
- Per-request cost limits and daily budget caps
- PII scanning — block secrets before they hit LLM providers
- HITL approval queues for sensitive operations
- Model allowlists — control which models each team can use
- 27-event immutable audit trail
- Time-travel debugging — replay any session step-by-step
- 41-page ops console with real-time monitoring
- CI auto-fix — classify, diagnose, and fix build failures
Why migrate now?
OpenClaw's founder Peter Steinberger announced on February 14, 2026 that he is joining OpenAI. The project is transitioning to a foundation with untested governance. Teams running OpenClaw in production face uncertainty about security patches, roadmap direction, and long-term support. Migrating to Curate-Me gives you a managed platform with SLA-backed uptime, dedicated security patching, and a stable roadmap — regardless of what happens upstream.
Common Migration Concerns
Will my agents break?
No. The gateway is a transparent proxy. Your agents don't even know they're running through Curate-Me. Every API call is proxied with zero modification to the request/response format.
What about latency?
The governance chain adds <15ms per request (5 policy checks). LLM inference takes 500ms-30s. The overhead is imperceptible.
Can I go back to self-hosted?
Yes. Swap the URL back to your provider's direct endpoint and remove the API key header. Everything works as before. Zero lock-in.
Do you store my prompts?
We log metadata (model, token count, cost, latency) for your dashboard. Prompt content passes through the governance chain and is not stored unless you explicitly enable request logging.
What about the founder leaving OpenClaw?
Peter Steinberger announced he's joining OpenAI on February 14, 2026. The project is moving to a foundation. With Curate-Me, upstream governance changes don't affect you — we maintain the control plane, security patches, and SLAs independently.
Ready to migrate?
One URL change. Five minutes. Full governance. No lock-in.