← Back to research
·9 min read·opensource

NullClaw

NullClaw is the smallest fully autonomous AI assistant infrastructure — a 678 KB Zig binary that runs on $5 hardware with ~1 MB RAM. Now at ~7.7K GitHub stars with 50+ providers and 19 channels as of June 2026.

Key takeaways

  • 678 KB binary, ~1 MB RAM, <2 ms startup — the smallest in the OpenClaw family
  • Strong momentum: ~7.7K GitHub stars and ~900 forks as of June 2026, up from ~1.4K in February
  • Written in Zig for zero runtime overhead and cross-compilation to any architecture
  • 5,300+ tests, 50+ providers, 19 channels, MCP and subagent support, full OpenClaw config compatibility
  • Security-first: Landlock/Firejail/Bubblewrap sandboxing, ChaCha20-Poly1305 encrypted secrets

FAQ

How does NullClaw compare to ZeroClaw?

NullClaw (Zig) is smaller than ZeroClaw (Rust) — 678 KB vs ~8.8 MB binary, ~1 MB vs ~5 MB RAM. Both target extreme efficiency but NullClaw wins on size.

What hardware can run NullClaw?

Any $5 ARM, RISC-V, or x86 board. The 678 KB static binary with ~1 MB RAM requirement runs on Raspberry Pi Zero and similar minimal hardware.

Is NullClaw compatible with OpenClaw?

Yes. NullClaw uses the same config structure as OpenClaw (snake_case JSON) and includes a migration command to import OpenClaw memory.

Executive Summary

NullClaw is the smallest fully autonomous AI assistant infrastructure in the OpenClaw ecosystem — a 678 KB static Zig binary that boots in under 2 milliseconds and runs on hardware costing as little as $5.[1] Where ZeroClaw (Rust) optimizes for security and PicoClaw (Go) for simplicity, NullClaw pushes the efficiency envelope to its absolute limit using the Zig programming language. The project has serious momentum: as of June 2026 it sits at roughly 7,700 GitHub stars and 900 forks (up from ~1.4K stars in February), with daily commits, monthly tagged releases (latest v2026.5.29), and a growing "Null ecosystem" of companion tools — nullhub (management UI), nullboiler (workflow orchestration), and nullwatch (observability).[1]

AttributeValue
LanguageZig
LicenseMIT
Binary Size678 KB
Min RAM~1 MB
Startup Time<2 ms (Apple Silicon)
Test Count5,300+
GitHub Stars~7.7K (June 2026)

Product Overview

NullClaw takes a fundamentally different approach to AI agent runtimes.[2][3] Instead of building on interpreted languages like TypeScript (OpenClaw) or Python (NanoBot), it compiles directly to machine code with zero runtime overhead. The result is an agent that can run hundreds of instances concurrently on standard hardware without exhausting system resources.

Key Capabilities

CapabilityDescription
Ultra-Lightweight678 KB binary, ~1 MB peak RAM — smallest in the OpenClaw family
Instant Startup<2 ms cold start on Apple Silicon, <8 ms on 0.8 GHz edge hardware
50+ ProvidersOpenRouter, Anthropic, OpenAI, Ollama, Groq, DeepSeek, xAI, and more
19 ChannelsTelegram, Discord, Slack, iMessage, WhatsApp, Matrix, IRC, and more
Full Agent Stack35+ tools, 10 memory engines, MCP, subagents, streaming, and voice support
Pluggable EverythingVtable interfaces for providers, channels, memory, tools, sandboxes
OpenClaw CompatibleSame config structure, includes migration command; Homebrew install (brew install nullclaw)

Benchmark Comparison

PlatformLanguageRAMStartup (0.8 GHz)BinaryTestsHardware Cost
OpenClawTypeScript>1 GB>500 s~28 MB$599 Mac
NanoBotPython>100 MB>30 sN/A~$50 SBC
PicoClawGo<10 MB<1 s~8 MB$10 board
ZeroClawRust<5 MB<10 ms~8.8 MB1,017$10 any
NullClawZig~1 MB<8 ms678 KB5,300+$5 any

Figures are from NullClaw's own benchmark (macOS arm64, Feb 2026, normalized for 0.8 GHz edge hardware) — treat them as vendor-reported.[1]


Technical Architecture

NullClaw is built entirely in Zig, a systems programming language that offers strict safety guarantees and explicit memory management without garbage collection or runtime overhead.[4]

Why Zig?

  • Zero Runtime Overhead — No interpreter, no VM, no GC. The OS executes the binary directly.
  • Cross-Compilation — Single command to compile for Windows, macOS, Linux, ARM, RISC-V, embedded systems.
  • C Interop — Straightforward integration with C libraries when needed.
  • Explicit Memory — Complete control over every byte allocated.

Subsystem Architecture

Every subsystem is a vtable interface — swap implementations with a config change:[5]

SubsystemInterfaceShips With
AI ModelsProvider22+ providers (OpenRouter, Anthropic, OpenAI, Ollama, etc.)
ChannelsChannelCLI, Telegram, Discord, Slack, iMessage, Matrix, WhatsApp, IRC, Webhook
MemoryMemorySQLite hybrid search (FTS5 + vector cosine similarity)
ToolsToolshell, file ops, memory ops, browser, screenshot, HTTP, hardware
SandboxSandboxLandlock, Firejail, Bubblewrap, Docker, auto-detect
IdentityIdentityConfigOpenClaw markdown, AIEOS v1.1 JSON
TunnelTunnelCloudflare, Tailscale, ngrok, custom
PeripheralsPeripheralSerial, Arduino, Raspberry Pi GPIO, STM32/Nucleo

Memory System

All custom, zero external dependencies:

