Earnie

Trust & data handling

Your code stays on your server. On SaaS, only fingerprints leave it.

Same chain. The boundary moves.

Earnie runs on your server in both models, and so does your record. It identifies your code by its fingerprints. What changes is where the knowledge base that matches them lives.

Both are single-tenant: one deployment per customer, structurally isolated from every other customer.

Hosted by us
Your network
Matches
Your code stays on your server
Earnie UI + API
ready
Crypto detectionlocal
OSS fingerprintingvia KB
AI model fingerprintingvia KB
Your recordupdated
findings · BOM · decisions
Knowledge base Earnie · hosted API
Returns
Component + version Licence CVEs Snippet origin AI model provenance
Fingerprints hashes only
Internet
Not required
KB updateoffline bundle · periodic
manual transfer
Deployment: SaaSSaaS. Your code, Earnie and your record stay in your network. Earnie sends only fingerprints to the knowledge base, hosted by us, and gets matches back.YOUR NETWORKYour codeEarnieUI + APIYour recordMatchesFingerprintsKnowledge baseEarnie · hosted APIHOSTEDBY US

No internet. No exceptions.

On-prem, Earnie runs fully air-gapped, with no internet connection at all. The knowledge base runs on your server too, and updates arrive as an offline bundle your team transfers in.

Your data, where you need it.

Earnie runs wherever your server is. On SaaS, choose the region of the knowledge base. Either way, your code and your record stay where your obligations say they must.

Deterministic by design.

Every finding traces to hard, reliable data: the same input produces the same result, every time. Results you can trust, and regulators can audit.

Ask us how your code is handled.

Request a demo
Trust and data handling | Earnie
Earnie

Trust & data handling

Your code stays on your server. On SaaS, only fingerprints leave it.

Same chain. The boundary moves.

Earnie runs on your server in both models, and so does your record. It identifies your code by its fingerprints. What changes is where the knowledge base that matches them lives.

Both are single-tenant: one deployment per customer, structurally isolated from every other customer.

Hosted by us
Your network
Matches
{{ packets }}
Your code stays on your server
Earnie UI + API
{{ status }}
Crypto detectionlocal
OSS fingerprintingvia KB
AI model fingerprintingvia KB
Your recordupdated
findings · BOM · decisions
Knowledge base Earnie · hosted API Earnie · offline, on your server
Returns
Component + version Licence CVEs Snippet origin AI model provenance
Fingerprints hashes only
Internet
Not required
KB updateoffline bundle · periodic
manual transfer
{{ popTitle }} {{ popMeta }}

{{ popBody }}

12=5f1c9a0e,b72e04d1 17=93d2e10f 19=c05e9a13,6e3d21b8
Deployment: SaaSSaaS. Your code, Earnie and your record stay in your network. Earnie sends only fingerprints to the knowledge base, hosted by us, and gets matches back.YOUR NETWORKYour codeEarnieUI + APIYour recordMatchesFingerprintsKnowledge baseEarnie · hosted APIHOSTEDBY USDeployment: on-prem or air-gappedOn-prem. Your code, Earnie, your record and the knowledge base all run on your server. Earnie sends fingerprints to the knowledge base and gets matches back inside your network. No internet connection is required.YOUR NETWORKYour codeEarnieUI + APIYour recordMatchesFingerprintsKnowledge baseOffline, on your serverNot requiredInternet

No internet. No exceptions.

On-prem, Earnie runs fully air-gapped, with no internet connection at all. The knowledge base runs on your server too, and updates arrive as an offline bundle your team transfers in.

Your data, where you need it.

Earnie runs wherever your server is. On SaaS, choose the region of the knowledge base. Either way, your code and your record stay where your obligations say they must.

Deterministic by design.

Every finding traces to hard, reliable data: the same input produces the same result, every time. Results you can trust, and regulators can audit.

Ask us how your code is handled.

Request a demo