NEXUS infrastructure

Certify your impacts ten times faster, at a tenth of the cost.

From the meter to the registry, NEXUS automates certification: a few weeks instead of several months, at a cost within reach of any project, whatever its size.NEXUS automates certification: a few weeks, at a cost within reach of any project.

Certify a project See the architecture

Three upright layers read left to right: data streams enter the data layer, pass the verification layer and the registry layer, and leave as a certificate

02What it unlocks

Weeks, not years.

Conventional certification is slow and costly. NEXUS automates it, so any project can be certified, whatever its size.

Lead timesA few days or weeks, instead of months or years.

÷10

CostsCertification within reach of projects of any size.

03Architecture and traceability

From raw data to certificate, every link is explicit.

Four layers: measurement, calculation, verification, certificate. Each object is linked to the one before it: from any certificate, you can trace back to the original evidence.Measurement, calculation, verification, certificate: traceable back to the evidence.

Four stacked layers, from the meter at the bottom to the certificate at the top: reading, calculation, report, certificate; a dotted blue line runs down through every layer, from the certificate to its source

04Methodological corpus

A public, modular and versioned methodological corpus.

The NEXUS Standard sets the common principles. Modules bring the methods, protocols apply them to each type of intervention.One standard, modules, one protocol per intervention.

Read the Standard

The standard as an open book, above three modules as puzzle pieces, which feed the six protocols, one per intervention

05Executable infrastructure

Every written rule has an executable twin.

Each protocol ships with a YAML companion that conforms to JSON Schema 2020-12. Every line of code points to the normative clause it comes from.Every line of code points to its clause.

Discover Smart Protocol

A written page and a code window side by side, each line of code linked to the line of text it comes from

06Agentic infrastructure

AI-native infrastructure, where AI operates but never signs.

Every step is typed by mode: code calculates, the NEXUS agent assists, the verifier seals. All within a system aligned with ISO/IEC 42001.Code calculates, the agent assists, the verifier seals.

Discover the NEXUS agent

Three modes in a row: a terminal for the code that computes, a spark for the agent that assists, a seal in full ink for the verifier who alone signs

07Evidence collection

Ranked evidence, collected at the source.

The dMRV+ platform connects to sensors and existing monitoring tools. Each data point is ranked from T1 to T4: weaker evidence lowers the certified volume.Weaker evidence lowers the certified volume.

Four sources from the strongest to the weakest, a connected sensor, a meter read by hand, a document, a statement, each with a bar of certified volume that shrinks as the proof weakens

08Water and carbon accounting

Water and carbon accounting: one reading, several impacts.

The same reading can feed the Water, Carbon, Energy and Performance modules. Each keeps its own method, unit and certificate, with no double counting.One reading, four impacts, no double counting.

See the protocols

One meter in full ink feeding four impacts, a drop for water, CO₂ for carbon, a bolt for energy, rising bars for performance, each ending in its own certificate

09Independent verifiers

Independent verifiers validate the PDD and verify the results.

Bodies accredited under ISO/IEC 17029, chosen and paid by Veracity, never by the project owner. They validate the design, then verify each monitoring period.Accredited bodies, paid by Veracity, never by the project owner.

Certify a project

The design document, then the same document checked once validated; three monitoring periods, each checked once verified; a certificate in full ink at the end

10Certification and registry

NEXUS certification and public registry.

Every certificate has a serial number and a permanent address. The registry tracks each issuance, transfer and retirement, as well as the encumbered, split and cancelled states.Every certificate has a serial number and a permanent address.

Explore the registry

The registry in full ink at the centre, linked to what it records: issuance, transfer, retirement, split, encumbered, cancelled

11Open APIs

Open APIs: data flows in and out without re-entry.

Data comes in through connectors from measurement systems. It goes out structured for reporting, AI agents and the digital product passport. Compatible with W3C VC 2.0, SAREF4WATR, FIWARE, JSON-LD and the EU Dataspace.Data comes in through connectors and goes out structured, without re-entry.

Request API access

A sensor and a meter send their data to the open interface in full ink, which passes it on to reporting, AI agents and product passports

12Get started

See the infrastructure run on your project.

One pilot project is enough: PDD, monitoring plan, first verified results.One pilot project is enough.

Get started

+Questions

Does Veracity verify its own certificates?

No. A body accredited under ISO/IEC 17029, chosen and paid by Veracity, validates the PDD and verifies every result. Veracity never signs.

Can AI issue a certificate?

No. The NEXUS agent prepares and checks; issuance follows the verifier’s opinion, and integrity rules run as deterministic code.

Can a certificate be recalculated years later?

Yes. Each certificate states the pinned versions of the protocol, modules and formulas; the same calculation gives the same result.

How do I access the APIs?

On request, through the contact page: we open access according to your use (data integration, registry, AI agents).