Index / ZeroClaw · updated Oct 2, 2026
ZeroClaw
zeroclaw-labs/zeroclaw · healthy · rank 7 of 43 by stars
A single-binary Rust agent runtime that positions itself as the lean, self-owned alternative to OpenClaw — 30+ channels, ~20 LLM providers, and a plugin system in one deployable artifact. Extremely active development with a security-hardening focus (OIDC, plugin admission, opt-in browser automation) and a strong 'you own the machine' philosophy.
Facts
Repository
Runtime
Posture
Community
Security breakdown
Composite 82 / 100 · how these are scored
higher is safer
higher is safer
higher is safer
higher is safer
higher is riskier
Model access
Read from the repository, not written by a model · 117 files examined
5 providers · runs locally · gateway support
Pinned models
Pin last edited 6 days ago
Evidence
Decision
Why choose ZeroClaw over OpenClaw?
Why choose this
- Dramatically lower resource footprint — single Rust binary runnable in tens of MB of RAM
- Simpler deployment: one install script, no orchestrated service stack
- Runs on constrained hardware (ARM NAS, Raspberry Pi, Android) where OpenClaw is impractical
Tradeoffs
- No equivalent of OpenClaw's Control UI dashboard and Canvas features
- Younger project (v0.8.x) with pre-1.0 stability and frequent breaking-change risk
- Plugin/component system still under active construction with admission bugs being fixed
Best fit
- Users who want a lightweight, low-RAM agent on small hardware (NAS, Raspberry Pi, old laptops)
- Self-hosters who want one binary instead of a multi-service stack
- Operators needing many chat channels (Telegram, Discord, Matrix, email) from one runtime
Avoid if
- You want a polished GUI/dashboard experience out of the box
- You need a mature, stable plugin ecosystem with third-party extensions
- You prefer managed cloud hosting over running your own binary
Strong evidence from README, release data, and multiple independent ecosystem digests confirming ZeroClaw's positioning as a lightweight OpenClaw alternative. Uncertainty remains around multi-user support and real-world plugin maturity since the plugin system is visibly mid-refactor in recent commits.
AI layer reviewed Sep 21, 2026 · how this is written
Star activity
32,927 stars today
Overview
ZeroClaw is an agent runtime written in Rust and distributed as a single binary, built around four ownership principles: you own the agent, the data, and the machine it runs on. It connects to roughly 20 LLM providers (Anthropic, OpenAI, Ollama, and others), reaches users through 30+ channels including Discord, Telegram, Matrix, email, voice, and webhooks, and acts through tools such as shell, browser, HTTP, hardware, and custom MCP servers. Installation is a one-line curl script or a prebuilt Windows binary, followed by an interactive quickstart.
Architecturally, it contrasts sharply with OpenClaw's heavier stack: instead of a multi-service deployment with a Control UI, ZeroClaw is a single configurable process designed to run anywhere — from a $200 ARM NAS to Android devices — with a memory footprint measured in tens of megabytes. Recent commits show heavy investment in correctness and security hardening: an OIDC token-verification provider, plugin component admission with exact payload byte validation, opt-in gating for full browser automation, deterministic tool-spec ordering for prompt-cache stability, and token accounting on history-trim events.
The trade-off is maturity. At v0.8.5, ZeroClaw is pre-1.0 with a plugin system still being actively rebuilt, and it lacks OpenClaw's dashboard, Canvas, and polished multi-agent UI. It is best understood as the infrastructure-first, resource-frugal member of the Claw family: ideal for self-hosters who want an always-on assistant on cheap hardware, less ideal for users who want a batteries-included graphical experience.