Proof-of-capture · Media provenance

Don't know what's real?

The Epistemic Suite helps you show your work is genuinely human.

Don't trust us, trust the device! Every capture includes a signed proof you can verify locally (Verifier CLI) or at ingestion (Epistemic Vault). Media Bridge then enriches metadata downstream without touching the original proofs.

Where C2PA and Content Credentials describe how a file was made and edited, Epistemic proofs are created at the moment of capture: tamper-evident, cryptographically signed, and verifiable by anyone.

Suite Flow

Recorder → Vault → Media Bridge

Verify capture proofs, then enrich and route metadata downstream.

Three products, one system.

Each product is focused. Together, they form a defensible chain of custody.

Epistemic Recorder

Capture with proof.

Android + iOS apps, plus the Epistemic Universal Box (EUB) for external camera workflows-all producing the same capture proofs, including randomized capture-time challenges recorded in the proof and visible in verification output.

Visit recorder.epistemicsuite.com

Epistemic Vault

Zero-trust ingestion.

A cryptographically enforced verification boundary: nothing is accepted unless it is provably correct.

Visit epistemicvault.com

Epistemic Media Bridge

Bridge the rest of your stack.

Post-ingestion metadata operations: enrich, normalize, and route content without touching the original proofs.

In build

Designed as a verification boundary.

Each Recorder capture includes a tamper-evident proof created at capture time. Recorder hashes the media and signs a manifest; Vault re-verifies at ingestion and issues a receipt; the free Verifier CLI can verify the proof locally. Media Bridge is post-Vault and operates on metadata only.

Capture-time proof Hash + signature verification Receipt + proof bundle
01

Capture

Recorder computes hashes, builds a signed manifest, and embeds provenance at the source.

02

Verify

Verify at ingestion (Vault) or locally (Verifier CLI); both re-check hashes and signatures.

03

Bridge

Media Bridge enriches and routes metadata downstream without altering or re-ingesting the original asset.

C2PA & Content Credentials

C2PA, Content Credentials, and the gap at capture.

C2PA is the open standard behind Content Credentials: signed manifests that record which tools made and edited a file. It is an important step for media provenance, but a valid signature shows who signed a claim, not what happened in front of the lens. Epistemic Suite focuses on that moment of capture.

What C2PA does well

A shared language for provenance.

Cameras, editing tools, and platforms can attach and read signed provenance manifests, so a file can carry its history of creation and edits in a common format.

Where concerns come up

Stripping, signers, and trust.

Credentials are often stripped when platforms re-encode uploads, and a missing credential proves nothing either way. A manifest is only as trustworthy as its signer, and AI generators and editing tools sign their output too.

What proof-of-capture adds

Evidence the camera acted.

Epistemic Recorder issues randomized challenges to the camera during recording and binds them, with on-device hashes and device attestation, into a signed proof. Anyone can check it with the free, open-source Verifier CLI.

Media Bridge

Unify everything your team already records.

Media Bridge is post-Vault. It connects distribution, post-production, and external metadata systems while keeping the original Vault-verified asset untouched. It is the connective tissue between verified capture and downstream workflows.

Multi-source

Video, audio, and photos.

Normalized

Consistent metadata and identifiers after ingestion.

Trusted

Preserve chain-of-custody while operating on metadata.

Verifier CLI

Independently verify what happened—locally.

The Verifier CLI is an open-source command line tool that validates Epistemic capture proofs outside the Vault. It recomputes hashes, checks signed manifests, and produces a clear verification report you can share or audit.

It does not try to “prove reality” from pixels alone. It verifies the capture proof and whether the file matches it.

It is free for everyone because trust cannot depend on a gatekeeper. Anyone should be able to verify originals with the same rules, using their own machine.

Open Verifier CLI on GitHub

What it is

Open-source verifier for Epistemic capture proofs.

What it does

Recomputes hashes, validates signatures, and reports verdicts.

Why it is free

So verification stays independent, transparent, and widely usable.

Ready to explore the suite?

Tell us what you are building and we will shape the right deployment.

Request access

FAQ: C2PA, media provenance, and proving what's real

Short answers for anyone looking for a defensible way to separate signal from synthetic noise.

How can I show my work is genuinely human?

Epistemic Recorder produces tamper-evident proofs at capture (hashes, signed manifests, device attestation, and randomized capture-time challenges recorded in the proof). Epistemic Vault re-verifies those proofs at ingestion, and the free Verifier CLI can verify them locally.

What is proof-of-capture?

Evidence created by the recording device itself at the moment of capture, rather than added afterwards. Epistemic Recorder hashes media on the device, records the randomized challenges the camera executed while recording, and signs everything into a tamper-evident manifest backed by device attestation.

What is C2PA, and does it prove a photo or video is real?

C2PA (the Coalition for Content Provenance and Authenticity) is the open standard behind Content Credentials: signed manifests that record which device or software created and edited a file. A valid credential shows who signed that history. On its own it does not show that a camera captured a real scene, and AI generators and editing tools sign their output too.

Is Epistemic Suite a C2PA implementation?

No. Epistemic proofs use their own manifest format, built from similar building blocks (CBOR manifests and COSE signatures), and they answer a different question. C2PA describes how a file was made and edited; an Epistemic proof shows that a real device captured it, including the randomized challenges the camera executed during capture.

What happens when Content Credentials or other metadata get stripped?

Any proof embedded in a file, C2PA or ours, can be removed when a platform re-encodes an upload, and a missing credential proves nothing either way. What matters is keeping a verifiable original: Epistemic Vault re-verifies each capture at ingestion and issues a signed receipt, and the Verifier CLI can check the original on any machine.

How is this different from deepfake or AI detection?

Detectors analyze finished pixels and estimate whether something looks generated, which gets harder as generators improve and compression erases traces. Epistemic Suite does not guess from pixels. It verifies a proof made at capture time, and whether the file still matches it.

Does the Epistemic Media Bridge push footage back into the Vault?

No. Media Bridge is post-Vault and handles metadata enrichment, normalization, and routing for downstream workflows. It does not re-ingest footage into the Vault and it does not alter the original proofs.

What does "verification boundary" mean?

It means you can check the same proof at the boundary: Recorder creates it at capture time, and it is re-verified before it is accepted. Verification can happen in Vault or on your own machine with the free Verifier CLI.

Why EU?

Epistemic Vault is proudly EU-based — governed by European law, hosted in Europe, and designed to operate independently of US jurisdictional control.