Least privilege,
stated plainly.
Blue Mantis is a delivery tool with write access to your repository. Here is exactly what it holds, what it touches, and what it refuses to do.
Every key is stored against your user record in an isolated config table. There is no shared pool, no fallback to an environment variable in production, and no key is ever written to a log line.
Projects, work items, runs and suggestions are all filtered by user on every read and write. There is no global collection a bug could expose.
Blue Mantis creates branches, commits and pull requests. It does not merge, force-push, or touch your default branch.
Items and test cases are pushed only when you ask. The single automatic write-back is a status change when an item closes.
Only the files selected as relevant to the work item, plus the detected stack profile, are passed to the agent pipeline — scoped to what the keyword extractor judges relevant.
A run that fails records the error and stops. Nothing half-written reaches your repository, and stuck runs are swept after twenty minutes. A blocked Aegis gate records every finding and stops without writing anything to main. Nothing with a High or Critical finding can be promoted until it is resolved and the gate clears.
Aegis posts a blue-mantis/security status check to every PR. Configure one branch protection rule on main and GitHub enforces it — no High or Critical security finding can be merged until it is resolved. Blue Mantis never merges anything itself.
Where your data sits
| Processor | Purpose | What it sees |
|---|---|---|
| Supabase (Postgres) | Application database | Work items, runs, suggestions, your encrypted-at-rest config |
| Clerk | Authentication | Email, session, OAuth identity |
| Generation pipeline | Code generation, ranking, and review | Case file per run: work item, acceptance criteria, selected repository files. Agents: Raptia, Fovea, Synthesia, Veria. |
| Aegis (security pipeline) | Security vulnerability scanning | The committed code change only — same file the developer committed. No other repository files. |
| Resend | Transactional email | Your address and the run outcome |
For a complete security overview including sub-processor list, compliance status, AI model disclosure, and audit log details —
View our Trust and Security page →