How to read these docs
ReadyThese docs are organized by what you are trying to do, not by feature list. There are four ways in — see it work, understand it, integrate it, or understand why it is built this way — and most pages open with a one-line TL;DR and a who this is for, so you can tell in a few seconds whether it is the page you want.
Who this is for: everyone, once. Skim this, take whichever door below fits your reason for being here, and you will not need to come back.
Where to start#
Pick the door that matches why you are here.
Bring the whole system up on your laptop and drive a real signed approval in about five minutes. Quickstart →
Two minutes on What is Ydentifi, then The ceremony for how a proof is made, and Architecture for where the pieces sit.
Add a second factor to an existing login with Integrate: step-up, or onboard end to end with Integrate: full. Then the API reference and an SDK.
The opinions behind the design, argued: On passwords, On passkeys, On devices, and Why gRPC-only.
How it is laid out#
The navigation on the left follows 8 groups, roughly from “what is this” to “every last detail”:
Reading a page#
Pages are built the same way, so you can navigate one you have never seen:
- A TL;DR at the top — the whole point in a sentence or two. If it is not what you need, you have lost ten seconds, not ten minutes.
- A who this is for line, so you can hand a page to the right person — or rule yourself out.
- An on this page list on the right, and cross-links throughout to the concepts a page assumes. Follow them; they go where you expect.
Ready means the page and the thing it describes are done. At launch means the page is written and the thing it describes opens to the public at launch. Nothing is left as a stub; a page either stands behind what it says or tells you it is not there yet.