Passports outlive
the companies
that make them.
A battery sold in 2027 is still on the road in 2037. Its passport has to answer for all of it — including after the brand, the importer, or the supplier is gone.
A copy is only half the answer.
Most of this market talks about the data. The failure that actually strands consumers is the address.
The content path
Machines look up an identifier, then an endpoint, then the data. If the data holder disappears, that chain ends nowhere. A second holder fixes it.
The consumer path
A person scans the code on the product. That address is printed into packaging that already shipped. If the domain stops resolving, no copy anywhere can be reached.
So we treat the address as a compliance asset, not an IT expense: longest available registration, custody and succession arranged, renewal on the same obligations list as the archive.
A second copy that answers.
Not a cold archive. A live holder that answers the way we do.
The whole history
Current state and every archived version, retrievable by date from the backup too.
The same access rules
Same entitlements per audience. Continuity must not become a side door.
Per unit, not per model
Item records travel too, or a second-hand buyer's own unit becomes unrecognisable.
Inside the same region
Chinese backups stay in China, EU backups in the EU. Continuity is never an export.
Separated infrastructure
Different provider and site — the realistic single point of failure is an account.
Nothing else
The holder stores and discloses. It does not analyse, enrich or trade the data.
And if Authentag stops?
Fair question, and the honest answer is that the mechanism exists precisely because no provider should be a single point of failure — including us.
The second copy sits on separate infrastructure. Signing keys are published, so sealed passports verify without us, and anchors sit on a public chain we do not control.
Identifiers are not locked to our brand. They can be re-pointed to another provider — portability we treat as a feature to be tested, not a threat to be quietly prevented.
Entities, hosting and current status →We can be your backup.
If you already run a passport platform, you still need somebody independent holding the second copy — and it cannot be another instance of your own stack.
We provide that as a standalone service: receive replication, hold the archive, serve the same read requests under the same rules, in your region. No competition for your customer relationship; we never see the commercial side of it.
Talk about backup provision →