Skip to content
Alpha — Odal Node is in active development. APIs, schemas, and docs may and will change before 1.0.

What the core does

The core is the regulatory standard expressed in code: the rules a compliant Digital Product Passport must satisfy. It is open under Apache-2.0, carries no infrastructure — no database, no server, no configuration — and anyone may build on it.

What it gives you

  • A definition of a passport — its identity, who issued it, what it’s made of, the sector-specific data the regulation requires, and the lifecycle it moves through. (The exact shape lives in the code, which is the authoritative reference.)
  • Validation — a passport is checked against its sector’s versioned schema. This is a pure, local operation: no network, no services, nothing leaves the machine.
  • Signing and verification — a valid passport is signed with the issuer’s own key, binding it to their published identity. Anyone can then verify it on their own, without the issuer’s systems and without Odal.
  • A lifecycle — draft, published, suspended, archived. The transitions are one-directional and recorded, so a passport’s history can’t be quietly rewritten.

Why it has no infrastructure

Keeping the core pure is what makes the open-core boundary real: if a piece of code needs a database or a network, it isn’t part of the standard — it belongs in the engine. It also means the same rules run anywhere, from a server to an edge runtime, unchanged.