Skip to content

EU Digital Product Passports

Alpha · in active development

Signed by you. Verified by anyone.

Issue EU Digital Product Passports from your own infrastructure. Odal Node checks your product data against its product group's rules, signs it with your key and publishes the passport behind the product's QR code. Anyone can check it, even offline. You keep your data and your key. We never see either.

Tell us what you makeRead the docs
  • Free to self-host for your own products
  • No licence keys, no passport limits
  • Source code public on GitHub

Why now

Know which date applies to your products.

Passports arrive one product group at a time, each with its own date. Four passport obligations already carry a date in law:

After these, passports arrive product group by product group. The Commission's 2025–2030 working plan puts iron and steel first, then textiles, tyres and aluminium, then furniture and mattresses, with indicative adoption from 2026 to 2029. Each act will set its own passport dates when it is adopted.

Software you adopt now has to keep working as the next acts are adopted. In Odal Node, a new product group arrives as an update to its rules, not as a new system.

See a passport

One passport, read three ways.

The same battery passport shows each reader the part the law gives them. Pick a reader to see which parts they can read.

Read it as

Legal basis: Art. 77(2)(a) of the Batteries Regulation.

See the full exampleWhy it is not a ladder

Musterzelle EV Traction Battery 75 kWh

Musterzelle GmbH (an invented company)

Example data

  1. Part 1. Public informationVisibleWithheld

    Chemistry
    NMC
    Rated capacity (kWh)
    75
    Expected lifetime (cycles)
    1,800
    Withheld from this reader

  2. Part 2. Model detail, not publicVisibleWithheld

    Cathode material
    LiNi0.8Mn0.1Co0.1O2 and 2 more
    Component part numbers
    VBX-CELL-4680-NMC811 and 3 more
    Withheld from this reader

  3. Part 3. Evidence of conformityVisibleWithheld

    Test report results
    IEC 62660-2:2018 pass; ISO 6469-1:2019 pass; UN 38.3 pass; report VBX-TR-2026-0507
    Withheld from this reader

  4. Part 4. This battery's own historyVisibleWithheld

    Battery status
    Original
    Use so far
    8 charge and discharge cycles so far
    Withheld from this reader

Battery passport only. Other product groups get their access rules from their own acts.

How it works

Proof-bound: your data stays with you, and every published field is signed.

Manufacturers have trade secrets to protect. Regulators and customers need data they can trust. Odal Node handles both: your product data is validated and signed on your own infrastructure, and the node serves the signed passport, which carries the full product data with every field signed. Each reader sees the parts their access rights allow.

On your infrastructure

  1. ImportProduct data from CSV or Excel, including exports from your ERP.
  2. ValidateAgainst each product group's rules, on your own node.
  3. SignWith your own key, generated and held on your infrastructure.
  • Everything the node stores stays here, and so does your signing key, encrypted at rest.

On the web

  1. PublishThe signed passport becomes resolvable through its QR code and GS1 Digital Link.
  • Anyone reads the public part.
  • Repairers, recyclers and authorities read the restricted parts, on a verified credential.

Anyone, anywhere

  1. VerifyAnyone checks the signature against the identity on your web domain, without Odal. A passport's proof file can be checked even offline.

OdalNot in this path. Your product data never reaches us.

Data and trust

What Odal Node can and cannot see.

Your node runs on your infrastructure and we are not part of it, so we have no access to the production data behind a passport. This comes from how the software works, not from a policy. In detail:

We can see

What anyone can see: the public part of the passports you publish.

We cannot see

Your private keys, your raw production data and your supply-chain detail. They stay on your infrastructure, and we are not part of it.

We cannot change

Your published passports. Every field carries your signature, so a change made without your key fails verification.

How this works

For your engineers

For the people who will run it.

One service, on your infrastructure

The node is one self-contained service. Run it on your own infrastructure, or on a cloud you control.

Rules in a sandbox

Product-group rules run in an isolated sandbox, and new rules arrive as signed updates rather than rewrites of the software.

Export for Industry 4.0 systems

A node can serve a published passport in the Asset Administration Shell format. The field meanings use Odal's own identifiers for now, so a receiving system still has to map them.

Build it from the source

The source code is public. Build our setup tool once (you need Docker and Rust), and it sets up and starts a node on your own machine. No licence keys, no passport caps. Ever.

Standards and licences

Built on open standards.

  • GS1 Digital Link

    Product identification and QR resolution

    In place

  • JSON Web Signature

    How every passport is signed

    In place

  • did:web

    Issuer identity, anchored in your own web domain

    In place

  • W3C Verifiable Credentials

    How a reader proves who they are

    In place

  • IDTA AAS

    Export for Industry 4.0 systems, with Odal's own identifiers for now

    Partly in place

  • European DPP standards

    The six harmonised standards cited in July 2026

    Partly in place

Two licences: the library and the node.

  • The core libraryApache-2.0Open source

    Use it, adapt it and build on it freely.

    The library on GitHub

  • The nodeBSL-1.1Source available

    Running it for your own organisation's passports is free. Offering it to others as a hosted service, or shipping it inside a competing product, needs a commercial licence. Each release becomes Apache-2.0 four years after it is published.

    The node on GitHub

The licensing page has the detail, and the licence texts in each repository are the ones that bind.

The EU acts it applies

Where it stands

What works today, and what comes next.

Nobody is running this in production. The roadmap lists what is built, what is waiting on a legal step and what comes next, with no dates on anything unbuilt.

See the roadmap

Next step

Get ready for your products' passports.

Check whether your product needs a passport, find your product group, or tell us what you make and we will keep you posted as the software takes shape.

Tell us what you makeCheck if you need a passportFind your product group