Ship at agent speed and still know what ends up in the product.
For Head of Engineering. Earnie puts your policies inside the coding agent’s loop, and keeps the record of what each release contains.
The check moves into the agent’s loop.
Agents write faster than people can review, so review turns into a bottleneck.
Earnie checks where the code is written. The project’s policies sit in the agent’s instructions before it starts, its changes are reviewed at the end of every turn, and when something breaks a rule the agent gets the reason and a suggested fix. The pull request check still decides what merges.
How Earnie works for an engineering org
From the agent’s first change to the release record. Click through the four steps, or use the app itself.
Scan Configuration
Controls how and when this project scans. They change what Earnie says and which paths it scans: never a verdict, a gate, or a finding already recorded.
On merge to payments-api’s default branch on GitHub.
The agent authenticates with an API key made with the Coding agent (MCP) preset, and sees only the tools and projects that key allows.
Runs from the pre-commit hook appear in Self-checks for 30 days.
| Claude Code | Policy block, review hooks and session-start hook |
| Cursor | Policy block, review hooks and session-start hook |
| Codex | The same, once the hooks are approved with /hooks |
| VS Code | Policy block |
Only on failure still refreshes an existing comment, so no stale red verdict stays up.
Lower severities stay visible in Earnie and in the summary.
Skip leaves a draft unscanned until it is marked ready.
Self-checks
Reviews of code sent by coding agents and the pre-commit hook. A self-check creates no findings and leaves the project’s posture alone. Results stay linked for 30 days.
| Source | Files | Gate | |
|---|---|---|---|
| Claude Codekey: payments-agent | 2 | BLOCK | |
| Cursorkey: web-agent | 5 | PASS | |
| pre-commitm.ortiz | 1 | WARN | |
| Codexkey: payments-agent | 3 | PASS |
- Violation
pdf-forge 2.3.0is AGPL-3.0- Policy
- Block banned licenses
- Suggested fix
- Use an MIT- or Apache-2.0-licensed alternative
- Scanners
- oss, crypto
All projects
The merge gate from each project’s latest scan, with what needs attention.
| Project | Merge gate | Needs attention | |
|---|---|---|---|
| payments-api | BLOCK | 2 policy results block a merge | |
| checkout-web | PASS | Nothing needs attention | |
| mobile-app | APPROVAL | 14 results need approval | |
| data-pipeline | WARN | 9 results warn | |
| auth-service | PASS | Nothing needs attention | |
| search-api | WARN | 3 components carry no license assertion | |
| billing-worker | PASS | Nothing needs attention |
SBOMs
Snapshots of a scan, exported as CycloneDX 1.7. Reports are frozen at generation and anchored to one scan.
| Record | Format | Anchor | Download |
|---|---|---|---|
| SBOMrelease 4.12 | CycloneDX 1.7 | 9a91b12a | ↓ JSON |
| Compliance reportrelease 4.12 | PDF · CSV | 9a91b12a | ↓ PDF ↓ CSV |
Guardrails that hold at agent speed
-
Policy inside the agent loop
A rule in a prompt is a suggestion. A review at the end of every turn is a check. Licence, vulnerability and cryptography questions get answered while the agent is still writing, and it fixes what it broke before anyone opens the pull request.
-
One status for every project
Each project shows pass, warn, block or approval required from its latest scan, with what needs attention attached. Your engineering managers see the same view you do, and human review goes where something was flagged.
-
Evidence for every release
SBOM, CBOM and AIBOM export in CycloneDX 1.7, and compliance reports stay frozen to the scan they describe, ready for a customer’s security review or a CRA request. Earnie identifies open source down to snippet level, so it finds copied open source code, even when there is no manifest to read. Your code stays on your server. On SaaS, only fingerprints leave it.
Agents check the rules while they write, and the pipeline confirms it. When someone asks what went into a release, the answer already exists.
Someone will ask what went into this release, and which checks it passed. Earnie keeps that record.
Try it on your repo