Vidimus
Explainer videos NL Start free

VIDIMUS/QUESTIONS/SENSORS AND LOGGERS

How do you show an insurer or GDP auditor that your temperature measurements were not adjusted?

Short answerBy anchoring every measurement outside your own system at the moment itself: a fingerprint per measurement, signed with the key of that logger, with an external timestamp within five minutes. In a claim or audit, you show the series of that device, and the insurer or auditor recomputes for themselves that no value was adjusted afterwards.

Updated on 29 October 2026 · Oskar Verschoren, Vidimus (VO Initiatives BV, Antwerp)

01 / HOW IT WORKS

How it works.

  1. Create the measurement source onceunit · range · own key

    In the app, you create each logger or sensor with a unit and a range. A value outside the range is refused. Your loggers and your measurement platform stay the same.

  2. Send every measurementPOST /measurements

    The device or your measurement platform sends every measurement to the API: source, time, one number and the unit. At most one measurement per ten seconds per device, in ascending time order.

  3. Fingerprint and signature per measurementsha-256 · ed25519

    Each measurement gets its own fingerprint over source, time, value and unit. A corrected value gives a different fingerprint. The measurement is signed with the key of that measurement source, which Vidimus keeps for you.

  4. Anchored within five minutesrfc 3161 · bitcoin

    An external timestamping service signs the group the measurement is in; an anchor in Bitcoin follows. If the group contains records of customer organisations, the group then also receives a qualified timestamp from GLOBALTRUST (eIDAS), usually within six hours.

  5. In a claim or auditthe series of the device

    You show the series of that measurement source: every measurement with its fingerprint, in ascending time order. A period without measurements remains visible as a gap. Whoever receives the evidence bundles recomputes them with the script that comes with them, without an account.

02 / ALSO NEEDED

What you need besides this.

  • A calibration certificate for each logger, traceable to a measurement standard. The EU guidelines on good distribution practice (GDP, 2013/C 343/01) require, among other things, calibrated measuring equipment and data that is retained and can be consulted.
  • The location of the sensor in the cold store or the trailer, and who started and read out the logger, and when.
  • An alarm procedure and a report per deviation: what happened, when you noticed it and what you did.
  • The handovers of the load, for example with a signed record at loading and unloading.
03 / LIMITS

What it does not prove.

  • That the logger measured accurately. Calibration and placement remain your responsibility. A wrong temperature stays wrong, but anchored as 'this was reported at the time'.
  • That the time in the measurement is right. That is the device's clock. The group's timestamp shows the latest moment by which the measurement was anchored.
  • That a measurement from a hacked system is accurate. If the measurement comes from the system that was attacked, what that system passed on is anchored. Use a separate logger if you want to show afterwards what happened.
  • Measurements from before the integration, or measurements that are older than 24 hours when they come in.
  • That the goods are in order or damaged, or who is liable. That is for your insurer, the auditor or the court to assess.
  • That Vidimus can never sign anything in the name of the measurement source. Vidimus keeps the key of the measurement source. It could be used to create a new measurement, but only with the anchoring time of that moment, not an earlier one; changing an existing measurement afterwards stands out.
04 / SPECIFICATIONS

Specifications and price.

transport
HTTPS · REST API · key in the x-api-key header
endpoints
POST /measurements · POST /measurements/batch
format
JSON · source, time, one number, unit
range
a unit and a range per measurement source; refused outside it
rate
at most one measurement per ten seconds per device, in ascending time order
after offline
send later together via batch, measurements up to 24 hours old
testing
test key that records nothing; response with "proef": true
retention
ten years per logbook by default, adjustable
price
€15 per device per month with at least one measurement · the first one free · unlimited measurements · excl. VAT
05 / QUESTIONS

Frequently asked questions.

Do I have to replace my loggers or measurement platform?

No. Your loggers and your platform stay. The platform or the device also sends every measurement to Vidimus. You first test the integration with a test key that records nothing; then the administrator creates the live key.

What if the logger is offline for a while?

Send the measurements that the device or your platform stored in the meantime later, together, via /measurements/batch, in ascending time order and no older than 24 hours. The time in the measurement is what the device reported; the group's timestamp shows when the measurement was anchored.

Does this replace the validation or calibration that GDP requires?

No. Vidimus is not a measuring system and approves nothing. It helps with one question in an audit or claim: is the data you show today the same as what the logger passed on at the time?

What can you still show if the refrigeration system is hacked?

Vidimus does not stop an attack and does not replace security. It helps afterwards. If a separate logger, apart from the attacked system, also sends every measurement to Vidimus, that measurement is also outside your systems within five minutes. You can then show when the temperature rose, and a gap in the series remains visible. A third party recomputes that themselves. If the measurement comes from the attacked system itself, what that system passed on is anchored, accurate or not. The occasion: on the night of 1 to 2 November 2026, a cyberattack set the refrigeration systems of dozens of Belgian supermarkets to defrost (VRT NWS, the news service of the Flemish public broadcaster, 2 November 2026).

What does it cost?

€15 per sensor or logger per month, only in a month in which the device sent at least one measurement. The first one is free and measurements are unlimited. Once you pay anything, at least €19 a month. Prices excl. VAT.

How we start: your first logbook today, the first 100 records free.

You create your account in two minutes, no payment details needed. A director identifies your company once with the Belgian eID; then you create your first logbook in a few minutes. Would you rather talk first? Book 15 minutes with the founder.