One word against another
The recipient says 23 pallets, your customer says 26. Both exports come from a system that is itself in dispute. Whoever has the nicest PDF wins.
For vendors of TMS, WMS, ERP, IoT platforms and sector software. You build nothing. You put one proof layer under what you already have and sell your customers what they lack today: records that every party can check later — who, when and whether anything has changed since, even without Vidimus.
Your system shows what was recorded. It cannot show that it has stayed untouched since — an ordinary database can change afterwards, both at your customer and at their counterparty, and the history that would show it is in the same database. As long as that cannot be proven, every delivery, measurement or approval in a dispute comes down to one word against another.
The recipient says 23 pallets, your customer says 26. Both exports come from a system that is itself in dispute. Whoever has the nicest PDF wins.
The FASFC (the Belgian food safety agency), insurer, statutory auditor, court: they look in the system, and then ask whether it has stayed unchanged since and exactly when it was recorded. An export or screenshot from that same system says nothing about that.
“It was in the system, surely?” Every dispute your customer loses falls back on the software in which it happened — yours.
Today your customer pays in hours, lost claims and insurance premiums for something their software cannot do: show that a record has not changed since. With Vidimus underneath, that costs them €232 a month for 3,000 records and 1 measurement source (less use costs less, with a minimum of €19) — and they buy it from you, in the product they already know.
No cryptography in your code, no key management, no contract with a timestamping service, no Bitcoin. That is the layer. You send what you already have.
One call per customer: name, your customer number, company number. You get back a separate organisation with its own key and its own vault — fully separated from your other customers. Your customer's director signs the mandate once with the Belgian eID (you send them the signing link); after that, the same call also creates the logbook. Your partner key manages and counts, but never reads their content.
At every event in your system — delivery, approval, photo, document — you pass the data on with that customer's key. Sensor values come from a measurement source that you create per customer with a unit and a range; they go through /measurements and are included without limit per measurement source. What your system itself sends is a record. Vidimus hashes, signs, timestamps and anchors.
Each record gets a public check page and an evidence bundle that anyone can recompute without Vidimus. You show the link on your own screen. “Unchanged” — that is what your customer and their counterparty see.
{"naam":"Transport Peeters BV","extern_id":"klant-001","kbo":"BE0123456789","stroom":{"name":"CMR"},"systeem":"tms-koppeling"}org_id · api_key · systeemsleutel.id · stroom: null (waiting for the mandate)stroom.idFull description with examples per system type in the developer documentation (in Dutch). You get a sandbox and key right after accepting the agreement.
The more you do yourself, the more you earn. One tier applies per end customer; no exclusivity, for either party. Worked examples for a customer with 3,000 records and 1 measurement source a month: €232 at the standard prices, excl. VAT.
Your customer signs up with your link and pays Vidimus directly. You get 20% of every monthly invoice, for 24 months. No invoicing, no support.
€46.40 per customer per month · ≈ €1,114 per customer brought in
You buy at a 30% discount and invoice your customers under your own name, at your price. You are first-line support; we are second line. The pooled meter and the breakdown per customer are in your portal.
purchase €162.40 · margin €69.60 per customer · 50 customers = €3,480 a month
As for resellers, plus 100% of the implementation fee you agree with the customer yourself (usually €750 to €5,000 one-off). Up to 40% discount by agreement, based on volume.
margin €69.60 – €92.80 per customer + your implementation
Enter how many customers you connect and how many records a customer makes on average. The prices are those of the pricing page: per record and per measurement source; your tier sets your share. Everything stays in your browser, nothing is sent.
Never say that Vidimus vouches for the content. It establishes who, what, when, and whether anything changed afterwards — and lets everyone recompute that for themselves.
Company number checked in the Belgian company register (KBO), mandate signed with the eID, a certificate per device or system in the company's name. Every signature is Ed25519; the key stays on the device.
Not our clock: an external timestamp within five minutes, and GLOBALTRUST, a qualified trust service provider on the EU trusted list, puts a qualified timestamp (eIDAS) on the groups with records of customer organisations, usually within six hours. After that, the same root goes into Bitcoin via OpenTimestamps — a second witness, public and verifiable without Vidimus.
SHA-256 over the data and the attachments, per five-minute group in one Merkle tree. One byte different and the fingerprint no longer matches the anchor — even if we were to try.
Public check page, evidence bundle with a check script, case file for the court. Every step can be repeated with open tools. Originals encrypted per document, with a key per organisation; every decryption by our server is shown in the access log, which your customer sees for itself.
What you sell, to whom, which tier fits. After that you get your personal link.
Digitally, in the app. The acceptance is anchored with the hash of the text: both parties can recompute it later.
Your partner key, a sandbox end customer with a test logbook and the first curl command. No payment details needed.
One POST. A few minutes later you open the check page and see “unchanged” — what your customers will see. The sandbox needs no mandate; a real customer does.
Documentation per system type. The portal shows what is still open: agreement, sandbox, anchored test, first real customer.
End customers with their usage and list price, your purchase or share per month, the price sheet, and the questions you may and may not answer.
Yes. Co-branding (“your proof layer — powered by Vidimus”) is allowed in your product and documentation. Only the verification itself stays on the Vidimus domain: a check page with only your logo would undermine the separation between who records and who shows the proof, and that separation is exactly what your customer is buying.
Reseller and integrator: you. You receive one monthly invoice from us, with the discount of your tier as a separate line. Referral: we invoice the customer and pay out your share each quarter; the amount is shown in your portal every month.
That is allowed. The customer takes their records, keys and verification links with them; you cooperate with the handover. Running referral shares continue until the end of their 24 months.
No. You sell in your own name (reseller, integrator) or bring in customers for a fee that is limited in time (referral). There is no exclusivity and no goodwill or clientele indemnity. The agreement says so.
You may say: who, what, when and whether anything changed afterwards is on record and can be recomputed without Vidimus. You may not say: that Vidimus vouches for the content, that there is a “Bitcoin guarantee”, or that a court must accept the proof. The court weighs it; we make it recomputable. The explainer pack in the portal has the right wording.
Measurements from a measurement source (sensor, logger, weighbridge, GPS) are included without limit in €15 per measurement source per month in which it measures, the first one free, via /measurements. You create a measurement source with a name, a unit and a range (POST /sources, or per end customer through the partner API); only its own key may send measurements. Everything with its own content or ID — delivery, photo, CMR, approval — is a record and counts per item, per tier, via /registrations: also what your system sends, and also what still comes in through the old /ingest. See the pricing.
Each organisation has its own key; originals are encrypted per document (AES-256-GCM). Your partner key never reads content. If our server reads content for a case file or bundle, that is shown in the access log, which the customer sees for itself.
Evidence bundles are open formats with published verification steps (SHA-256, RFC 3161, Merkle, OpenTimestamps). They remain verifiable without Vidimus. The agreement says so, and so does the verification explanation.
All answers you may pass on to your customer: the sixteen hardest questions.
Thirty minutes to decide which tier fits you. After that: agreement, key and sandbox in five minutes, first test record in ten. You do not talk to a support desk, but to the person who built it.
REFERRAL 20% · RESELLER 30% · INTEGRATOR 30–40% · NO EXCLUSIVITY · AGREEMENT ANCHORED