Coming soon

This workflow is in development and is not available yet. It is a preview of a planned application built on the IP Vault evidence engine.

Register your interest
For labs, biotech R&D and CROs

Make every raw result defensible from the moment it is produced.

Seal protocols, assays and instrument outputs with a UTC-synchronised external timestamp, without uploading proprietary data to another SaaS platform.

External UTC time, not a workstation clock
Raw data stays local
Reason-for-change audit trail
Works alongside your ELN or LIMS

Evidence record

Biotech & Clinical

Coming soon
Record status Sealed and timestamped
Time source eIDAS qualified + Bitcoin
File storage Your cloud or local drive
Version Linked to prior certificate
Verification Shareable public record
Included in the archive
Declaration Manifest .tsr .ots ZIP

The problem

What makes this hard to prove today

Most evidence problems are not about whether a file exists. They are about whether you can show what it was, when it existed and that it has not changed since.

Local workstation clocks are not audit-grade

Device time can be changed and is weak evidence in an inspection. Regulators expect a time source outside the operator's control.

Heavy ELN and LIMS validation is out of reach

Smaller labs, academic core facilities and spinouts need a lightweight way to seal records without a long IQ/OQ/PQ programme.

Raw outputs can be edited before submission

Chromatography peaks, mass-spec output, blots and sequencing files need an early, tamper-evident anchor.

Changes need a documented reason

Annex 11 and ALCOA+ expect an audit trail and a reason for modification, not just a final file.

What you get

An evidence pack you can actually use

IP Vault produces the sealed record. Your team keeps control of the files and decides who receives the verification link.

01

Protocol and assay seals

Hash a protocol, raw output or dataset without sending the underlying file to IP Vault.

02

Externally sourced time

The digest is signed by an eIDAS-qualified timestamp authority and anchored to Bitcoin.

03

A change record

Record why a revision was made and link it to the prior certificate for a traceable history.

04

An inspector-ready package

Declaration, manifest and proof files in a ZIP your team keeps and controls.

How it works

Three steps, no new storage platform

1

Hash the record locally

The assay, protocol or dataset is fingerprinted in memory. The raw file is not uploaded to IP Vault.

2

Seal it with external time

The digest is timestamped through the qualified authority and anchored to the Bitcoin blockchain.

3

Store and hand over the evidence

Keep the evidence pack in your own cloud or local archive and share the verification record with QA, a partner or an auditor.

Regulatory context

Designed around regulated record-keeping

IP Vault is designed to produce an ALCOA+-aligned evidence record. It does not replace a validated ELN, LIMS, QMS or your own Part 11 compliance programme.

FDA 21 CFR Part 11
EMA EU GMP Annex 11
Good Laboratory Practice, 21 CFR Part 58
WHO Technical Report Series 996 Annex 5
MHRA GxP data integrity guidance
ALCOA+ principles

Who it is for

Built for teams that have to show their work

Talk to us about your workflow →
Heads of quality assurance Regulatory affairs leads Principal investigators CRO compliance leads Biotech R&D directors Academic core facilities

Common questions

The short answers

Does this make us Part 11 compliant?
No. It can support an audit-trail and record-integrity workflow, but compliance depends on your validated systems, SOPs and controls.
Do you receive our raw data?
No. Files are hashed in memory. IP Vault receives the digest and the declaration, not the underlying data.
Can we keep our existing LIMS?
Yes. The service is designed to sit alongside your existing systems, not replace them.
Can we record why a record changed?
Yes. Revisions require a reason and embed the previous certificate hash.

Create the record now, decide who sees it later

Start with a single protection run. Keep the archive, share the verification link, and add revisions when the work changes.