Vidimus
Explainer videos NL Start free

Vidimus/Products/Data

LiveVidimus Data

The state of your data, recorded outside your system.

A snapshot of a database or folder, or a web page as it was online. For databases and folders, you compute the fingerprints yourself: the content stays with you.

snapshot, folder and web page: today · automatically every night: in development

A server cabinet and a database in a frame on a platform; the fingerprints pass through four gates: fingerprint, key, clock and anchor
01 / WHAT IT DOES

What it does.

Vidimus Data records the state of data that is already in your systems: a database, a folder of files or a web page. For databases and folders, you compute the fingerprints yourself; only fingerprints, names and counts go to Vidimus. Each recording is one record, anchored within five minutes.

example · fictional snapshot
snapshot
orders · 1,284 rows
to Vidimus
fingerprints · table and column names · counts
content
stays with you
recorded
30 September 2026 · 00:00 (UTC+2)
counts as
one record
outcome
unchanged · timestamp + Bitcoin anchor
  • today

    Snapshot of a database

    You export your database. Each row gets a fingerprint on your side; only fingerprints, the names of tables and columns, and counts go to Vidimus. With the row key, no key values either.

  • today

    A whole folder

    Each file gets a fingerprint on your own computer; only the list of file names and fingerprints goes to Vidimus. In the dashboard by dragging in the folder, or with a small script.

  • today

    A web page

    Our server fetches the page itself: the HTML byte for byte, the response headers, the redirects, the TLS certificate and a screenshot. What it proves and what it does not

in developmentAutomatically every nightThe same export runs by itself every night, so you have a fixed starting point for every day.

in developmentComparing a database after an incidentThe current export next to the snapshot from before the incident: per row unchanged, changed or new.

AFTER AN INCIDENT

After a breach: per file, what stayed unchanged.

The history is on the same server. Your snapshot is not.

After a breach, a customer or insurer asks: how do you know this is still the same as before the breach? Your answer then comes from the system that was broken into.

If you recorded a folder before the incident, you put the current files next to it. Per file you see what is unchanged, changed, moved or gone, and your customer recomputes it for themselves. For a database we are building that comparison now; you can already record the snapshot itself today.

What Vidimus does not do

  • It does not prevent a breach and it does not detect one either.
  • It does not replace a patch, a backup or a security firm.
  • The proof only covers data that was anchored before the incident.
  • What to do now after a breach
02 / THE PROOF

Four steps, the same for every record.

  1. 01

    Fingerprint

    sha-256 · per row or per file, computed on your side

    The content cannot be reconstructed from a fingerprint. For a web page, our server computes them over what it fetched.

  2. 02

    Signature

    ed25519 · key of your device or system

    The list of fingerprints is signed as one record by whoever records it: your device, or your system's key.

  3. 03

    Timestamp

    rfc 3161 · per five-minute group

    An external timestamping service signs the group that contains the record, every five minutes. The time does not come from you and not from us. After that comes the qualified timestamp from GLOBALTRUST (eIDAS), per group, for customer organisations, usually within six hours.

  4. 04

    Anchor

    ledger (hash chain) → opentimestamps → bitcoin

    The root of the group goes into our ledger, where each entry hashes the previous one, and via OpenTimestamps into Bitcoin. Anyone who checks will see a change or deletion, even if we were the ones to try it.

Every step can be recomputed, even without Vidimus. All seven steps, from identity to erasure

03 / SPECIFICATIONS

Specifications and price.

database
fingerprint per row · to Vidimus: fingerprints, table and column names, counts · with row key no key values
folder
fingerprint per file · to Vidimus: file names and fingerprints · in the dashboard or with a small script
web page
HTML byte for byte · response headers · redirects · TLS certificate · screenshot 1280 × 2400
web limits
public pages only · at most five per minute per organisation · not in a confidential logbook
compare
folder: per file unchanged, changed, moved or gone · database: in development
every night
in development
anchored
anchored within five minutes
retention
ten years per logbook by default, adjustable
counts as
one record per snapshot, folder or web page
04 / USE CASES

What it is often about.

Examples, not limits: Vidimus is one product for every kind of record.

05 / QUESTIONS

What you want to know.

Do we have to upload our database to Vidimus?

No. The fingerprints are computed on your side. For a database, Vidimus only receives fingerprints, the names of tables and columns, and counts; with the row key, no key values either. For a folder, that is the fingerprints and the file names. Not the content itself.

Does it also work for data from before the incident?

Only if it was already anchored then. A snapshot taken today proves what your data looks like today, and that it has stayed unchanged since. That is why it is best to start now.

Does the counterparty see exactly what I saw on a web page?

Not necessarily. The record shows what was served at that address to our server, from our server in the EU. Someone viewing from another country, in another language or logged in may see something else. Every record says so.

Start today: your first snapshot is free.

No payment details needed. A director identifies your company once with the Belgian eID; after that you record your first folder, snapshot or web page. Are you a hosting provider or IT partner? If so, we will look together at how you can offer it to your customers.