Before & After Clawrium
Before: Manual SSH chaos
You (laptop)
│
├── SSH to pi-lab ──────> configure agent
│ restart service
│ check logs
│ update config...
│
├── SSH to nuc-01 ──────> same manual steps
│
└── SSH to dev-box ─────> same manual steps
❌ No unified view
❌ Config drift between machines
❌ Manual secret managementAfter: One CLI, all agents
You (laptop + clawctl CLI)
│
└── clawctl ──┬── pi-lab ───> openclaw
│
├── nuc-01 ───> openclaw
│
└── dev-box ──> hermes
✅ Single command center
✅ Consistent configuration
✅ Centralized secretsSee your entire fleet with one command:
$ clawctl agent get NAME TYPE HOST PROVIDER STATUS AGE ───────────────────────────────────────────────────────────────── oc-discord openclaw pi-lab anthropic running 3d 4h oc-work openclaw nuc-01 anthropic running 12h hm-research hermes dev-box openrouter running 2h
🌐 Universal Agent Support
Clawrium supports OpenClaw, Hermes, and ZeroClaw end-to-end today. Additional agent types are planned.
⚙️ Normalized Configuration
One config format for every agent. Define your preferences once and Clawrium translates them into each agent's native format.
🔓 Multi-Model Freedom
Run any model across your fleet: open models like Nemotron, providers like OpenAI and Anthropic, or local with Ollama.
Who Uses Clawrium?
Homelabbers
Run AI assistants on your Raspberry Pis, NUCs, and spare hardware. Experiment with different models without cloud costs.
Teams
Standardize agent deployment across developer machines. Share configurations and ensure everyone runs the same setup.
Small Orgs
Deploy purpose-built agents for different departments. A research agent, a support agent, a coding agent - each isolated.