Skip to main content

​
“Can Policy Scale Past the People Enforcing It?”

Set a policy once, by clicking fields with the Sentence builder or writing the CEL expression directly, and Earnie checks it everywhere: the editor, the pre-commit hook, the merge gate, and MCP. A policy belongs to your organisation rather than to a single project, so the same rule can be attached to several projects at once, and its Where This Applies panel names every one of them.

​
Developers Never Leave Where They Work

Checks arrive in the pull request and, once earnie mcp setup has run, in the coding agent itself, wired up once. There’s no separate portal to visit, no ticket to file.

​
The Audit View

The obligations a licence policy is meant to catch are the same evidence covered in Exporting an SBOM: licence obligations mapped down to the snippet, Attribution Documents rendered from a snapshot, and SBOMs that are versioned and retrievable rather than a one-off export. The audit log behind it all is never edited or deleted.

​
What’s Next

Start with Setting Policies to write the first rule, or Exporting an SBOM to see the evidence a policy produces.