Index / IronClaw · updated Aug 17, 2026
IronClaw
nearai/ironclaw · healthy · rank 12 of 43 by stars
A Rust rewrite of OpenClaw engineered for hardcore security with WASM sandboxing and capability-based permissions. The 'Reborn' runtime migration is active, showing a privacy-first agent OS with a passionate NEAR-aligned community.
Facts
Repository
Runtime
Posture
Community
Security breakdown
Composite 90 / 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 · 142 files examined
7 providers · runs locally · gateway support
Pinned models
gemini-2.5-flash released 2025-06-17 — 14 months old (from the public model catalogue)
Pin last edited 2 days ago
Several defaults are pinned; the project picks one per provider rather than shipping a single default.
Evidence
Decision
Why choose IronClaw over OpenClaw?
Why choose this
- Rust memory safety with WASM sandbox isolation
- Capability-based permissions mitigate prompt injection
- Privacy-first local execution, no mandatory cloud telemetry
Tradeoffs
- Smaller skill/plugin ecosystem than OpenClaw's ClawHub
- Requires Rust toolchain build, less beginner-friendly
- Reborn branch migration may cause transitional instability
Best fit
- Privacy-focused users wanting a local AI assistant
- Rust developers needing extensible agent framework
- Web3/NEAR ecosystem automation tasks
Avoid if
- Want zero-build plug-and-play setup
- Need massive mature plugin registry like ClawHub
- Non-technical users uncomfortable with CLI and cargo
Strong evidence from README, commits, and search indicates active secure development; uncertainty remains on multi-user support and exact telemetry defaults.
AI layer reviewed Aug 2, 2026 · how this is written
Star activity
12,604 stars today
Overview
IronClaw is an Agent OS written in Rust by NEAR AI, positioned as a security-hardened alternative to OpenClaw. Its architecture emphasizes privacy and extensibility through WASM sandbox isolation, capability-based permission models, and prompt-injection defenses, as noted in external summaries. The project is undergoing a significant transition with the 'Reborn' standalone runtime (on the reborn-integration branch) that introduces a separate ironclaw-reborn binary, isolated state roots, and CLI-native model route configuration.
Recent commit activity shows heavy investment in test coverage, CI stability, and migration of core commands (doctor, status, config) to the Reborn framework, indicating a healthy, fast-moving codebase. Features include multi-provider LLM routing (OpenAI, local near.ai endpoints), Slack/Telegram integrations, and a skill/extension system. Compared to OpenClaw, IronClaw trades a larger plug-and-play ecosystem for stronger isolation guarantees and a memory-safe Rust foundation, targeting users who prioritize local-first operation and adversarial robustness.