0DATA
Services Preuve-as-a-Service Proof catalogue Why 0DATA Lab Contact
MRV · White-label · Verifiers & firms

When the rule changes, your files stay provable.

A white-label MRV engine for verifiers and compliance firms. Every regulation is a versioned configuration: at each revision, the impact on your files is recalculated and dated.

CBAM · NIS2 · energy Versioned diff · timestamped Anchored on a public ledger Verifiable by a third party
How it works, for you

Your job doesn't change. Your proof does.

You remain the verifier. The engine does what a spreadsheet cannot: version the rule, date the change, recalculate the impact and seal the proof.

01

You connect your mandates

Sectors, regulations, client files. Nothing to code: each applicable rule is a versioned configuration file.

02

The engine versions

CBAM, NIS2, EUDR… each rule becomes a dated config, with its version number and source.

03

A rule changes → a diff

Brussels revises a threshold or a scope. The engine produces the diff (before → after), dates it and lists the affected files.

04

The impact is recalculated

For each client file, the engine recalculates the consequence (exempt, subject, threshold crossed) and notifies your team.

05

The proof is sealed & anchored

The diff is hashed (SHA-256), timestamped and anchored on a public ledger. Your clients receive a report under your brand.

Concrete example

You are a CBAM verifier with 40 steel mandates. The omnibus package lowers the exemption threshold from 50 → 20 net tonnes/year. Result: 3 of your mandates, previously exempt, become subject. The engine lists them, recalculates their exposure, and seals the diff. You notify your 3 clients in 1 hour — instead of 2 days of manual re-configuration.

Live demo

Try a diff, now.

Choose a regulation, simulate a revision. The diff and its SHA-256 fingerprint are computed for real in your browser — exactly what is timestamped then anchored in production.

Choose a regulation
The problem

Every rule change costs you unbillable hours.

Threshold, scope, schedule, emission factor: since 2025, European texts have been moving continuously. You rework your files by hand — and you carry the risk.

Without tooling

  • Manual re-configuration at every regulatory revision
  • Risk of non-compliance on already validated files
  • Unbillable audit hours, melting margin
  • Hard to demonstrate when and why a file changed

With a proof engine

  • The rule is a versioned diff, applied automatically
  • Every file keeps its timestamped history
  • The impact of a change is recalculated for your clients
  • You demonstrate traceability — that's your added value
The mechanics, not the product

No rule is hard-coded.

The engine consumes versioned configurations. The regulation is an input — not your architecture.

Rule = versioned config file
→
Engine — generic MRV
→
Proof — timestamped · traceable
// When Brussels revises a threshold or a scope,
// for the importer it's chaos, for you it's untooled work,
// for us it's a configuration update in a few hours.
Regulatory Diff — historical examples

What "rules that change" means, concretely.

Three real changes to the CBAM scope, presented in diff format. The automated pipeline (detection, dating, impact recalculation) is being rolled out.

DIFF 011 January 2026

Transitional regime → definitive regime

Before

Quarterly emission declarations, with no financial obligation (transitional period 2023–2025).

After

Mandatory "authorised CBAM declarant" status; certificates become payable according to the phase-in schedule.

Impact: your clients move from declarative reporting to a real financial obligation — data quality becomes binding.
Source: Regulation (EU) 2023/956, definitive regime applicable from 1 January 2026.
DIFF 022025 — omnibus package

Exemption below 50 net tonnes per year

Before

Broad scope: most importers in the covered sectors entered the scheme.

After

Exemption for importers below 50 net tonnes/year (art. 2(3) of Regulation 2023/956, amended).

Impact: volume concentrates on large importers — your mandates change in nature, and the burden of proof shifts to their suppliers.
Source: Regulation (EU) 2023/956 art. 2(3), amended by the 2025 omnibus package.
DIFF 03Applicable from 1 January 2026

Scope of indirect emissions — Implementing Regulation (EU) 2025/2621

Before

Indirect emissions (electricity) expected across several sectors of the definitive regime.

After

Indirect emissions included only for cement (0.05) and fertilisers (0.30); out of scope for steel, aluminium and hydrogen.

Impact: your steel/aluminium checklists no longer include electricity — any file already prepared on that scope must be revised, otherwise non-compliance.
Source: Implementing Regulation (EU) 2025/2621, Annex I — indirect emissions limited to cement and fertilisers.
Historical examples, sourced from published texts. The proof mechanics (versioned diff + SHA-256 sealing + anchoring) are operational — automated detection of new revisions is continuously enriched. Try the demo →
White label

Your name. Your identity. Your reports.

We provide the proof layer. You remain your clients' regulatory point of contact.

Your brand

Reports, verification files and interfaces under your name. The end client only sees you.

Your added value

The engine automates the calculation and traceability. You keep the judgment and independence — what accreditation requires.

No capital link

No equity stake: the tool and the verification stay separate, to preserve your regulatory impartiality.

Pricing

A white-label engine, quoted on a per-project basis.

No subscription imposed: the price is calibrated to your mandates, your sectors and your dossier volume. Together we quantify the time the next regulatory revision will cost you — then we show you what the engine recovers.

Contact

Let's talk about your mandates.

A 30-minute call is enough to quantify the impact of the next regulatory revision on your files.