Pre-endorsement stage Capabilities described on this site are planned. Nothing here describes a capability that currently exists in operation. See the roadmap.

A measurement basis you can rely on — and never a competitor.

Assurance work needs inputs that are independent, reproducible and open to challenge. Vemissure is being designed to provide exactly that, and to stop precisely where your accreditation begins.

The boundary, stated first

The operator carries the Article 12(3) obligation. The accredited verifier carries the ISO/IEC 17029 accreditation.[22] Vemissure supplies an input to both and carries neither. It is not a regulated entity, holds no licence, permit or accreditation, and does not verify, certify or assure.

That line is protected deliberately. Cross it in a single sentence and three things happen at once: the accreditation claim becomes a misrepresentation, the channel closes because the partner now sees a competitor, and the verifier's own impartiality position becomes harder to defend.

The proposition

Six properties an assurance workflow can use.

01

Independent

Sensor-neutral by construction. Vemissure owns no instruments, so it has no interest in any particular feed producing a favourable answer.

02

Calibrated

Conformal, coverage-calibrated intervals against a controlled-release corpus — a testable property rather than a nominal label.

03

Reproducible

A manifest designed for bit-identical re-derivation, so the figure can be regenerated and checked years after filing.

04

Traceable

A GUM-form Level-4 uncertainty budget with SI traceability, rather than a single opaque margin.[19]

05

Bounded

Detection floors and scope limits are published in the pack itself. You are told where the constraint does not apply.

06

Embeddable

The planned Verifier Edition licenses the engine inside your own assurance product rather than sitting beside it.

Where it sits

Inside the workflow, below the judgement.

The intended separation of responsibilities. Vemissure occupies one lane and does not cross into the other.

METHANELENS — MEASUREMENT BASIS OBSERVATIONRECORD QUANTIFICATION CALIBRATEDUNCERTAINTY RECONCILIATION EVIDENCEPACK Measurement, uncertainty and evidence. No verification opinion is formed here. EVIDENCE HANDOVER ACCREDITED VERIFIER — ISO/IEC 17029 SCOPE &MATERIALITY EVIDENCEREVIEW CHALLENGE& TESTING JUDGEMENT VERIFICATIONSTATEMENT Scope, testing, judgement and the statement remain entirely the verifier's. Vemissure supplies an input. It does not verify, certify or assure.

Programme licensing

One programme relationship, 8–25 operators.

The verifier-embedded licence (register entry I-6) is the planned route by which a certification programme or verification body licenses the engine inside its own assurance product. The planning assumption is a reach of 8–25 operators per programme at £8–15k per facility.

For the programme it means a consistent, reproducible measurement basis applied uniformly across clients — one that the programme does not have to build or defend itself. For Vemissure it means reach without a proportional sales force. Both sides benefit from the same property: consistency.

Commission Recommendations C/2026/5172 and C/2026/5176 of 20 July 2026 set out a transitional application and penalty grace period, and separately a defined independent-certification route.[18] The net effect is a slower but more durable market — and a channel that did not formally exist a year ago.

£150k–£400k Indicative annual programme licence

Planning assumption from the business concept note, based on analogue pricing and currently unvalidated. Vemissure is pre-revenue; nothing has been transacted.

Planned Verifier Edition — R3, Month 20

Objective: turn one customer into a channel. Pass criterion: one certifier programme licence signed. Early programme conversations shape what the edition contains.

Assurance SLAs (I-11) are intended to carry contractual commitments on turnaround, reproducibility and defensibility support, aligned to verification timetables.

Questions verifiers ask

Answered without hedging.

QAre you trying to become a verifier?

No — and the business model depends on it. The verifier channel is planned to carry roughly a third of revenue, which is incompatible with competing for the same work. Independence from both the sensing side and the assurance side is the entire position.

QCan we reproduce your figures independently?

That is the design intent, and it is a stated target rather than a courtesy: bit-identical re-derivation from the manifest, years later. A measurement input that cannot be checked is of little use in assurance.

QHow would you evidence the calibration claim itself?

Gate R0 at Month 4: a published coverage benchmark computed on public controlled-release data, with a pass criterion of ≥90% empirical coverage of nominal 95% intervals. The method and code are intended to be published alongside it, with a right of reply for any system assessed.

QWhere do standards programmes fit?

Adopt, do not compete. Standardised satellite-methane metrology work strengthens the traceability position rather than undermining it; competing with it would be both futile and counterproductive.

QWhat is available today?

Nothing operational. Vemissure is at pre-endorsement stage and every capability described here is planned. What is available now is a conversation about what a verifier-facing measurement input would need to contain to be accepted into a filing.

Start a conversation

Build a defensible measurement basis for methane MRV.

Talk to us about operator workflows, verifier programmes, technical validation or strategic partnerships.