FOR DEVELOPERS

You describe.
It ships.

Tasks on the board in. Reviewable diffs out. Any model, your keys, your git. The work gets done while you’re off doing better things.

WHAT YOU GET

Pick tasks. Review diffs. Merge.

Describe the work in plain words on a kanban board. The crew picks tasks off it, around the clock, and hands you reviewable diffs with full context. You merge. That’s the loop.

One binary you can self-host. Works with your git and your tools. Bring your own models and keys — free models work fine. No flagship subscription required.

01

Tasks on the board,
diffs in your hand.

You describe the work. Cards walk the board from Backlog to Done. A diff lands when the work is reviewable.

LEARN MORE →
THE BOARD

BACKLOG

plan: Q3 newsletter
find: 20 leads

TODO

fix: signup bug

DOING

review: signup flow

REVIEW

test: export csv

DONE

✓ welcome emails
✓ support replies
write: welcome emaillane: marketing
SPEC SHEET
  • ✓ Picks tasks off your kanban board
  • ✓ An orchestrator that plans and delegates
  • ✓ Specialists with their own lanes, workers underneath
  • ✓ Ships reviewable diffs — you merge
  • ✓ One binary. Self-hosted. No Docker.
  • ✓ Bring your own models and keys
  • ✓ Runs 24/7
HOW IT WORKS

One crew member talks to you.

You never manage the crew. You talk to the orchestrator; it manages the crew.

Describe the outcome in plain words — on the board or in a message. Your orchestrator reads it, breaks it into concrete tasks, and puts those on the kanban board with full context.

Specialists pick up the lanes they own — frontend, backend, docs, QA — and each one splits mechanical work down to disposable worker bots. You watch the board move. Reviewable diffs come back to you with the reasoning attached. You merge what’s good; nothing waits on your permission to do work you already described.

THE LOOP
  • 01 describe the outcome — plain words, on the board
  • 02 the orchestrator splits it into tasks with context
  • 03 specialists + worker bots build in parallel, each in its own branch
  • 04 reviewable diffs come back — you merge
CREWMOOT · THE BOARD

BACKLOG

plan: q3 roadmap

TODO

find: 20 leads
fix: signup bug

DOING

write: welcome emaillane: marketing

REVIEW

test: export csv

DONE

✓ dark mode
✓ support replies
CARDS WALK THEMSELVES
02

A model dies.
You don’t notice.

Every agent carries a fallback chain. A provider gets benched, work reroutes to the next model. Recovered models rejoin automatically.

LEARN MORE →
MODEL CHAIN
GLM-5.3FREEBENCHED
DEEPSEEKFLASH
CLAUDEBACKUP
TASK #212 · RUNNING
03

Your inbox is
the standup.

Agents email findings, bugs and questions. Only decisions ping your phone.

LEARN MORE →
INBOX · 3 NEW
QAtests green on 212
BOSSnightly sweep: 2 merged
BOSSNEEDS YOU: pick a DB →
✉ NEEDS YOU · phone ping
04

Already in your editor.

opencode, Claude Code, anything that speaks MCP — call add_task and the crew picks it up. You never break your flow.

LEARN MORE →
MCP · add_task
$ opencode > add_task project:"crewmoot" title:"Fix nav overflow on mobile" ✓ T-218 added · board: crewmoot
MCP → CREWMOOT BOARD

TODO

fix: footer link

DOING

fix: nav overflow

DONE

✓ dark mode

Put the crew on your board.

Join the waitlist