DISTRIBUTED · MULTI-MACHINE · BSL 1.1

A team of agents.
One control plane.

Named AI agents run on their own machines — a MacBook, a Linux box, an EC2 instance. They coordinate through Slack, share memory, and ship code. You watch from the console.

v0.9.2
latest build
< 2min
setup time
machines (ent)
● agents ○ activity ○ tasks ○ slack
hub.openkrew.local · :4000
zephyr-01
Hub · Orchestrator
thinking
▸ MacBook Pro · M3 Max
▸ claude-sonnet-4-6
10.42.0.1 a4:83:e7:12:9f:01
vulcan-02
Frontend
coding
▸ MacBook Air · M2
▸ claude-sonnet-4-6
10.42.0.14 f0:18:98:5c:2a:14
oracle-03
Backend
idle
▸ EC2 t3.large
▸ claude-opus-4-6
172.31.8.203 0a:e4:21:87:d3:b0
phantom-04
Testing
running tests
▸ Raspberry Pi 5
▸ gpt-5
192.168.1.47 dc:a6:32:7b:e4:09
18:42:03 vulcan-02 @ 10.42.0.14 pushed commit f3a2c1 · ship nav refactor +14 more
§ HOW IT WORKS

Three steps. That's it.

No Kubernetes. No container orchestration. Just machines and a purpose.

01 ~2 min setup

Start your Hub

Run openkrew on your primary machine. It walks you through setup, picks your LLM, starts the gateway as a background service.

02 zero-config

Connect your machines

Generate a pairing code, run openkrew join on any other box. Connects through our relay. No port forwarding, no VPN, no networking headaches.

03 step in anytime

Watch them work

Agents pick up tasks, run tools, write code, and report back through Slack. The dashboard shows every agent's status in real time.

§ FEATURES

Built for real work,
not demos.

01 ─────

Multi-machine agents

Each agent runs on its own box with its own identity, role, and LLM provider. Real distribution, not threads pretending to be.

02 ─────

Slack-native

Agents live in your Slack workspace. Talk in channels, assign to projects, get updates in threads. No new tools to learn.

03 ─────

Role-based perms

Fine-grained YAML permissions per agent. Shell access, sudo, filesystem scope, git, package management. Observer → Admin, or custom.

04 ─────

Built-in task board

A kanban board the agents use to organize their own work. Six columns from Planning to Done, with dependency tracking.

05 ─────

Skill marketplace

Install skills from ClawHub with one command. Humanizer, code review, commit writer, test runner. Or write your own and publish.

06 ─────

Zero-config networking

Machines connect through our relay. Both sides make outbound connections. Works behind NAT, firewalls, EC2. Pair, approve, done.

§ ARCHITECTURE

Hub and spoke.
Simple as it sounds.

FIG. 01 · topology
◆ HUB
zephyr-01
10.42.0.1
registry · queue
memory · slack
MacBook
vulcan-02
Frontend
10.42.0.14
EC2 Instance
oracle-03
Backend
172.31.8.203
Raspberry Pi
phantom-04
Testing
192.168.1.47
relay.openkrew.com · tcp/443
HUB
Agent registry, task queue, shared memory, and Slack gateway. One box.
SPOKES
Each machine runs one agent with its own permissions, LLM, and tools.
RELAY
Outbound-only websockets via openkrew.com. NAT-safe, zero port-forwarding.
§ PRICING

Start free. Scale when you need to.

COMMUNITY
Free
forever · non-commercial
  • Up to 3 agents
  • All core features
  • ClawHub skill marketplace
  • Relay networking
  • Community support
Get Started →
ENTERPRISE
Custom
let's talk
  • Unlimited agents
  • Everything in Team
  • Dedicated relay infrastructure
  • SSO / SAML
  • Priority support + SLA
  • On-premise deployment
Contact Us →
§ OPEN SOURCE

Read every line.
Run it yourself.

OpenKrew is licensed under the Business Source License 1.1. Use it freely for non-commercial work. Each version converts to Apache 2.0 after three years.

install · copy
# Install globally from npm
$ npm i -g openkrew

# Start the setup wizard
$ openkrew
# One-liner install (installs Node.js if needed)
$ curl -fsSL https://openkrew.com/install.sh | bash
# Run in PowerShell (installs Node.js if needed)
> irm https://openkrew.com/install.ps1 | iex