Odux · Council

Ask a council, not a chatbot.
Get a conclusion you can trust.

One AI gives you an answer. Odux Council seats several around the same question: they argue it out, check each other's work, and a chairman writes the conclusion. Then the same seats can build it.

Any model on any seatYour own keysRead aloud
Example Read aloud
Should a new startup build a monolith or microservices?
Claude critic

A monolith. Microservices solve a problem you don't have yet: many teams shipping on their own. Until then they only add moving parts.

Kimi long context

Most early startups die of the product, not the architecture. Whatever ships fastest wins, and that's one codebase.

DeepSeek coder

Agree, with one condition: keep clear module boundaries inside it, so splitting later is a refactor, not a rewrite.

GPT generalist

The one case for services on day one: a part with very different load, like video processing. Split that, and only that.

The chairman's conclusion

Start with a modular monolith. Split out a service only when a team or a load pattern forces it.

Different minds, one table.

Every model has its habits and blind spots. Put several of them on one question and the weak arguments fall away. You hear each one, read aloud if you like, and you keep the conclusion.

Conference

The seats debate in turns and answer each other, then the chairman concludes.

For decisions with two sides.

Advisory

Each seat answers on its own, unseen by the others, and the chairman writes one synthesis.

For a quick second, third and fourth opinion.

Peer review

Each seat answers, then ranks the others' answers without knowing whose they are.

For finding the strongest answer.

Deliberation

The seats answer, critique each other, and revise before the synthesis.

For hard questions that need a second pass.

Then let them build.

In the Code Room the same seats become a team. A developer writes each task, a senior and a co-senior from other vendors review the actual change, and a gate decides whether it may ship.

  • Cross-vendor review, so a model never signs off on its own maker's work.
  • Every word on the record: the developer's change and each review, as a transcript you can replay or hear.
  • Nothing merges on a promise. Without passing checks, the gate holds it and says why.
Try the Code Room
Code Room task 1Example
Developer DeepSeek

Add a /health endpoint that returns the version.

+@router.get("/health")
+def health():
+    return {"ok": True, "version": VERSION}
Senior Claude, approves

Small and clean. Import VERSION from app.version, or this fails at start-up.

Co-senior GPT, approves

Agreed. Add a test that calls /health and checks the version field.

Built by DeepSeekReviewed by Claude and GPTHeld at the gate until the checks pass

Your models, your keys.

You decide who sits on your council. Add the providers you use and tick the models you want. Nothing else appears on the seats.

Bring your own keys

Paste a key and check it with the provider in one click. It's stored encrypted, tied to you, and only its last four characters are ever shown again.

Any mix of models

Claude next to DeepSeek next to a model running on your own hardware through Ollama. Spread them across the seats, or put every seat on one provider.

A team, if you have one

Workspaces share keys and runs with your colleagues, with roles for who may change what. On your own, it's just you and your council.

Odux crest

Bring your hardest question.

Set up your models in a minute, seat your council, and hear what they make of it.

Create your council