OpenClaw is powerful but can be unwieldy. Evolve helps manage a group (aka pod) of OpenClaw instances for individuals and SMBs who can install software and care about their data — but don't want to spend weekends managing AI infrastructure.
At the center is evo — an OpenClaw bot that knows your pod end-to-end and resolves things in conversation. Underneath is a full dashboard with real depth — usage, security, applications, self-improvement suggestions — for when you want to dig in. Chat handles the common path; the dashboard is there when you want detail.
Evolve is opening up soon. Leave your email and we'll send you access the moment the code goes public — plus a hand with getting your first pod running.
These are the issues we hear about most often from people running OpenClaw bots. This is what Evolve is built to solve.
Evo is an OpenClaw bot that knows your pod end-to-end. Talk to evo and it resolves things — finds the suggestion, applies it, verifies, reports. The dashboard is still real and substantial underneath: usage graphs, credentials, applications, security audits, self-improvement suggestions. Chat for the common path; dig into the dashboard when you want detail.
Open the admin UI and the first thing you see is evo's short report on the state of things, plus a conversation thread to address any of it. Say "snooze every team_bot_a alert until tomorrow" or "fix the cron caps issue" — evo finds the matching change, applies it, verifies, and reports done.
Wherever you are in the dashboard, evo is on the right with the context of that page. Open Alerts and ask "why is this firing?" — evo sees the same signals you see. Switch pages and the conversation context switches with you; each page keeps its own thread.
Chat in the dashboard, DM evo on Telegram, or use the evo keyword from any bot's thread on Signal, iMessage, Slack, or Discord. One bot, one set of tools, one long-term memory. Improvements to evo's instructions land everywhere at once.
Evolve helps you run your OpenClaw pod from the ground up.
Take a bare Mac — or an Ubuntu VPS — to a running pod in one pass. The setup wizard creates the service user, installs OpenClaw, deploys the plugin, wires the scheduled jobs, and walks you through your first bot.
evolve-admin setup --fresh handles everything — service user, OpenClaw install, plugin, channel tokens, launchd jobs. About 30 minutes when you have your keys ready.
/start requests auto-approve so you skip the code round-trip. Single-user ↔ multi-user toggle per bot.Health monitoring, auto-healing, and version management — so a downed gateway, a stale plugin, or an OpenClaw upgrade doesn't quietly take a bot offline.
Vigilant by default, friendly by design. Security audits and cost controls run in the background, surface plain-language findings, and gate every behavior change through a signed approval pipeline.
warn alerts you, downgrade drops the session tier and pauses non-critical crons, hard trips an L1 breaker that refuses gateway calls. Caps roll at midnight in the pod's local timezone. A behavioral Cost Efficiency Score grades the routing choices each bot is making.$/turn, effective cost per 1k tokens (cache-aware), spend, or share. Filter by provider, pricing band, bot, or audience. The transpose of per-bot usage — built for tuning model choice by comparing within a band or across providers.
fast / standard / power) feeds a hierarchical routing cascade: classifier → operator default → per-user override. Maintenance sessions go to Haiku; productive sessions stay on Sonnet. Users can set their own default per bot via evo tier in any thread — it persists.
A bot that can't reach your calendar, email, or notes is a toy. Evolve gives you the capability surface — installable skills, configurable plugins, and the applications that combine them into something actually useful.
app-changes or app-scan and it does the rest.The self-improvement layer. A portfolio of specialized coaches watches your pod and proposes specific, falsifiable improvements; evo resolves them in chat end-to-end. The Continuity Engine closes the statelessness gap. The Gallery and Forge let you grow the pod's capabilities deliberately. The approval pipeline is what makes all of this safe — RSI applied to applications, not raw prompts, with a human in the loop on every change.
evo improve "this could be better" from any thread; evo captures it, drafts a body, and stages it as a Draft. Promote with one click — it lands as a real GitHub issue on the repo you pick. Inbound issues filed by other people on repos you maintain get LLM-triaged (category, urgency, draft reply) and queued for review; an opt-in auto-response policy with a 24-hour undo handles the obvious cases.
The usage layer. Evo is the front door and the panel that follows you. Coaches do the proactive watching so you don't have to. The Claude Desktop bridge lets you bring pod context into a deep-work session when you want it.
evo keyword from any bot's thread on Signal, iMessage, Slack, or Discord. All routes hit one OpenClaw bot — same SOUL, same tools, same long-term memory.
The most important layer that doesn't show up in a feature matrix. Evolve is built to feel like it was made by people who care about your experience — not by a committee writing a roadmap.
A growing catalog of installable skills covering messaging, productivity, home, dev, and creative work. OAuth flows, key rotation, health monitoring, and credential handling — all handled.
Evolve sits in a specific spot in the market. If you recognize yourself in the cards below, it's probably for you. If you don't, that's useful information too.
One bot per family member, plus a household coordinator. Domain-compartmentalized — health doesn't see ventures, ventures doesn't see giving.
Designers, contractors, planners, real estate agents. A studio bot plus a bot per active client engagement. Existing tools (Studio Designer, QuickBooks, Asana) keep working.
Lawyers, accountants, consultants. One or two bots. Client data stays on a Mac in your office. No cloud roundtrip on local-system integrations like iMessage and Obsidian.
If you have a dedicated AI ops function, look at Preloop. Evolve doesn't try to be your platform.
If one OpenClaw instance is all you need, you'll find Evolve heavy. The wins compound when you have several.
Evolve runs on hardware you own, on purpose. There's no cloud control plane to sign up for.
Want more detail? The product vision doc goes deeper on positioning, architecture, and what's explicitly out of scope.
Bots cannot influence their own management layer. Every production change requires human approval.
evo conversational interface.Full checklist: pre-install-checklist.md
You can install Evolve on an existing OpenClaw instance or create a new pod from scratch using the Evolve setup wizard.
python3 --version node --version # brew (macOS) / apt (Linux) install node if needed
sudo git clone https://github.com/evolve-ops/evolve /Users/Shared/evolve-repo sudo python3 -m venv /Users/Shared/evolve-venv sudo /Users/Shared/evolve-venv/bin/pip install -e /Users/Shared/evolve-repo/packages/admin/
evolve service user, installs OpenClaw, deploys the plugin, and wires the scheduled jobs. Have your API keys, channel tokens, and a private GitHub repo URL ready.sudo evolve-admin setup --fresh
open http://localhost:5050
Ran into something? File a bug report or start a discussion.