Investor proof · verify it yourself
Don't take our word for it.
Verify it.
EVE is decision-evidence infrastructure — its whole premise is that claims should be independently checkable, not trusted. So here are ours. Every item on this page you can verify yourself, right now, without contacting us.
1 · Verify a signed decision — offline, in your browser
This is the moat made tangible. Below is a Governed Decision Certificate and its Ed25519 public key. The signature is checked entirely in your browser using only the public key — no EVE server is contacted. Tamper with the decision and the signature breaks. A model vendor structurally can't offer this: the value is that the verifier is not the party that made the decision.
What just happened: Ed25519 verification ran client-side over the exact signed bytes. This is what an external auditor does with our published key at /.well-known/eve-pubkey — verifying a decision years later without any dependency on EVE, the model vendor, or a shared secret.
1b · ...or verify from your own pipeline — one standalone script
The in-browser demo proves the cryptography. For your CI or model-risk pipeline, the identical check runs as a short script that imports nothing from EVE — only the cryptography package. It recomputes the decision's SHA-256 hash and verifies the Ed25519 signature against our published public key. Alter any field and it exits non-zero.
pip install cryptography # verify a CoreGuard decision against our LIVE published key python verify_eve_decision.py decision.json # ...or fully offline, against a downloaded key (air-gapped) python verify_eve_decision.py decision.json --pubkey eve-pubkey.pem # untouched record -> Result: [VERIFIED] (exit 0) # tampered record -> Result: [FAILED] HASH MISMATCH (exit 1)
Or with no download at all: a real production decision from POST /v1/decisions/evaluate (with include_evidence=true) can be re-checked by posting its evidence record to POST /v1/decisions/verify-evidence — a public endpoint that recomputes the hash and verifies the Ed25519 signature against the published key. It contacts no shared secret and verification confers no privilege.
2 · The rest of our claims, each self-serve
No screenshots. Live links to primary sources.
The code ships
The enforcement and certification engines are pip-installable packages with public test suites. pip install eve-coreguard
The public key is public
The Ed25519 verification key is published at a well-known URL so anyone can verify a certificate offline — no login, no shared secret.
/.well-known/eve-pubkey ↗The IP is filed
90 USPTO provisional applications (Serial Nos. 63/988,235 – 64/047,284), including a 3-family control-plane stack.
Patent portfolio ↗The product is live
The deterministic decision gate runs in production at POST /v1/decisions/evaluate, returning ALLOW / BLOCK / MODIFY with a signed audit record.
The commercial code is clean
The EVE CoreGuard and Proof packages import zero research modules — the surface area an investor worries about is walled off and checkable in the package manifests.
Inspect eve-proof ↗Mapped to the regulation
Controls map to EU AI Act Art. 12/15 record-keeping, ECOA/Reg B adverse-action, and SR 11-7 model risk — the forcing functions behind the buy.
Whitepaper ↗3 · Where we honestly are
The same standard we hold our certificates to: every number real or omitted.
- In place: the cryptographic primitive (independently-verifiable decision evidence), shipped products (EVE CoreGuard, Proof), 90 filed patents, the regulatory mapping, and founder distribution into lending.
- The gating milestone we are executing now: the first reference lender. We are deliberately pre-revenue on this SKU — the design-partner program ($37.5K, fair-lending sandbox replay) is live and in market.
- What we will not do: show invented traction. The honest version of a proof-of-demand slide is the one that lists only real conversations — and tells you exactly what we are manufacturing before we pitch a Series A.
Want the data room — or to replay your own decisions?
We will run a 14-day sandbox against real decision logs and hand back an exam-ready evidence package. No integration.