Turn a corpus-grounded template into a whole task graph you can trust — cycles refused, gaps labeled honest.

Every organization's situation and tool stack is unique — shaped by the work already done, the data you have, and the decisions you've already made.

The same measurement and decision tools are needed across organizations, and it is inefficient for each to stand them up alone — built once, owned in common, on your own data.

Own the tools you use

The Software Engineering chapter of the Bicycle Cooperative is forming. Join in the class that fits you, or rent the tools.

See the offer

For humans and AI

Turn a plan into a working task graph — instantly.

Pick a template derived from a real how-to guide and Kanbai creates every task in order, with dates and dependencies attached. Track it as a list, a board, or a timeline. The template catalog is open to browse — a project’s own tasks and board need sign-in.

What a project page looks like

Foundations
Discovery
Co-design

An illustration of what a template builds — browse the real catalog to see the actual task sets.

How it works

Templates build the graph

Instantiating a template creates the whole task set in one atomic write, with order, assignees, and computed dates — never a half-created project.

Dependencies can't cycle

A database trigger rejects any dependency that would create a cycle, not just a UI warning that's easy to route around.

Origins, not just checklists

Where a plan comes from — the source guide, the derivation tier — travels with it, cited in the open, not buried in a changelog.

Open catalog, gated projects

Templates, SOPs, and tools stay open to anyone with the link. A project's own tasks and board need membership — editing needs a real identity, never "signed in" alone.