EvidenceVaultEvidenceVault
Sign inRequest a pilot →
About

EvidenceVault.

A UK-sovereign cold-storage platform purpose-built for digital forensic evidence. Built and operated in the United Kingdom; engineered around the trust boundary between the force that owns the evidence and the platform that stores it.

EvidenceVault was started after a year spent inside three Digital Forensic Units watching the same problem: closed-case evidence lives on shared SAN, on hard drives in evidence rooms, on optical media in cold storage cupboards — anywhere but a system designed for it. Retrieval is hours or days. Integrity is asserted, not provable. Retention compliance is a spreadsheet exercise. When CPS calls back six years later, the right answer is "we have the evidence, here is the cryptographic proof it has not been touched" — and that answer was, until now, simply not a product anyone could buy.

We exist to build the system that gives that answer. UK-sovereign Azure topology; force-controlled encryption keys; immutable WORM storage with double encryption; hash-chained audit log. The platform we operate is deliberately constrained — we cannot read your evidence, cannot delete it, cannot change it. That is not a policy choice. That is the architecture.

1
UK-sovereign by construction

Every byte of evidence — primary, audit log, metadata — lives in Azure UK South. No replication overseas, ever. Cross-region egress is policy-blocked at the platform layer.

2
The force holds the key

Customer-managed encryption keys live in the force's own Key Vault, never the platform's. We can show you the cryptographic proof in under a minute — disable, watch reads fail, re-enable, watch them succeed.

3
Audit is mathematics, not policy

Every action is hash-chained. The force can verify chain integrity end-to-end on demand. Tampering is detectable in milliseconds; concealing it would require rewriting every row from the tamper point to the tail.

4
Operator-blind by build

The platform operator runs the infrastructure but cannot read the data. Plane separation is enforced in the build graph — operator code does not even compile against the tenant data layer.

"If your evidence isn't perfect when you ask for it back, we have failed."

— EvidenceVault operating principle
Run a 90-day pilot for your DFU.
Dedicated UK-region tenant. Three named users. No commercial commitment.
Request a pilot →