Vibe Kanban vs win.sh: Two Operating Models
Vibe Kanban centers a board for parallel coding-agent delivery. win.sh runs a 24/7 business loop inside an authority matrix.
Founder, Task Machine
A developer running five coding agents at once needs a board that keeps their branches apart and their diffs reviewable. A founder running a store needs something that notices a failed payment at midnight. Vibe Kanban and win.sh come up in the same searches, but they solve those two different problems.
Vibe Kanban is an open-source board for parallel coding-agent work. You plan issues and sub-issues, assign coding tasks to agents, run each in its own git worktree, inspect the diffs, and track status against pull requests. The Apache 2.0 project moved to community maintenance after its company, Bloop, shut down in April 2026. win.sh runs a 24/7 loop over the business accounts you connect and acts inside an authority matrix you set.
How do Vibe Kanban and win.sh compare?
| Dimension | Vibe Kanban | win.sh |
|---|---|---|
| Core abstraction | A coding card run in a git worktree and reviewed as a diff or pull request | A 24/7 loop that monitors connected business accounts and acts |
| Human role | Plan the board, run agents in parallel, and review diffs and pull requests | Set rules per type of work, then review decisions and receipts |
| Execution | Open-source, community-maintained coding-agent board | Cloud sandboxes connected to accounts the customer owns |
| Strongest fit | Keeping parallel coding agents apart and their work reviewable | Founders who want the business watched with little daily involvement |
| Recurring work | Cards you plan and assign as development work comes up | Runs continuously, with recurring workflows and a morning brief |
| Control | Board state, worktree isolation, diff inspection, and pull-request review | Approval gates, authority levels, a hard budget cap, and receipts |
| Main cost | Non-code operations, schedules, and general approvals sit outside its focus | The loop acts before the brief, so much of the review happens afterwards |
| Commercial model | Free and open source under Apache 2.0 | Self-serve monthly budget from $50 to $10,000, no revenue share |
Prices and features were checked against each vendor's own pages on 6 October 2026.
Who does Vibe Kanban fit?
Vibe Kanban fits developers whose agent work is almost all code. Each card gets its own worktree, so three agents can change the same repository without colliding, and every result comes back as a diff you read before merging. Because it is free and open source, a team can adopt it without a purchase decision.
Its scope is the coding job. Recurring schedules, customer-facing work, and approvals outside a pull request sit beyond what the board was built for, and since April 2026 its future depends on community maintainers.
Who does win.sh fit?
win.sh fits founders who need the business watched more than the codebase. It monitors accounts such as Stripe and Plausible, with GitHub listed as coming soon, around the clock, proposes or takes the next step, and reports each morning through a Telegram brief and the Decisions tab.
Trust grows per type of work as approvals, edits, and rejections become rules, and spending, outreach, publishing, and sensitive changes wait at approval gates. Its budget has a hard monthly ceiling and no revenue share. Its center is the business loop rather than code review, and much of its work is reviewed after it runs.
Where does each product put human control?
Vibe Kanban puts control in the developer's review. Nothing lands until someone reads the diff and merges the pull request, a gate developers already trust, though it only covers code.
win.sh puts control in standing policy for the whole business, and its authority matrix covers support replies, spending, and publishing as well as anything touching code. If your agents both write code and send customer emails, ask where each product would stop a mistake in the email, since a diff review would never see it.
Where does Task Machine fit?
Task Machine covers the work on both sides. Coding agents can open pull requests from tasks, and the same Inbox holds approvals for customer replies, reports, and spending, with each recurring job running as an explicit workflow with approval, question, and verifier steps. Tasks track each job, whether it ends in a merged pull request or a sent reply.
Task Machine fits a small company where code is one kind of recurring work among several. Vibe Kanban stays the more focused tool for parallel worktrees and diff review, and using both makes sense when it remains your coding surface.
Which should you choose?
Choose Vibe Kanban if your agents mostly write code and you want worktree isolation and diff review for free. Choose win.sh if your business accounts, more than your repositories, need watching around the clock. Choose Task Machine if your recurring work spans code and operations and you want every approval in one Inbox.