A structural asymmetry in physical operations.
In the world's most consequential physical operations, the evidence of what happened is produced and controlled by the same parties whose actions are being judged. Evolkai exists to replace that with forensic-grade evidence records built to survive courtroom and litigation scrutiny.
Operators document their own custody. Inspectors record their own conclusions. Carriers timestamp their own handoffs. The records that should resolve disputes are exactly the records under challenge — and counsel on the other side of the table knows exactly how to challenge them. Server-side timestamps are editable. Database entries can be backdated. CCTV chains of custody are reconstructable. ERP exports are filtered before they're shared. Under adversarial scrutiny, conventional records share a fatal flaw: they are self-generated, self-stored, and self-presented by the interested party. Their evidentiary weight collapses precisely when it matters.
Separation of powers, applied to evidence.
Trust in physical operations cannot be a feature retrofitted onto operational software. It has to be an architecture — one in which execution, evidence generation, storage, governance, and verification are handled by structurally independent parties. If any one party controls more than one of those layers, sophisticated counterparties will challenge the evidence on exactly that basis. Evolkai exists to provide the evidence-generation layer, and to provide it independently of the parties whose work it documents.
Four components. Verifiable end-to-end.
The Evolkai stack is purpose-built for trust generation, not retrofitted from general-purpose cryptography services. Each layer has a single, narrow responsibility, and the chain between them is auditable.
The HSM
The cryptographic root deployed at each facility. Designed for FIPS 140-3 Level 3 — the certification standard required for evidence to survive adversarial scrutiny in regulated and litigated contexts. Owned and operated by Evolkai under a lease-and-service model so the operator never has physical control of the sealing device.
Edge Primitives
A catalog of trusted devices — biometric readers, weighbridge interfaces, inspection scanners, gate sensors, GPS-anchored handhelds — that sign raw measurements and authentication events at the source, before any operator system touches them. The signature happens where the event happens.
Proof Artifacts
The output: structured records of execution events that contain the event data, the signing identity, an independent timestamp, and a cryptographic chain back to the HSM and Edge Primitives that produced them. Verifiable by any party with the public schema — no Evolkai involvement required to validate.
Evidence Protocol Foundation
The schema governing artifact format, verification procedures, and accreditation of verification authorities is held by an independent foundation — not by Evolkai, not by any operator, not by any licensee. This neutrality is what allows artifacts to function as evidence across jurisdictions and counterparties.
From physical event to verifiable record.
The sealing flow is engineered so that the artifact's evidentiary chain begins at the physical event itself — not at the database write that records it.
Built for any sector where physical execution generates risk.
Trust infrastructure is industry-agnostic by design. Today, Evolkai's first commercial deployment is in logistics — under exclusive license to easyblox. The same architecture is available, on a non-exclusive basis, across every sector where physical events generate evidence that must survive scrutiny.
First commercial deployment: logistics, with easyblox.
Evolkai's trust infrastructure is exclusively licensed to easyblox in the logistics, supply chain, and physical trade sectors. The Lagos corridor is the first commercial proof point — a deployment environment chosen specifically because logistics disputes are frequent, high-stakes, and adversarial. If the architecture holds there, it holds anywhere.
Inquire about non-exclusive sectorsThe conditions for hardware-rooted trust have arrived.
FIPS 140-3 baseline shift
The successor standard to FIPS 140-2 is reshaping what counts as defensible cryptographic infrastructure. Regulated and litigated contexts are migrating their floor.
Synthetic evidence is cheap
Generative AI has collapsed the cost of producing fabricated photographs, documents, and signatures. The only durable defense is evidence that was tamper-evident from the moment of capture.
Audit and disclosure are tightening
Across jurisdictions, regulators are moving from periodic attestation toward continuous, machine-verifiable disclosure. Self-generated logs no longer clear the bar.
Logs describe what happened. Proof demonstrates it.
Conventional records and forensic-grade artifacts occupy fundamentally different categories of evidence. One is testimony by the interested party. The other is an independently attested fact.
Logs, audit trails, ERP exports, CCTV, scans
Generated by the operator's own systems. Stored on the operator's servers. Presented by the operator as evidence of the operator's compliance.
- ✕Server-side timestamps editable by system administrators
- ✕Database entries modifiable — no cryptographic integrity guarantee
- ✕Records retrievable only with access to the operator's systems
- ✕Authenticity cannot be proven without trusting the presenting party
- ✕No independent attestation of time, identity, or authorization
- ✕Credibility ceiling under adversarial legal scrutiny
Sealed at the moment of action
Generated by controlled execution workflows. Sealed by independent trust infrastructure. Timestamped by a neutral authority. Governed by a standards body. Verifiable by any party without system access.
- ✓Hardware-rooted cryptographic seal (ECDSA-P384 inside an HSM)
- ✓Tamper-evident — any modification breaks the fingerprint match
- ✓Independent RFC 3161 timestamp from a neutral authority
- ✓Identity-bound to the operator, device, and authorization chain
- ✓Verifiable by any party via public endpoints — no system access required
- ✓Court-admissible grade under recognized international standards
Built to survive the courtroom.
Every layer of the proof artifact aligns with recognized international standards for cryptography, evidence handling, data protection, and electronic-signature law. Each entry below is a click — open it to see the role it plays in the architecture.
Built so nobody — including us — can hold the system hostage.
Evolkai's value to a licensee depends on the licensee being able to trust that we cannot, will not, and structurally do not have the leverage to behave opportunistically. These commitments aren't marketing. They're built into the agreements that govern our relationships.
Independent provider
Evolkai does not operate in any of the industries it serves. We sell trust infrastructure; we do not compete with the businesses we equip. This separation is structural, not promised.
Lease-and-service hardware
Evolkai retains continuous title to all HSMs and Edge Primitives we install. Operators have right of use, never ownership. If an operator owned the sealing hardware, defense counsel could argue the operator could have manipulated it. Title resolves that argument by design.
Neutral standard governance
The artifact schema is held by the Evidence Protocol Foundation, an independent body. Neither Evolkai nor any licensee can change the rules of verification unilaterally.
Continuity guaranteed
If Evolkai ceases operations, title to deployed hardware transfers automatically to the licensee — preserving operational continuity. Existing Proof Artifacts remain verifiable indefinitely. The system survives us.
Bounded, benchmarked pricing
Licensee fees are individually capped, fixed for five-year windows, with annual benchmarking against published Cloud HSM pricing. No surprise fee categories. No discretionary surcharges.
Irrevocable license rights
Where exclusivity is granted, the license cannot be terminated, suspended, or modified except for uncured material breach. Licensees can build long-term businesses on top of Evolkai infrastructure with confidence in the foundation.
Evolkai exists because the trust layer for physical operations had to be built right — and could not be built inside any of the companies that need it.
I have spent years building product across multiple industries, and the same problem appears in each one: the most consequential events generate evidence that the parties to the events produce, store, and present. The asymmetry isn't a software bug. It's an architectural choice that nobody had revisited.
So we revisited it. Hardware-rooted sealing at the source. Independent timestamping. A neutral schema body. Lease-and-service hardware so the operator never has physical control of the device that signs against them. The point isn't to make trust louder. It's to make it structural.
If you operate in a sector where evidence has to survive scrutiny — and you've been quietly aware that your current documentation wouldn't — we should talk.
Tell us what your evidence has to survive.
Every deployment begins with a specific question: where in your operation does an event need to become evidence that holds up to scrutiny? Tell us that, and we'll tell you how the architecture maps to it.
For non-exclusive sectors
Energy, mining, pharmaceuticals, healthcare, financial services, government, manufacturing, construction, agriculture, and other sectors outside logistics. Discuss licensing terms, deployment requirements, and timelines.
licensing@evolkai.comFor architects, CISOs, and integrators
Discuss the architecture document (EVO-ARCH-2026-001), Edge Primitive catalog, integration patterns, certification status, and verification protocols. NDA available on request.
hello@evolkai.com— Or see how it all comes together end-to-end.
Open the proof engine demonstration Token required