🚧 Active development.APIs and features may change. Follow on GitHub →
Quorum / preview · Elastic License 2.0 · Open Source · MCP
Quorumpreview
2Get Started
cost & roi

The ROI isn't a spreadsheet.

We're not going to give you a calculator with fake multipliers. We're going to ask you four questions instead.

SECTION 01 · ask your team
no benchmark required
01
How long does it take a new engineer to make their first meaningful contribution?
If the answer is weeks or months, how much of that is finding context that already exists somewhere?
02
When a senior engineer leaves, what happens to the reasoning behind the decisions they made?
Not the decisions themselves — they're in git. The reasoning. The constraints. The rejected alternatives.
03
How often do your AI agents contradict a product requirement nobody told them about?
Claude Code doesn't know about R-022 unless you tell it every session. How often do you remember?
04
How much time do engineers spend re-litigating decisions that were already made?
"Didn't we decide this six months ago?" How often does that sentence appear in your Slack?
SECTION 02 · the compounding curve

Agent quality compounds with the knowledge graph.

The graph isn't useful from day one. It gets useful fast — and then it compounds. Teams that reach 500 nodes rarely go back to managing context by hand.

agent quality ↑
10 nodes
Claude needs lots of hand-holding
100 nodes
Rarely asks obvious questions
500 nodes
Pre-loads context automatically
2000 nodes
Agents deliver features semi-autonomously
5000+ nodes
Agents are team members

Illustrative — based on team reports, not a controlled study.

SECTION 03 · illustrative scenario

The guest checkout requirement.

A real pattern we've seen play out. The names are fictional.

WITHOUT QUORUM
@product
R-022: Guest checkout must be available for non-authenticated users. Conversion drop of 40% observed when requiring sign-up.
@dev
Refactoring auth flow. The old guest-checkout path looks unused — removing it to clean up the code.
agent
Removed 3 legacy auth routes. No tests failing. PR ready for review.
🚨 prod
Conversion dropped 38% overnight. Guest checkout is broken.
WITH QUORUM
@product
R-022 stored: Guest checkout must be available for non-authenticated users. Pinned = true. Owner: @ml-rodriguez.
agent
[session start] Pending items: R-022 guest-checkout-requirement (pinned, authority: product). Loading context...
agent
Detected: proposed refactor touches auth flow. R-022 requires guest checkout to remain available. Flagging for human review before proceeding.
@dev
Oh right — that's the 40% drop-off requirement. Revising the refactor to preserve the guest path.
↳ R-022 enforced · 0 production incidents · refactor completed safely
The difference →
The requirement existed in both scenarios. In the first, it lived in a Slack message nobody searched. In the second, it was a governed record the agent loaded at session start — automatically.
SECTION 04 · what quorum costs

$0.
No per-seat fees.
No usage tiers.

Quorum is Elastic License 2.0. You self-host it on your own infrastructure. There is no SaaS tier, no enterprise gating, no seat-based pricing.

What you do pay →
Infrastructure to run the graph server (a small VPS or Docker container) and the time to set it up. Most teams are running in under 30 minutes.
Elastic License 2.0
Commercial use and modification permitted. Cannot offer as a managed/hosted service to third parties.
Self-hosted
Your knowledge graph never leaves your infrastructure. No vendor lock-in.
No per-seat pricing
Add the whole engineering org. Add contractors. No counting heads.
No usage caps
No token limits on the knowledge graph. Write as much as you need.
No feature tiers
All constitutional rules, all features, all integrations — in the free version.
SECTION 05 · still evaluating?

That's reasonable. Here's what we suggest.

Don't evaluate Quorum against a blank canvas. Pick one real decision your team made in the last month. Try to find the reasoning behind it. If you can't find it in under 60 seconds — that's the problem Quorum solves.

01
Pick a real past decision — auth mechanism, API design, rate limit, whatever.
02
Try to find the original reasoning. Not the decision — the why.
03
Time yourself. If it takes more than 60 seconds, run the setup anyway.
04
It's free, it's 30 minutes, and the worst case is a small Docker container.

Free, self-hosted, 30 minutes to running.

Elastic License 2.0. No account required. No card required.