For Manufacturers & Producers
Issue battery passports — with the engine we use ourselves
From 18 February 2027, the digital battery passport is mandatory for EV batteries over 2 kWh. The DPP Engine covers the whole path: deliver data, pass two gates, publish the passport — with a version history nobody can rewrite after the fact.
The path to your first passport
Four steps, none of them hidden
01
Account & identifier
A tenant with an operator identifier (GLN) and an API key. Ingest, write, and publish are separate permissions.
02
Deliver data without rebuilding everything
Three paths are open, depending on what you already have — see below.
03
Two gates before a passport goes live
Completeness against the mandatory fields due for your category, and a provenance check — estimated or AI-extracted values alone aren't enough.
04
After that: versions, not overwrites
Every change creates a new, hash-chained version — traceable for anyone with access, forwards and backwards.
Three paths, one engine
Connect however fits your systems
ERP integration
Batch import with a dry run — see what passes and what the gate stops before anything goes live.
Studio
A web interface for manual work — create individual passports, fill in fields, grant approvals.
MCP server
For agent workflows and automation — the same engine, addressed machine-to-machine.
Before you decide
What the engine does, not what we claim
Two pages show it with real data from our own pilot.
✦ Next step
Ready for your first passport?
Write to us — we'll tell you how fast it can go for your battery category.
Get in touch