Earnie

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.

Earniepayments-api 2VEvp.eng
payments-api / Scan Configuration

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.

Skip patternsComponent overridesInherited layers
Automatic scanningApplies on the next merge

On merge to payments-api’s default branch on GitHub.

Pre-commit and coding agentsSelf-checks
Coding agents over MCP

The agent authenticates with an API key made with the Coding agent (MCP) preset, and sees only the tools and projects that key allows.

Pre-commit hook

Runs from the pre-commit hook appear in Self-checks for 30 days.

earnie hook install
What earnie mcp setup addsper client
Claude CodePolicy block, review hooks and session-start hook
CursorPolicy block, review hooks and session-start hook
CodexThe same, once the hooks are approved with /hooks
VS CodePolicy block
Pull-request feedbackApplies on the next pull-request scan
Summary comment

Only on failure still refreshes an existing comment, so no stale red verdict stays up.

Inline comment floor

Lower severities stay visible in Earnie and in the summary.

Draft pull requests

Skip leaves a draft unscanned until it is marked ready.

payments-api / Self-checks

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.

SourceFilesGateWhen
Claude Codekey: payments-agent2BLOCK2 min ago
Cursorkey: web-agent5PASS14 min ago
pre-commitm.ortiz1WARN1 hour ago
Codexkey: payments-agent3PASS2 hours ago
Claude Code · 2 filesBLOCK
Violation
pdf-forge 2.3.0 is 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.

Passing
3
Warn or approval
3
Blocked
1
ProjectMerge gateNeeds attentionLast scan
payments-apiBLOCK2 policy results block a merge2 hours ago
checkout-webPASSNothing needs attention40 min ago
mobile-appAPPROVAL14 results need approval1 hour ago
data-pipelineWARN9 results warn3 hours ago
auth-servicePASSNothing needs attention25 min ago
search-apiWARN3 components carry no license assertion5 hours ago
billing-workerPASSNothing needs attention1 hour ago
payments-api / SBOMs

SBOMs

Snapshots of a scan, exported as CycloneDX 1.7. Reports are frozen at generation and anchored to one scan.

anchored to scan 42
RecordFormatAnchorDownload
SBOMrelease 4.12CycloneDX 1.79a91b12a↓ JSON
Compliance reportrelease 4.12PDF · CSV9a91b12a↓ 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
Earnie for Head of Engineering
Earnie

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.

Earniepayments-api 2VEvp.eng
payments-api / Scan Configuration

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.

Skip patternsComponent overridesInherited layers
Automatic scanningApplies on the next merge

On merge to payments-api’s default branch on GitHub.

Pre-commit and coding agentsSelf-checks
Coding agents over MCP

The agent authenticates with an API key made with the Coding agent (MCP) preset, and sees only the tools and projects that key allows.

Pre-commit hook

Runs from the pre-commit hook appear in Self-checks for 30 days.

earnie hook install
What earnie mcp setup addsper client
Claude CodePolicy block, review hooks and session-start hook
CursorPolicy block, review hooks and session-start hook
CodexThe same, once the hooks are approved with /hooks
VS CodePolicy block
Pull-request feedbackApplies on the next pull-request scan
Summary comment

Only on failure still refreshes an existing comment, so no stale red verdict stays up.

Inline comment floor

Lower severities stay visible in Earnie and in the summary.

Draft pull requests

Skip leaves a draft unscanned until it is marked ready.

payments-api / Self-checks

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.

SourceFilesGateWhen
Claude Codekey: payments-agent2BLOCK2 min ago
Cursorkey: web-agent5PASS14 min ago
pre-commitm.ortiz1WARN1 hour ago
Codexkey: payments-agent3PASS2 hours ago
Claude Code · 2 filesBLOCK
Violation
pdf-forge 2.3.0 is 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.

Passing
3
Warn or approval
3
Blocked
1
ProjectMerge gateNeeds attentionLast scan
payments-apiBLOCK2 policy results block a merge2 hours ago
checkout-webPASSNothing needs attention40 min ago
mobile-appAPPROVAL14 results need approval1 hour ago
data-pipelineWARN9 results warn3 hours ago
auth-servicePASSNothing needs attention25 min ago
search-apiWARN3 components carry no license assertion5 hours ago
billing-workerPASSNothing needs attention1 hour ago
payments-api / SBOMs

SBOMs

Snapshots of a scan, exported as CycloneDX 1.7. Reports are frozen at generation and anchored to one scan.

anchored to scan 42
RecordFormatAnchorDownload
SBOMrelease 4.12CycloneDX 1.79a91b12a↓ JSON
Compliance reportrelease 4.12PDF · CSV9a91b12a↓ 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