LayerImplementation
Vector DBEmbeddings stored as BLOB in SQLite, cosine similarity search
Keyword SearchFTS5 virtual tables with BM25 scoring
Hybrid MergeConfigurable vector/keyword weights
EmbeddingsProvider vtable — OpenAI, custom URL, or noop
HygieneAutomatic archival + purge of stale memories

Strengths

  • Smallest Footprint — 678 KB binary and ~1 MB RAM make NullClaw the most resource-efficient option in the OpenClaw ecosystem, enabling deployment on $5 microcontrollers.
  • Fastest Startup — Sub-2ms cold start makes NullClaw ideal for serverless, on-demand, or transient agent deployments where instant response matters.
  • Comprehensive Testing — 5,300+ tests provide confidence in reliability, significantly more than ZeroClaw's 1,017.[1]
  • OpenClaw Compatibility — Same config format and migration tooling means existing OpenClaw users can switch with minimal friction.
  • Hardware Peripheral Support — Native interfaces for Serial, Arduino, Raspberry Pi GPIO, and STM32 enable IoT and embedded use cases.

Cautions

  • Zig Ecosystem Maturity — Zig is less mature than Rust, with a smaller community and fewer libraries. This may limit extensibility for niche use cases.
  • AI-Generated Code Velocity — Much of the codebase is written with AI assistance at extreme pace; one observer noted the repo owner "averaging 70+ commits per day."[6] That velocity cuts both ways: rapid features, but review depth is hard to verify.
  • Smaller Community — Compared to OpenClaw's massive community, NullClaw's contributor base is smaller, potentially affecting long-term maintenance.
  • Less Documented — The standalone docs site (nullclaw.github.io) has gone dark; documentation now lives in the repo's docs/en tree, requiring more source-code diving for advanced customization.[7]
  • No GUI in Core — NullClaw itself is CLI-first; the companion nullhub project (beta) adds a management UI but is a separate install.[1]

What Developers Say

Community sentiment on Hacker News skews positive on footprint, with honest reservations about maturity:

  • "I ended up installing Nullclaw which is simpler but much more lightweight," wrote jpfaraco, comparing it to OpenClaw on a Raspberry Pi 4.[8]
  • "I've switched to nullclaw instead. Mostly because Zig seems very interesting so if I have to debug any issues with Nullclaw at least I'll be learning something new :)" — LaurensBER.[9]
  • The same user later tempered that enthusiasm while hunting for Kubernetes-friendly options: "I tried Zeroclaw and Nullclaw but they're bad in their own way." — LaurensBER.[10]

A popular Show HN ("I put an AI agent on a $7/month VPS with IRC as its transport layer," 340 points) ran on NullClaw, which is the most visible real-world deployment discussion to date.


Pricing & Licensing

TierPriceIncludes
Open SourceFreeFull functionality, MIT license

Licensing model: MIT — permissive open source, commercial use allowed.

Hidden costs: None. Bring your own API keys for LLM providers.


Competitive Positioning

Direct Competitors

CompetitorDifferentiation
ZeroClawNullClaw is smaller (678 KB vs ~8.8 MB) and faster startup (<8 ms vs <10 ms on edge hardware)
PicoClawNullClaw uses Zig vs Go, achieving smaller binary and lower RAM
OpenClawNullClaw trades features for efficiency — 1000x less RAM, 250x faster startup

When to Choose NullClaw

  • Choose NullClaw when: You need the absolute smallest footprint, sub-$10 hardware, or serverless deployment.
  • Choose ZeroClaw when: Security is paramount (stronger WASM sandbox story).
  • Choose PicoClaw when: Go ecosystem familiarity matters.
  • Choose OpenClaw when: You need maximum features and don't care about resources.

Ideal Customer Profile

Best fit:

  • Embedded systems developers deploying AI on microcontrollers
  • IoT/edge computing scenarios with strict resource constraints
  • Developers running many concurrent agent instances
  • Serverless deployments requiring instant cold starts

Poor fit:

  • Users wanting GUI/desktop experience
  • Those needing extensive plugin ecosystem
  • Teams unfamiliar with systems programming concepts

Viability Assessment

FactorAssessment
Financial HealthCommunity-driven (no company; funding not publicly disclosed)
Market PositionStrongest of the minimalist OpenClaw forks — ~7.7K stars
Innovation PaceVery active — daily commits, monthly releases plus nightlies
Community/EcosystemGrowing fast: ~900 forks, Discord, and companion projects (nullhub, nullboiler, nullwatch)
Long-term OutlookPositive for embedded/edge use cases

NullClaw is decisively alive as of June 2026: stars grew roughly 5x since this profile's original February snapshot (~1.4K to ~7.7K), the repo was pushed to the day before this update, and tagged releases ship roughly monthly (v2026.4.7, v2026.4.9, v2026.4.17, v2026.5.4, v2026.5.29).[1] In a fast-churn ecosystem where tiny agent projects die in weeks, that consistency is the strongest signal in its favor. The main residual risk is bus factor: development pace is dominated by a single maintainer working at AI-assisted speed.[6]


Bottom Line

NullClaw is the ultimate expression of "less is more" in the AI agent space, and unlike most minimalist OpenClaw forks it has survived and compounded — ~7.7K stars, monthly releases, and an expanding companion-tool ecosystem as of June 2026. If you're deploying on hardware that costs less than a fancy coffee, need hundreds of concurrent agents, or require near-instant startup, NullClaw is unmatched.

Recommended for: Embedded developers, IoT deployments, serverless architectures, resource-constrained environments.

Not recommended for: Users wanting batteries-included experience, extensive documentation, or GUI interfaces.

Outlook: As AI moves to the edge, NullClaw's efficiency-first approach positions it well for embedded and IoT growth.


Research by Ry Walker Research • methodology