What OpenClaw is good at
- MIT licensed and run by the OpenClaw Foundation, a nonprofit: no paid tier and no telemetry by default beyond a version check you can turn off.
- One Gateway serves many chat channels at once, with multi-agent routing, a browser for the agent, skills, and cron jobs, hooks and webhooks.
- Works with the model provider you choose, including local model services.
- Very large community: about 391,000 GitHub stars when checked.
Where OpenClaw breaks
- You run and secure it yourself: keep the Gateway loopback-only behind SSH or Tailscale, and any non-loopback bind needs gateway auth.
- Files under ~/.openclaw can hold channel credentials, OAuth tokens and session transcripts with private messages and tool output, readable by any process or user with disk access.
- In a shared Slack, any allowed sender can make the agent call tools (exec, browser, files), and one sender's prompt injection can lead to data leaks; the docs say to keep personal-data agents private.
- Needs Node 24.16+ or 26, your own model API key (and its costs), and an always-on host such as a VPS or home server for 24/7 use.
When a custom build beats OpenClaw
OpenClaw is itself the build-your-own option; a hosted agent beats it when nobody on the team will patch, monitor and lock down the Gateway.
Setup
Needs a developer. Plan for a developer to set it up and keep it running.
Sources
- docs.openclaw.ai/
- docs.openclaw.ai/gateway/remote
- docs.openclaw.ai/gateway/security/secrets-and-storage
- github.com/openclaw/openclaw
Price checked 9 Oct 2026. If something here is out of date, email indra@kratuva.com and we will fix it.
