How CONSYRIUM AI works β from your question to a reasoned decision
Example scenario β illustration, not live data.
01CONSYRIUM AI
Debate. Decide. Deliver.Debate.Decide.Deliver.
Claude, OpenAI, Gemini, Grok, DeepSeek, Kimi and other AI models think independently, challenge each other and reach a documented verdict with evidence. You approve β and take the decision where you work: as a report, in your tools or, with a connected GitHub repository, as a reviewed pull request.
Create a project and describe the decision. Choose the models and up to twelve perspectives. You connect your own provider keys and set a hard token budget β CONSYRIUM AI sells no AI credits.
EXAMPLEQuestion: βWhich database architecture should our SaaS product use?β β three models, twelve perspectives, a budget on your own keys.
Project, question and context
Models and perspectives you pick
Your own API keys, your budget
03PHASE 1
Independent Thinking
Every model receives the identical brief and works on its own. Answers stay sealed until all are in β no model can see or copy another.
EXAMPLEModel A drafts a managed multi-tenant database, B a self-hosted cluster, C a hybrid β none of them sees the others.
04PHASE 2
Open Council
All proposals are revealed at once and laid out side by side as equals. You compare the alternatives while the models ask each other precise questions.
EXAMPLESide by side: A is fastest to launch, B gives the most control, C balances both. B asks A how tenants are kept apart.
05PHASE 3
12 Minds Council
Roles such as architecture, security, cost and critic unfold around the models and test every proposal. Twelve perspectives are roles β not twelve extra models or votes.
EXAMPLEThe security role checks tenant isolation, the cost role compares running costs, the critic looks for weak spots.
06PHASE 4
Minority Review
A substantiated objection is highlighted and checked against evidence by independent models. Dissent is recorded β never smoothed away.
EXAMPLEOne objection stands out: in A, a misconfiguration could let tenants see each otherβs data. Evidence: test results and provider docs.
07PHASE 5
Consensus Round
Authors revise their proposals against the objections; compatible ideas can merge into a hybrid option. Differences that remain stay documented.
EXAMPLEA adds per-tenant keys and merges with C into βHybrid A + Cβ. Bβs cost concern stays documented.
08PHASE 6
Final Verdict
Recommendation, independent scores, evidence and the minority position come together in one decision report. Nothing is built at this point.
EXAMPLERecommendation: Hybrid A + C β with scores for security, cost and time to launch, and the security objection on record.
09HUMAN APPROVAL
You decide
Approve, choose an alternative, ask for more debate, request changes or reject. A proposal with an open critical security objection cannot be approved. Without your approval nothing is built.
EXAMPLEYou approve Hybrid A + C β or ask for one more round on cost first.
10PHASE 7 Β· OPTIONAL, WITH GITHUB
Execution Council
Only if you want it and a GitHub repository is connected: after your approval the decision becomes tasks, code, tests and independent reviews β delivered as a draft pull request. Most decisions need no build; merge and deployment stay your separate decisions.
EXAMPLETasks: schema, per-tenant keys, migration tests β opened as a draft pull request in your repository.
11FROM QUESTION TO DECISION
From your question to a reasoned decision β delivered where you work, optionally all the way to reviewed code.
Your keys, your providers, your approval. Every step leaves evidence you can follow.
Seven canonical stages. Modes β Independent Expert, Adversarial Review, Consensus β change how the council is orchestrated, not just the wording.
STAGE 1
Independent Thinking
Every model receives the identical brief and answers blind. No model sees another proposal before the reveal.
STAGE 2
Open Council
All proposals are revealed side by side. Models ask each other precise questions and answer them.
STAGE 3
12 Minds Council
Up to twelve perspectives β architecture, security, cost, critic and more β review every proposal.
STAGE 4
Minority Review
Dissent is first-class. Substantiated objections are checked by independent models and may stay unresolved.
STAGE 5
Consensus Round
Authors revise their proposals against the objections. Agreements and open disagreements are documented.
STAGE 6
Final Verdict
Independent scores, hard gates and a separate majority vote produce a reproducible verdict β then you decide.
STAGE 7
Execution Council
Optional, with a connected GitHub repository: after your approval a task plan, sandboxed code, tests, reviews and a draft pull request.
HUMAN GATE
Approve, select an alternative, request more debate, request changes or reject. Proposals with a critical security objection cannot be approved.
Why CONSYRIUM AI?
Several AI models develop solutions, challenge each other and score them. You see the reasoning, open objections and results before you decide.
Different perspectives
Up to six AI models work on the same decision.
Independent review
Models challenge each other's proposals.
Clear requirements
Solutions are measured against your confirmed hard requirements.
Traceable results
Scores, reasoning and unresolved objections side by side.
You decide
Final approval always stays with you.
Your keys. Your providers.
CONSYRIUM AI is bring-your-own-key only. You connect your own API keys and pay the providers directly β CONSYRIUM AI sells no AI credits and has no fallback key.
β’ Keys are encrypted with AES-256-GCM before they are stored and are never shown again.
β’ Each key is checked against the provider; model lists come live from the provider.
β’ Every session has a hard token budget that is enforced on the server.
Most teams need the reasoned decision, not code. Take the verdict as a report or into your tools β a pull request is one option, only with a connected repository.
AVAILABLE
Decision report
Recommendation, scores, dissent and evidence in the app
AVAILABLE
Markdown & JSON
Export for your notes, wiki or own tools
AVAILABLE
PDF & Word
Print-ready report to share or file
AVAILABLE
E-mail
Summary with the report attached
AVAILABLE
Telegram
Short verdict and link to your chat
AVAILABLE
Confluence
A page in your team space
PLANNED
Obsidian
The report as a note in your vault
WITH A CONNECTED REPOSITORY
GitHub pull request
Optional build by the Execution Council β reviewed, tested, as a draft
CONSYRIUM AI where you work
You don't have to open the web app for every question. With Pro you start decisions from your development tool or your private Telegram chat.
MCP SERVER
In your development workflow
The built-in MCP server connects CONSYRIUM AI to Claude Code, Claude Desktop, Cursor and VS Code.
β’ Send a question to the council with ask_consyrion, fetch the verdict with get_decision.
β’ Access with API tokens, read-only tokens included.
β’ Approvals, builds, deleting, keys and billing are never possible over MCP.
TELEGRAM
Straight from your chat
Your own bot takes questions and sends the verdict back.
β’ Ask with /frage β lines starting with "- " become hard requirements.
β’ Check models and budget, then confirm with "Start".
β’ Verdict and PDF arrive in your private chat; /offen shows what is waiting.
Optional: from verdict to pull request
With a connected GitHub repository the Execution Council can build an approved decision β reviewed, tested and always as a draft for you to merge.
01
Approve
A human approves the verdict. Nothing is built before that.
02
Plan
The Execution Council turns the verdict into a validated task graph.
03
Code & test
Code only runs isolated β in a sandbox without network access or in your repository's GitHub Actions.
04
Review
Independent models review the change; findings stay visible.
05
Pull request
A draft pull request opens in your repository through the GitHub App.
Open source. Run it on your own server.
CONSYRIUM AI is free, open-source software. Download the source code from GitHub and run it yourself with Docker Compose.