Than the displayed 1.52GB OpenClaw reference. Against the bare Node.js baseline shown here, Operator uses over 74% less memory.
Go-native · edge-ready · MIT
The AI agent that runs on a $10 chip.
A complete personal agent runtime in one Go binary: persistent memory, model routing, skills, schedules, and messaging—without hauling a data center onto your desk.
git clone https://github.com/operatoronline/operator-os.git
Memory, not marketing
Leave the runtime overhead behind.
Operator OS idles under 10MB. That changes where an always-on agent can live—and how little hardware it takes to keep one running.
Small binary, full stack
Everything the agent needs. Nothing it doesn’t.
Bring your model. Switch without rebuilding.
Route across cloud and local providers from one configuration. Keep the runtime fixed while the intelligence layer changes.
Meet users where they are
Telegram, Discord, Slack, and WhatsApp channels are built into the gateway.
Memory that survives
Long-term memory and daily notes persist across sessions and reboots.
Skills, on disk
Add capabilities through a filesystem-based skills system you can inspect and version.
Time is a tool
Native cron scheduling turns prompts into repeatable background jobs.
Five architectures
Build once. Put intelligence anywhere.
From a Pi Zero-class board to a rack server, the same single-process design travels without a JavaScript runtime or Python environment.
- ✓x86_64desktop / server
- ✓ARM64Pi / edge
- ✓ARMv7legacy boards
- ✓RISC-Vopen silicon
- ✓LoongArch64native target
Pi Zero-class
An always-on personal agent without always-on cloud compute.
Runtime baggage
A self-contained Go binary. No Node.js or Python runtime to manage.
Gateway daemon
One process coordinates channels, sessions, tools, memory, and schedules.
Open source
Inspect it, fork it, and deploy it on hardware you control.
From clone to online
Three moves. One running agent.
Onboard the workspace
Initialize the folders and configuration Operator uses for your agent.
operator onboard
Configure your keys
Choose a model provider and connect whichever messaging channels you need.
$EDITOR ~/.operator/config.json
Start the gateway
Bring the daemon online. Your configured channels route into the agent loop.
operator gateway
Pick your launch path
Build it yourself—or hand us the keys.
Start with the exact parts and commands, or get a production-minded setup tailored to your hardware, models, and channels.
Pi-in-an-hour kit
A focused deployment kit for getting Operator OS running on inexpensive edge hardware without losing a weekend to configuration.
Get the kit →Paid deployment setup
Architecture review, hardware bring-up, provider and channel configuration, and a working handoff sized to your environment.
Book a setup →Operator OS is optimized for self-hosted, single-user deployments. Scope and final pricing are confirmed before work begins.