CirculeID

About

A passport has to outlast the contract that created it

A battery sold in 2027 is still in service in 2042, and its passport still has to resolve and still has to verify. Every significant decision this company has made follows from that one sentence.

Founded
2024
Model
CIRPASS-aligned
Data residency
EU available

Definition

What does CirculeID do?

CirculeID is an enterprise Digital Product Passport platform. It gives physical products a verifiable digital identity that travels with them from raw material to end-of-life, built on GS1 Digital Link, EPCIS 2.0 and W3C Verifiable Credentials so the record satisfies EU regulation and stays portable between systems.

The company exists because the ESPR turned product data into a legal obligation with a fifteen-year tail. Building on CIRPASS-aligned standards is how we make the record outlive us.

Consequences

What the durability constraint decides

These are not values. They are the specific decisions that follow from a record having to work longer than a vendor relationship.
Design decisions and the durability reasoning behind each
DecisionThe alternativeWhy we chose it
Implement open standardsA better proprietary data modelA proprietary record stops meaning anything when we do
Resolution on your domainIdentifiers under oursA fifteen-year public artefact should not carry our hostname
Signatures verifiable without usVerification through our APIAn API call is a dependency; a signature is not
Passport data off the ledgerImmutability as a featureRegulated data must sometimes be corrected, or erased
No token, no walletA token economyIt adds a procurement obstacle and solves nothing for the buyer
Anonymous public tierAccounts and engagement mechanicsCollecting identity from a scan is a liability, not an asset

Answers

Frequently asked questions

Why does CirculeID implement standards instead of building its own model?

Because a passport must remain meaningful for the product’s service life, which can exceed the life of any vendor relationship. A record expressed in GS1 and W3C specifications can be served by another conforming resolver and verified by systems that never integrated with us. That is the only durable answer to lock-in.

What happens to our passports if CirculeID ceases to exist?

The identifiers follow GS1 Digital Link and can already resolve on your own domain. The events follow EPCIS 2.0 and the credentials follow W3C Verifiable Credentials, both verifiable without us. Export produces the same documents another conforming implementation can serve. We would rather you ask this now than discover the answer later.

Why was the company founded?

Because the ESPR (EU) 2024/1781 turned product data into a legal obligation with a fifteen-year tail, and obligations on that horizon are badly served by proprietary formats. The regulation created a market; the durability requirement determined what kind of company should serve it.

What do you refuse to build?

Anything that makes the record less portable or less honest: passport data on an immutable ledger, a token requirement, engagement mechanics that collect identity from people scanning products, and adoption figures we cannot evidence. Each of those would sell better in the short term, which is precisely why the position needs stating.

How big is CirculeID?

Smaller than the enterprises we sell to, which is worth saying plainly because it affects procurement. It also means the people who built the platform are the ones who answer when something breaks, and an architecture review happens with the person who made the decision rather than a summary of it.

Next step

Ask us the exit question first

What happens to your passports if you stop using us is the most revealing question in this category, and the one we would rather answer at the start.

Index