openclaw-rs vs ZeroClaw — Rust OpenClaw rewrites compared
ZeroClaw is the most established Rust rewrite of OpenClaw — small static binary, broad provider coverage. openclaw-rs bets on two things ZeroClaw doesn't lead on: TypeScript-plugin compatibility and event sourcing.
The “OpenClaw, but in Rust” space has more than one entrant. ZeroClaw is the most established Rust rewrite — known for a very small static binary and broad LLM-provider coverage. openclaw-rs is a newer entrant that doesn’t try to win on breadth. It bets on two specific things: keeping your TypeScript plugins working, and building the runtime around event sourcing.
Same language, same “single binary, no Node.js” promise — different priorities.
What they share
- Rust, single static binary. No Node.js runtime to install or manage.
- A rewrite of the upstream OpenClaw agent runtime. Both are independent reimplementations, not affiliated with upstream.
- Provider-agnostic LLM calls. Point them at the model you want.
Where ZeroClaw leads
- Maturity and adoption. It’s the de-facto flagship of the Rust-rewrite space.
- Provider breadth. A wide set of built-in LLM provider integrations.
- Binary size. A very small static binary.
If you’re starting fresh, have no TypeScript plugins to carry, and want the most established option with the widest provider list today, ZeroClaw is a reasonable default.
Where openclaw-rs differentiates
- TypeScript-plugin compatibility. Your existing OpenClaw plugins keep running via an IPC bridge — migrate the host to Rust without rewriting the plugins.
- Event sourcing. Sessions are an append-only, replayable event log. That buys you time-travel debugging and an audit trail rather than a mutable, opaque session store.
- Full runtime, built in. axum HTTP/WS + JSON-RPC gateway, embedded Vue 3 dashboard, CLI (
onboard,gateway,doctor,status,config,daemon), and sandboxing (bubblewrap / sandbox-exec / Job Objects). - Encrypted credentials. AES-256-GCM with Argon2id key derivation, at rest.
How to choose
If your priority is adoption and provider breadth today, ZeroClaw is the safe, established pick. If your priority is bringing an existing TypeScript OpenClaw plugin setup to Rust — or you need replayable, auditable session history — openclaw-rs is built for exactly those two cases.
openclaw-rs is an independent implementation by Neul Labs. It is not affiliated with or endorsed by the upstream OpenClaw project or by ZeroClaw.
- You have an existing OpenClaw setup and want to keep your TypeScript plugins running — openclaw-rs bridges them over IPC instead of asking you to rewrite.
- You need a replayable, event-sourced session log — an append-only history you can replay for time-travel debugging and audit trails.
- You want a full runtime (axum HTTP/WS + JSON-RPC gateway, embedded Vue dashboard, CLI, sandboxing) rather than a library.
- You want encrypted-at-rest credentials (AES-256-GCM + Argon2id) built in.
- You want the most established, widely-adopted Rust rewrite today and don't have TypeScript plugins to bring along.
- Breadth of built-in LLM provider integrations is your top priority right now.
- You want the smallest possible static binary and a mature feature set over openclaw-rs's newer plugin-bridge and event-sourcing angle.
FAQ
- What's the main difference between openclaw-rs and ZeroClaw?
- Both are Rust rewrites of the OpenClaw agent runtime that ship as a single static binary with no Node.js required. ZeroClaw is the more established project with broad provider coverage. openclaw-rs differentiates on two things: TypeScript-plugin compatibility (your existing OpenClaw plugins keep working via an IPC bridge) and event sourcing (an append-only, replayable session log for time-travel debugging and audit).
- Can openclaw-rs run my existing TypeScript OpenClaw plugins?
- Yes — that's its core wedge. openclaw-rs runs TypeScript OpenClaw plugins over an IPC bridge, so you can move to a Rust host without rewriting your plugins. If keeping your existing plugin ecosystem matters, that's the reason to pick it over a rewrite that expects native plugins.
- Which Rust OpenClaw rewrite has audit logging / replayable history?
- openclaw-rs is built around event sourcing: sessions are an append-only event log you can replay. That gives you time-travel debugging and an audit trail out of the box, which is useful for compliance-sensitive deployments.
- Are openclaw-rs and ZeroClaw affiliated with upstream OpenClaw?
- No. Both are independent Rust reimplementations of the open-source OpenClaw project (github.com/openclaw/openclaw). openclaw-rs is built by Neul Labs and is not endorsed by or affiliated with the upstream OpenClaw project or ZeroClaw.