What decides it is how complex your orchestration is, not how big the project is or how many sessions you run. The signal for Harbor is sessions in Claude Desktop, the CLI and the cloud, on several accounts, that can’t see each other and have to be coordinated, or a whole team developing in the same repo, with work that has to reach `main` as releases that land together and in order.
Sessions that don’t depend on each other’s work, on one account and one machine.
Keelokit alonedirect landing
First time with agents, or building a first MVP.
Keelokit alonedirect landing
Several development CLIs and sessions to coordinate, local and in the cloud, that can’t see each other.
Add Harborone logbook, one convoy
Work that has to reach main as releases: together, verified once and in order.
Add Harborconvoys and the harbormaster’s ok
A whole team developing in the same repo.
Add Harborone logbook everyone reads
More than one Claude account, or more than one machine, the cloud included.
Add Harborshared logbook
Each landing costs a full verify, and every push to main starts a CI run you pay for.
Add Harborone verify and one push per convoy
Several branches keep touching the same files: schema, migrations, shared types, locales.
Add Harborhotspots, one at a time
Solo, one MVP
One laptop, one story at a time, a Claude plan. Keelokit lands each story as it’s proven. Nothing to coordinate.
A couple of stories a day, a helper now and then
A small team where two sessions sometimes run in parallel. Keelokit’s own coordinate skill is enough: the sessions don’t collide.
Desktop, CLI and cloud, across two accounts
Two Claude accounts, Claude Desktop on a laptop, the CLI and a cloud container. None of the sessions can see the others. Each one ends on its own branch; nobody sees the combination until a convoy is assembled and verified once.
A migrations folder everyone touches
Several branches add migrations in the same week and CI minutes are counting. Harbor keeps them out of the same open convoy and pushes once.
Harbor builds on Keelokit, so you start there and add Harbor when orchestrating the releases gets complex.