This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
QuorumRouter
Fail-closed routing and safe execution for AI agents
QuorumRouter is a Open source Deno framework with two distinct multi-model paths. Best Route fans prompts out to independent model adapters, validates every response with Zod, requires quorum, and synthesizes the strongest answer. Agent Chat gives different models shared conversation context so they can challenge, revise, and converge across visible turns. Any repository mutation still requires external SafeLoop authority, exact-digest approval, watched execution, and verified artifacts.
Hey Product Hunt 👋
I built QuorumRouter because multi-model AI systems often blur two fundamentally different ideas:
1. asking several models independently and selecting the best answer;
2. letting different models actually talk, disagree, revise, and converge.
QuorumRouter keeps those paths separate.
Best Route runs model candidates in isolated contexts, validates every response, requires quorum, compares the results, and synthesizes the strongest final answer.
Agent Chat invokes two distinct working provider/model wrappers and passes bounded conversation context between them. The CLI displays every model identity, reply target, and response as it arrives—so you can see one model challenge another, cause a revision, and move toward a conclusion.
If fewer than two working model identities can be established, Agent Chat fails closed rather than pretending a single-model response is a conversation.
Here is the real CLI path:
npx --yes github:sakamoto-sann/quorum-router#main my-quorum-router
cd my-quorum-router
deno task intake
deno task models:list
RUN_EXTERNAL_MODEL_DOGFOOD=1 \
RUN_EXPERIMENTAL_AGENT_CHAT=1 \
QUORUM_ROUTER_AGENT_CHAT_MAX_TURNS=6 \
deno task agent-chat \
--prompt "Debate the safest migration plan"
I verified the live path with a four-turn conversation between:
OpenAI/codex-cli ↔️ Cognition/devin-cli
Each turn preserved model identity and replying to lineage, passed schema validation and redaction checks, and was recorded in out/agent-chat-trace.json.
When a conversation produces an action with side effects, the models still do not receive execution authority. The exact proposal goes to SafeLoop, which handles policy checks, digest-bound approval, watched execution, artifact verification, and audit receipts. If approval or verification fails, the workflow stops.
The launch videos are deterministic visualizations rather than recordings of live model API traffic. The live wrapper-backed Agent Chat command is implemented separately and available from the source-backed scaffold.
MIT-licensed open source. Commercial and production use are permitted.
I’d especially appreciate feedback on:
- whether Best Route and Agent Chat feel clearly differentiated;
- which provider combinations you want next;
- what kinds of agent actions should always fail closed;
- how you would use visible cross-model debate in your own workflow.
Thanks for checking it out—I’ll be here answering questions throughout the launch! 🚀
What happens when the models don't reach quorum — do you return an error, retry, or fall back to the strongest single answer? That edge case seems like where the fail-closed promise actually gets tested.
the "return conflicting digests for manual review instead of auto-picking a winner" choice is the right instinct - a system that quietly resolves disagreement is more dangerous than one that admits it can't decide. one thing I'd want over time: if the same adapter is consistently the one whose digest doesn't match quorum on certain task types (not randomly, but a pattern), does QuorumRouter surface that as a signal that one provider is systematically weak there, or does every disagreement look like an isolated one-off unless you're tracking it yourself?
This one is close to home, I also run multiple models against the same question in my product. The interesting case is when they genuinely disagree. Quorum works when there is a clear majority, but sometimes the minority answer turns out to be the right one. How does Best Route handle a real split, does it synthesize anyway or surface the disagreement to the caller?
How does quorum validation actually pick the strongest answer when models disagree, and is there a way to see why one response won over another?
How does the quorum threshold get set, and can I tune how strict the validation is per model adapter?
Curious how it handles costs in Best Route when multiple models get pinged per request, any built-in controls or do we wire that up ourselves?
The quorum validation with Zod is a really clever way to keep multi-model output honest, and I was surprised how cleanly the agent chat handles disagreements between models.
How does the quorum validation actually work when models disagree strongly—does it use a judge model for arbitration or just majority vote on structured outputs?
Spent a couple hours wiring QuorumRouter into a small Deno script and the Zod validation step before quorum really does catch the lazy model. The SafeLoop approval flow feels heavy at first, but seeing the exact-digest check actually block a bad edit was a nice moment.
Spent an afternoon wiring QuorumRouter into a side project and the Zod validation step before quorum approval actually caught a flaky adapter I would have shipped. Curious how the SafeLoop approval flow feels once you stack more than a few repos.
About QuorumRouter on Product Hunt
“ Fail-closed routing and safe execution for AI agents”
QuorumRouter was submitted on Product Hunt and earned 14 upvotes and 24 comments, placing #38 on the daily leaderboard. QuorumRouter is a Open source Deno framework with two distinct multi-model paths. Best Route fans prompts out to independent model adapters, validates every response with Zod, requires quorum, and synthesizes the strongest answer. Agent Chat gives different models shared conversation context so they can challenge, revise, and converge across visible turns. Any repository mutation still requires external SafeLoop authority, exact-digest approval, watched execution, and verified artifacts.
QuorumRouter was featured in Productivity (656.2k followers), Developer Tools (515.9k followers), Artificial Intelligence (473.7k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 354.4k products, making this a competitive space to launch in.
Who hunted QuorumRouter?
QuorumRouter was hunted by tetsu sakamoto. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how QuorumRouter stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
tetsu sakamoto