One API call per unit
A REST API per brand registers a passport at the end of the line, with explicit validation feedback and protection against duplicate serial numbers. Test keys run in a sandbox that seals nothing.
For manufacturers at scale
Battery passports for the production line — and for the next fifteen years
For manufacturers that register thousands of units, connect their own systems, put the platform through a procurement and security review, and need the QR code on the label to keep working long after any contract.
Fits into the systems you already run
Your ERP or MES stays the source of the data; OrigoPass seals it, publishes it and keeps it answering.
Labels before the data
Pre-create passport IDs and print the QR codes ahead of production; each unit's data is sealed under its ID when it is ready.
Excel for the rest
Import product models and units from an Excel template — for the first migration, or for product lines without an integration.
Suppliers fill in their part
Carbon footprint, due diligence, cell chemistry: invite the cell maker or consultant to fill in exactly that block, and seal when the passport is complete.
Your identity provider
Single sign-on with Microsoft Entra ID or Okta, teams with rights per brand, and four-eyes approval on every rights change.
Standard exports
BatteryPass-Ready v2.0.1 JSON, W3C Verifiable Credentials, GS1 Digital Link and the identifiers for the EU DPP registry. See the evidence.
Quality you can prove, not just claim
An auditor, a customer or a market surveillance authority should not have to trust us — or you.
A register that cannot be rewritten
Every record carries a SHA-256 fingerprint of itself and of the record before it, and an Ed25519 signature. Change one historic byte and the chain breaks — publicly.
Verifiable without us
Each passport version is a signed W3C Verifiable Credential: any standard library checks it, without OrigoPass software.
Online when a server is not
A mirror at a second hosting provider re-verifies every record and serves the passports if the main server goes down. A mirror that falls behind takes itself out of rotation.
Your domain, for life
Passports answer on dpp.yourcompany.com with your logo and colours. The URL printed on the battery is yours, not ours.
An agreement that fits your production
Above the standard plans, the terms are written for you — and every change to them is sealed in the register.
Volume per month, with roll-over
An agreed number of new passports a month; optionally, what a month does not use carries over within the contract year.
Peaks without a stop
Above the agreement, registration simply continues at an agreed price per passport — or stops at a hard cap, if you prefer.
One invoice a year
Invoiced yearly, with all your brands and product categories — batteries now, ESPR product groups when they follow.
Onboarding and migration
We map your existing product data onto the passport model and import it with you, and agree the service level in writing.
For your procurement and security review
The questions purchasers and IT security ask us most, answered up front.
| Who are we? | Twenty9 Solutions (the Netherlands) operates OrigoPass. Company details, Chamber of Commerce and VAT numbers come with every quote. |
|---|---|
| Where is the data? | The register and all customer data are stored on servers in the European Union, with a standby mirror at a second hosting provider. Traffic reaches them through Cloudflare (protection and failover); every sub-processor is named in the terms. |
| Personal data in the register? | None. The sealed register holds product data only; user accounts, access requests and supplier contacts are ordinary records that can be erased. Our processing agreement under Article 28 GDPR is part of the terms. |
| How do your people sign in? | Passkeys or single sign-on with your own identity provider (OIDC: Microsoft Entra ID, Okta). Rights per brand, and every rights change needs a second admin's approval and lands in the sealed audit trail. |
| What runs in the visitor's browser? | Nothing of ours or of third parties: the passport pages contain no scripts and no third-party trackers, under a strict Content Security Policy. |
| Can anyone change a passport afterwards? | No — not you, not us. Records are append-only, hash-chained and signed; a correction is a new version next to the old one. Anyone can re-run the check and keep a signed checkpoint. |
| What if we leave, or you stop? | The QR codes point to your own domain. Every passport sealed in a paid period stays online for 15 years, and a signed static export lets you host the passports yourself. |
| Can it carry our volume? | Measured, not estimated: 250,000 passports registered through the normal path at 191 per second, a full chain verification in about a minute. The test and its method. |
See it on batteries like yours
Thirty minutes online: a unit registered the way your line would do it, the QR code scanned live, the sealed record verified in public.