EpochCore — Post-quantum, data-sovereign provenance

One artifact · end-to-end

The full CIA triad — post-quantum, sovereign.

Confidentiality, integrity, custody, and longevity in a single sealed artifact. Minted online with hardware-backed keys; opened and verified offline, forever.

Confidentiality

Encrypt to recipients

Only your named recipients can open it. Hybrid post-quantum encryption performed against hardware-custodied keys.

ML-KEM-1024 · producer-side HSM

Integrity + Authenticity

Triple post-quantum seal

A tamper-evident seal bound to the exact bytes, verifiable with no server and no trust in us — three independent signature families.

Ed25519 + ML-DSA-87 + SLH-DSA-128f · offline

Custody + Timestamp

HSM custody & immutable anchor

Signing keys never leave a FIPS hardware security module. Each seal is anchored to a write-once log — an independent, immutable timestamp.

IBM Key Protect HSM · WORM anchor

Sovereignty + Longevity

Verify air-gapped, forever

The verifier is fully self-contained. It runs with the network severed, in any jurisdiction, after the vendor and the network are gone.

zero-egress · region-resident · audit-ready

The category nobody else can sell

Everyone gives you one. We give you all of it.

Regulated and sovereign data is being mandated into a quadrant the market has nothing to sell into. Here's the gap.

What you get elsewhere — pick one

✕Online-only notary — proof dies the day the service does. No air-gap, no longevity.

✕US-cloud KMS — illegal for sovereign and residency-bound data; keys and bytes leave the region.

✕Classical crypto — RSA/ECC break under a quantum computer; "harvest now, decrypt later" is already happening.

What EpochCore gives you — the same seal, both ways

Verified offline-forever — self-contained, air-gapped, no vendor dependency.

Corroborated against a live immutable authority — independent timestamp + custody when you want it.

Post-quantum by construction — NIST FIPS-204/205 signatures and ML-KEM-1024, today.

Sovereign by default — bytes never leave the region; you control where verification runs.

How it works

Seal online. Verify offline. Corroborate when you choose.

The producer and the consumer confirm the same seal two independent ways — each corroborating the other.

01 — PRODUCE

Seal & encrypt online

Encrypt to recipients with ML-KEM-1024, triple-sign with hardware-custodied keys, and anchor the seal to the immutable log.

network: producer + HSM

02 — CONSUME

Open & verify offline

Open and verify the seal with the network severed — the signatures and the file-binding check run entirely on your side, in your region.

network: none · air-gapped

03 — CORROBORATE

Confirm against the live authority

Optionally confirm the seal against the live immutable authority for an independent timestamp and custody — opt-in, never required.

network: opt-in only

Built on standards, not promises

Every claim maps to a shipped primitive.

No proprietary "trust us" crypto. NIST-standardized post-quantum algorithms, FIPS hardware custody, and a write-once anchor.

ML-KEM-1024

Post-quantum key encapsulation — confidentiality to named recipients.

FIPS-203

ML-DSA-87

Lattice signature, NIST level 5 — integrity & authenticity.

FIPS-204

SLH-DSA-128f

Hash-based signature — a second, independent PQC family.

FIPS-205

Key Protect HSM

IBM FIPS hardware custody — signing keys never leave the module.

Custody

WORM anchor

Write-once immutable log — an independent, tamper-evident timestamp.

Provenance

Get started

Request access

For regulated, sovereign, and long-retention data — healthcare, legal, finance, defense, and AI provenance. Tell us who you are and we'll get you in.