Preview · wellknown.id is in development and isn’t live yet

An identity that is yours

Identity you hold, recognised where you choose.

A key made on your own device. Sites, venues and the people you trust recognise it; nobody issues it, and nothing about you is kept anywhere but with you.

Holder / Titulaire
Issued by / Émis par
You
Authority / Autorité
None required
Password / Mot de passe
None, ever
Valid / Valide
While you hold the key

More than signing in

One key. A patchwork of uses.

Signing in is the first patch. The same key can prove your age at a door, stand with others in a shared identity, and carry the memberships you choose to show. Pick a patch to read more.

How it works

A key, a proof, a recognition.

No accounts and no passwords: just cryptography your browser already speaks, and standards sites already use.

01 · YOUR KEY

Made on your device

The first time you use wellknown.id, your browser makes a key that can never be copied out. Its public half is your identifier.

02 · A PROOF

Signed, just now

To sign in, your browser signs a one-time challenge for that one site. It proves you hold the key without revealing it.

03 · RECOGNISED

Where you choose

Sites publish who they are on their own domain, so there’s no registration with anyone, and they recognise you by your key.

The full story

For developers

Two files and a script tag.

Publish your site’s public key at /.well-known/id, add the button, and receive a verified OpenID Connect ID token. No client registration, no secrets to rotate.

Integration guide
<!-- your page -->
<wellknown-id-button></wellknown-id-button>
<script src="https://wellknown.id/sdk/web.js?clientId=…" defer></script>

window.addEventListener('wellknown-id-login-success', (e) => {
  const { sub, id_token } = e.detail; // sub is the user's did:key
});

Roadmap

What’s sewn in, and what’s next.

An honest account of where each piece stands.