Your own issuer.
Your own domain.
In an hour. That is the target we are building toward. And you can fire us afterwards without losing anything you built. IN BUILD · P1
Three steps. Your name on every one.
IN BUILD · P1You issue under your own domain, your own brand — we are plumbing, not the landlord.
Your issuer lives at id.yourcompany.com, not somewhere on ours. Your name is on the documents. Your customers see you.
And the exit is part of the offer: delete the one DNS record that points at us and we are fired. The issuer identity stays yours, because it was never ours. Vendors who hold your identity hostage are the industry norm. That norm is the thing we are selling against.
The hour is a target, not a measurement. The register row stays IN BUILD until a timed, end-to-end run is published there. Read the row.
- One TXT record proves the domain is yours.
- One CNAME points id.yourcompany.com at us.
- You issue, under your own name. Delete the CNAME any day and keep everything.
See your name on it.
IN BUILD · P1Type your company's name. Watch a document render under your own domain.
A drawing in your browser, marked as one. The real path is the three-step ladder above, and it is not finished, which is why every tag in this section says IN BUILD.
You are not early. The deadlines already exist.
LIVEAge checks are fined today. Phone-based identity is EU law with dates attached.
| When | The law | Where our build stands |
|---|---|---|
| Now | Age-check duties are in force and being fined, in the UK today, with several US states legislating the same direction. | The one-answer age check is the first product. IN BUILD · P1 |
| Dec 2026 | Every EU member state must offer people a phone-based identity they control. | Your own branded issuer on the same rails. IN BUILD · P1 |
| 2027 | EU businesses in regulated sectors must accept that identity, and new anti-money-laundering rules land the same year. | The accepting side, built for you. PLANNED |
The dates are facts about law. That is all the LIVE tag above covers. The tag in each row says where our own build actually stands, and none of those says LIVE. How we separate the two.
Checking a proof will be free. Forever.
PLANNEDNot a promotion. A consequence of the shape of the thing.
Checking a proof from you means reading a few small signed files served from a content network: the cost of serving a file, fractions of nothing. Vendors who charge per check are charging margin on that, not cost.
Free checking is also why the fabric grows: anyone can accept proofs from your customers without asking us, paying us, or telling us.
This is an intention we have not signed. The register row says exactly that, and prices appear only when the owner signs them. Read the row.
The side that checks must never need our permission.
The shortest data agreement your lawyers will read this year.
LIVEIt is short because there is almost nothing to process.
Data-processing agreements are long when the vendor holds a copy of everyone's private life. We hold no names, no birthdays, no photos, no addresses. That is the LIVE row, checked against our own database declaration. So the processing annex is nearly empty, the subcontractor chain for personal data is nearly empty, and the breach clause collapses, because a breach of us is a breach of almost nothing.
Your procurement reads it in minutes. Competitors who store what we refuse to store cannot copy the clause: their architecture writes their annex for them.
What is LIVE here is the architecture that keeps the agreement short. See how we checked it. The agreement itself is drafted per deal and signed by the owner; there is no template to download yet.
What each of your people will ask.
Four chairs at your table, one honest answer each.
Your security lead: "What does a breach of you cost us?"
LIVEAlmost nothing. There is no pile of your customers' personal data here to steal: no names, no birthdays, no photos, no keys. What cannot be stolen also cannot be demanded or leaked.
The proof behind it
Your security lead, again: "Where do the keys live?"
IN BUILD · P1On your customers' phones, born inside the secure chip, never exportable. Custody is an operation we cannot perform — not a policy we promise.
The proof behind it
Your compliance officer: "What do audits look like?"
PLANNEDMachinery, not binders: a subject-access desk, erasure with proof of coverage, scheduled retention purges, a breach register — planned as running, tested code whose evidence is a query, not an archaeology project.
The proof behind it
Your CTO: "What breaks when you upgrade — or vanish?"
PLANNEDNothing, by two designs: a new engine ships only when the old interface's own tests pass against it, so your integration cuts over unchanged. And checking proofs runs on signed static files, so an outage of us does not stop your checks.
The proof behind it
Your product owner: "What do my users get out of it?"
PLANNEDSign-up without a form, proof without a document upload, and a phone they can lose without losing anything: the moments that make people stop abandoning your flows.
The proof behind it
Pricing
PLANNEDThere is no pricing table here — on purpose.
Published when signed. Not before.
Prices appear on this site when the owner signs them. Tiers invented to make a webpage look finished would be the first dishonest numbers on this site, and the register is built to keep them off it.
Two things are already decided in direction: issuing under your brand is what you pay for, and checking proofs is meant to be free, forever.
When you're ready.
-
Get early access.
First tenants shape the issuing path, and get the timed one-hour run done on their domain.
Get early access → -
Send your engineers ahead.
The integration is one paste; the protocol names live on their page, not this one.
See the developer path → -
Or audit us first.
Every claim on this page resolves to the public register, including the ones we marked against ourselves.
Open the register →