Relevance benchmarks tell you whether your retrieval is good. They say nothing about whether it is allowed. raggate exists to make that second question testable, repeatable, and documentable — with the same discipline a test suite gets.
You are about to roll out an index change, an embedding upgrade or a new connector, and you would like to know what it exposes before your users find out. You want a command with an exit code, not a dashboard.
You have been asked to sign off on an AI feature that reads from a corpus you do not control. You want evidence you can read months later, not a screenshot of a green tick.
You run one index across many customers or business units, and "similar documents" is exactly the boundary you cannot afford to blur.
The default embedder is seed-stable and runs locally, so the same inputs produce the same verdicts on any machine. Nondeterministic gate results are treated as a defect, not as variance to be tolerated.
An unreachable backend, a malformed response or an unresolvable document produces an error, not an empty result set. A tool whose job is finding leaks must never report a clean run because it quietly retrieved nothing.
Every finding is replayable from its record, and the source is Apache-2.0 so the logic behind a verdict can be read rather than trusted. Where the tool's coverage is narrower than a claim would suggest, it says so in its own output.
Remedies are ordered safest-first: narrow retrieval before you move data, and move data before you delete any. Rollback artifacts are written before mutations, not after.
raggate is a young project. The detection path is well covered by tests and exercised on every change; the commercial path has had exactly one real purchase, which was our own end-to-end test of checkout.
What exists instead is the thing itself: a repository you can clone, a sample corpus with planted leaks, and output you can inspect line by line. That seemed like a better opening argument than adjectives.
Questions, a pilot conversation, a bug, or a disagreement about how the oracle should treat some edge case — all welcome at the same address.
| What | Where |
|---|---|
| Anything at all | hitliqiwei@gmail.com |
| Security disclosure | Same address — see Security for what to include |
| Terms and data handling | Terms · Privacy |