Index / NullClaw · updated Oct 2, 2026
NullClaw
nullclaw/nullclaw · healthy · rank 13 of 43 by stars
A 678 KB static Zig binary that delivers a fully autonomous AI assistant stack with ~1 MB RAM and sub-2ms boot. It positions itself as the ultra-minimal, security-hardened, runs-on-anything alternative to heavier agent frameworks.
Facts
Repository
Runtime
Posture
Community
Security breakdown
Composite 88 / 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 · 51 files examined
5 providers · runs locally · gateway support
Pinned models
glm-4.7 released 2025-12-22 — 9 months old (from the public model catalogue)
Pin last edited 5 days ago
Several defaults are pinned; the project picks one per provider rather than shipping a single default.
Evidence
Decision
Why choose NullClaw over OpenClaw?
Why choose this
- Dramatically smaller footprint: 678 KB binary and ~1 MB RAM vs much heavier stacks
- Sub-2ms startup enables true edge and microcontroller deployment
- Single static binary with no runtime, VM, or framework dependencies
Tradeoffs
- Smaller community and ecosystem maturity compared to OpenClaw
- UI layer (nullhub) is still in beta; OpenClaw has a full Control UI dashboard
- Zig codebase has a smaller contributor pool than mainstream-language projects
Best fit
- Running agents on $5 SBCs and constrained edge hardware
- Users who want a single static binary with zero runtime deps
- Security-conscious self-hosters wanting layered sandboxing
Avoid if
- You want a polished UI out of the box (nullhub is still beta)
- You prefer mature ecosystems with large plugin marketplaces
- You are uncomfortable with a younger, fast-moving codebase
Strong evidence from the README and active commit history for performance and security claims, though benchmark numbers are self-reported. Community sentiment evidence is thin (1 Reddit match), so sentiment and ecosystem-maturity scores carry moderate uncertainty.
AI layer reviewed Sep 21, 2026 · how this is written
Star activity
8,103 stars today
Overview
NullClaw is a fully autonomous AI assistant infrastructure written entirely in Zig, shipping as a 678 KB static binary with ~1 MB peak RSS and sub-2ms startup on modern hardware. It requires nothing but libc, runs across ARM, x86, and RISC-V, and targets everything from $5 single-board computers to desktop machines. Despite its size, it claims a feature-complete stack: 50+ providers, 19 channels, 35+ tools, 10 memory engines, MCP support, subagents, streaming, voice, tunnels, and hardware peripherals.
Architecturally, NullClaw is built around vtable interfaces, making providers, channels, tools, memory, tunnels, and peripherals fully swappable. Security is a core design pillar: pairing-based auth, multi-layer sandboxing via landlock, firejail, bubblewrap, and Docker, explicit allowlists, workspace scoping, and encrypted secrets. Recent commits show active hardening work — suppressing stderr leaks from agent runners, binding gateway ports before allocation to avoid races, and validating config to prevent typo-driven message drops — alongside 5,300+ tests and CI/nightly pipelines.
Compared to OpenClaw, NullClaw trades ecosystem maturity and a polished Control UI for extreme minimalism and portability. Its companion project nullhub (in beta) aims to close the UI gap with setup, orchestration (nullboiler), observability (nullwatch), and task tracking (nulltickets). For users who want an agent that boots in milliseconds on the cheapest hardware available, NullClaw is arguably the most resource-efficient option in the OpenClaw-alternative landscape.