Is zeptoclaw free to use?

zeptoclaw is open source under the Apache-2.0 licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does zeptoclaw do?

Fast, small, secure, local-first personal AI assistant infrastructure: one Rust binary for tools, memory, channels, providers, and sandboxed autonomy.

What is zeptoclaw written in?

zeptoclaw is primarily written in Rust. Its source is publicly available at https://github.com/qhkm/zeptoclaw, and it has 653 GitHub stars.

zeptoclaw: Open Source AI Interaction & Interfaces

zeptoclaw is a free, open source ai interaction & interfaces project written in Rust and released under Apache-2.0. It has 653 GitHub stars, 98 forks and 54 open issues, and was last pushed 2 hours ago. On this registry it ranks #105 of 113 tracked projects in AI Interaction & Interfaces, with 5 head-to-head comparisons available.

ZeptoClaw

Fast, small, secure, and local-first personal AI assistant infrastructure.

$ zeptoclaw agent --stream -m "Analyze our API for security issues"

🤖 ZeptoClaw — Streaming analysis...

  [web_fetch]        Fetching API docs...
  [shell]            Running integration tests...
  [longterm_memory]  Storing findings...

→ Found 12 endpoints, 3 missing auth headers, 1 open redirect
→ Saved findings to long-term memory under "api-audit"

✓ Analysis complete in 4.2s

ZeptoClaw is one Rust binary for running personal AI agents locally, at the edge, or on a VPS — with tools, memory, channels, providers, and sandboxed autonomy built in. We studied the best AI assistants — and their tradeoffs: OpenClaw's integrations without the large TypeScript app footprint, NanoClaw's container-isolated simplicity without narrowing to a tiny assistant core, NemoClaw's OpenShell guardrails without the Docker/k3s footprint, and PicoClaw's edge efficiency with Rust's safety and runtime controls.

Why ZeptoClaw

We studied what works — and what doesn't.

OpenClaw proved a personal AI assistant can grow into a broad integration and skills ecosystem. NanoClaw proved container isolation can be simple enough to understand and customize. NemoClaw proved managed guardrails matter — policy-gated sandboxes, routed inference, credential injection, channel messaging, and digest-verified blueprints. PicoClaw proved edge assistants can run on $10 hardware with a Go binary under 10MB of RAM.

ZeptoClaw took notes. The integrations, the security, the governance, the size discipline — without the tradeoffs each one made. One 6MB Rust binary that starts in 50ms, uses 6MB of RAM, and ships with container isolation, prompt injection detection, and a circuit breaker provider stack.

	OpenClaw	NemoClaw	NanoClaw	PicoClaw	ZeptoClaw
Core shape	Broad TypeScript assistant + skills ecosystem	OpenClaw managed through OpenShell	Small TypeScript Claude assistant	Go edge assistant	Single Rust binary
Footprint focus	Integration breadth	Docker/k3s guardrails, ~2.4GB sandbox image	~500-line core

Any VPS

curl -fsSL https://zeptoclaw.com/setup.sh | bash

Installs the binary and prints next steps. Run zeptoclaw onboard to configure providers and channels.

Providers

ZeptoClaw supports 18 LLM providers. All OpenAI-compatible endpoints work out of the box.

Provider	Config key	Setup
Anthropic	`anthropic`	`api_key`
OpenAI	`openai`	`api_key`
OpenRouter	`openrouter`	`api_key`