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
Recurring agent work needs more than a model that can complete a task. It needs a durable owner, boundaries, evidence, and a review rhythm that still works when the operator is busy. The central choice is whether to manage a coding card executed in a git worktree and reviewed as a diff or pull request or a continuous loop that watches the business and decides what to do next.
Vibe Kanban centers a board for parallel coding-agent delivery. win.sh centers a 24/7 monitoring and action loop governed by a per-work-type authority matrix. Both can produce useful agent work, but they ask the operator to shape and review it differently.
How do Vibe Kanban and win.sh compare?
| Dimension | Vibe Kanban | win.sh |
|---|---|---|
| Core abstraction | A coding card executed in a git worktree and reviewed as a diff or pull request | Continuous business monitoring and action loop |
| Human role | Kanban state, parallel runs, diff inspection, and pull-request review | Set rules, review decisions and receipts, and adjust authority by work type |
| Execution | Open-source, community-maintained coding-agent orchestration | Cloud sandboxes connected to accounts the customer owns |
| Strongest fit | Focused worktree coordination and code review for parallel agents | Low-touch operation with a compact morning review rhythm |
| Recurring work | Repetition follows the a board for parallel coding-agent delivery model | Runs continuously, with recurring workflows and a daily brief |
| Control | Kanban state, parallel runs, diff inspection, and pull-request review | Approval gates, authority matrix, budget cap, receipts, and Decisions tab |
| Main cost | Non-code operations, recurring schedules, and general approval work sit outside the product focus | The loop acts before the brief, so some control happens after execution |
| Commercial model | Check current product pricing and deployment terms | Self-serve monthly budget from $50 to $10,000, no revenue share |
Who does Vibe Kanban fit?
Vibe Kanban fits software teams whose agent work is overwhelmingly code. Focused worktree coordination and code review for parallel agents. Its operating model is easier to justify when the work naturally looks like a coding card executed in a git worktree and reviewed as a diff or pull request.
The limitation follows from the same choice. Non-code operations, recurring schedules, and general approval work sit outside the product focus. That may be irrelevant for a contained job and decisive for work that crosses departments, artifacts, or approval boundaries.
Who does win.sh fit?
win.sh fits founders who want connected business systems watched continuously. The loop proposes actions, proceeds inside standing authority, holds risky categories for approval, and compresses activity into a morning Telegram brief and Decisions tab. Approvals, edits, and rejections become rules, which lets trust grow separately for each kind of work.
The ownership model is a strength. win.sh connects to accounts the customer owns, applies a hard monthly budget cap, shows dollar-based receipts, and takes no revenue share. Its tradeoff is the default rhythm: the loop runs before someone opens the product, and review often follows execution rather than steering each step in flight.
Where does each product put human control?
Vibe Kanban puts control in kanban state, parallel runs, diff inspection, and pull-request review. That gives the operator direct leverage over its primary object. win.sh moves more control into standing policy. The authority matrix describes what may happen, approval gates stop selected risks, and the brief summarizes the resulting work.
Neither approach is universally safer. A carefully configured specialist tool can be easier to bound than a general loop. A mature authority matrix can be easier to operate than dozens of hand-built review branches. Compare the actual exception paths, not the autonomy label.
Where does Task Machine fit?
Task Machine takes a third position for operators who want agents to execute while the recurring process stays explicit. Chat sets direction, one inbox gathers approvals, questions, failed verifiers, proposals, and exceptions, and tasks preserve detailed state. Workflow graphs record branches, human gates, verifier gates, and append-only step history.
That model involves the operator more than win.sh and requires more setup than Vibe Kanban when Vibe Kanban already fits the job. It does not replace focused worktree coordination and code review for parallel agents, and it does not promise a low-touch morning-brief rhythm. It fits when work crosses humans and agents and the process must remain readable independently of who executes it.
Which should you choose?
Choose Vibe Kanban when you are software teams whose agent work is overwhelmingly code and want focused worktree coordination and code review for parallel agents. Choose win.sh when continuous monitoring, accounts you own, a hard spending cap, and a light daily review rhythm matter most. Choose Task Machine when explicit workflows, verifier-backed gates, and one inbox for every judgment call matter more than minimum operator involvement.