A Digital Product Passport has to outlive your product, your vendor and possibly your company. That only works if it's built on open standards, hosted under EU jurisdiction, and exportable at any moment. That's how PassPer is built — deliberately.
Passports resolve at GS1 Digital Link URIs — /01/{gtin} with serial-level granularity (/21/{serial}). Carriers: QR, GS1 Data Matrix (real ISO/IEC 16022 ECC 200), NFC/RFID payloads. GTIN check-digit validation on intake.
Every passport serialises as JSON-LD with layered context — machine-readable, linked-data-native, and served with content negotiation from the same public URL humans see.
LiveOne click projects a passport into AAS submodels (application/aas+json) for IDTA / Industry-4.0 ecosystems and dataspace integrations — the lingua franca of industrial digital twins.
The passport structure, registry pointer records and access model track the CIRPASS-2 reference architecture and ESPR's mandated three-tier access (public / professional / authority), enforced at the resolver.
LiveHMAC-signed, hash-chained lifecycle events and SHA-256 version snapshots on every publish. PassPer Verify extends the same principle to any compliance document — hashed client-side, publicly re-verifiable.
LiveEvery published passport version is signed and hash-chained today. eIDAS qualified sealing (CAdES, over the version content hash) is built into the registry-submission path and verifiable via openssl-grade CMS checks — it activates the moment the qualified certificate is provisioned. UNTP credential issuance remains on the roadmap.
Built · activates at launchSee the numbers side by side, then try it on your own products.