head to head · open source
zeroshot vs flow-next
zeroshot has 2,090 GitHub stars, 198 forks, 3 open issues and last shipped yesterday. flow-next has 716 stars, 62 forks, 6 open issues and last shipped yesterday. zeroshot leads on adoption by 192% (2,090 vs 716 stars). zeroshot is written in Rust under MIT; flow-next is written in Python under MIT. zeroshot has attracted 9% as many forks as stars, flow-next 9%. zeroshot was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 4 topic tags (agentic-workflow, claude-code, code-review, codex), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| zeroshot | flow-next | |
|---|---|---|
| GitHub stars | ★ 2.1K | ★ 716 |
| License | MIT | MIT |
| Written in | Rust | Python |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 198 | ⑂ 62 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick zeroshot if
- You weight community size — 2.1K stars and counting
- You want the MIT license terms
- Your stack matches Rust
- You value the larger contributor base for long-term maintenance
pick flow-next if
- You want the flow-next feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Python
- You evaluated both and flow-next fits your workflow better
About zeroshot
Zeroshot The agent that writes the code should not be the one that decides it works. Zeroshot turns a software goal into an explicit multi agent graph: one agent implements, independent agents review, failures go back to a bounded repair loop, and nothing is delivered until the graph's checks pass. The implementing agent never approves its own work. Use the built in graph or bring your own topology. Add reviewers, tests, and repair loops, then save the setup as a profile for the next task. Opcore works alongside it: Opcore checks each edit while an agent writes code, and Zeroshot has independent agents review…
read the full zeroshot overview →
About flow-next
Flow Next Agents generate. flow next proves. Implementation got cheap. Reviewing it, verifying it, and keeping a codebase coherent did not. Flow Next is a workflow plugin that runs inside your coding agent. Give it the change you want and the rules your project follows. It turns that intent into specs, implementation, review, and pull requests with evidence. Your specs, decisions, and task state live in your repository. A real recorded run: plan, then cross model plan review (catches a missing guard, fix, SHIP), then implement plus tests, then impl review SHIP, ending on the receipt. Nothing staged; every frame…
read the full flow-next overview →
More in Developer Tools
Related comparisons
More Version Control & Collaboration projects
Compare either of these against the rest of the Version Control & Collaboration field.
Frequently asked questions
Is zeroshot or flow-next more popular?
zeroshot has 2,090 GitHub stars and flow-next has 716. zeroshot has the larger community by that measure.
Are zeroshot and flow-next free?
Both are open source. zeroshot is licensed under MIT and flow-next under MIT. Neither carries a licence fee.
What is the difference between zeroshot and flow-next?
zeroshot is written in Rust and flow-next in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, zeroshot or flow-next?
Choose zeroshot if you want the larger community (2,090 stars) or its MIT licence terms. Choose flow-next if its feature set, stack or MIT licence fits better. Both are self-hostable.