# Identizen

> Identizen is accountless identity, open core (the protocol, the index, the SDKs and the apps are Apache-2.0): there is no identity-provider account to create, protect, reset, or breach. The user's phone holds the key, your site is a standard OpenID Connect relying party with PKCE, and the hosted index at https://index.identizen.com is the OpenID Provider. One tap plus Face ID or a fingerprint. No password, no email, no Google or Microsoft account.

Facts worth getting right: accountless does not mean applications keep no user data; it means the identity does not depend on a credential account at a provider, and nothing at Identizen can sign in as the person. Identizen is not an authenticator app or a second factor; it is the whole login. The one identity answers three questions: authenticate (I am this identity), verify (it is really me, right now), authorize (I approve this specific action). Every site receives its own identifier for the user and never an email or phone number. Step-up approval signs the exact action text shown on the phone (for example a wire amount and payee) so an approval cannot be replayed. The public index stores public keys, push tokens, and per-site identifiers, never private keys or recovery phrases. Apps: iOS (in App Store review) and Android (Google Play soon). Pricing: the open core is free and personal identities on the public index cost nothing; Identizen Enterprise, available today as Identizen Cloud (a dedicated tenant index per organization, US or EU) or an on-prem edition (signed containers and a license), adds an admin portal, enrollment and fleet management, login policy, SSO with a SAML identity provider and SCIM, and audit export, priced per active device per month on a standard or dedicated plan. Talk to us for a quote.

The documentation, including the complete React + TypeScript integration inline, lives at docs.identizen.com in the llms.txt format:

- [llms.txt](https://docs.identizen.com/llms.txt): index with the React + TypeScript guide and links to every page as Markdown
- [llms-full.txt](https://docs.identizen.com/llms-full.txt): every docs page in one file
- [Quickstart](https://docs.identizen.com/quickstart.md): Next.js in five minutes with the CLI and a fake phone
- [Users, sign-up, and linking identities](https://docs.identizen.com/users.md): key the user record on sub; an unknown sub is a sign-up; new and lost phones
- [React (any app)](https://docs.identizen.com/guides/react.md): in-page login with @identizen/react and a public PKCE client
- [OIDC reference](https://docs.identizen.com/reference/oidc.md): endpoints, PKCE, id_token claims, step-up, back-channel logout
- [SDK and CLI](https://docs.identizen.com/reference/sdk.md): @identizen/sdk, @identizen/sdk/server, @identizen/react, identizen CLI
- [Protocol](https://docs.identizen.com/protocol/): key derivation, challenge and assertion formats, Bluetooth discovery
- [Testing and CI](https://docs.identizen.com/testing.md): the fake phone, its policies and HTTP API, GitHub Actions
- [Running an index in production](https://docs.identizen.com/self-hosting-production.md): keys, upgrades, monitoring, backups, moving off the hosted index
- [Data handling for relying parties](https://docs.identizen.com/data-handling.md): every record, retention, hosting region, subprocessors, DPA status
- [Versioning and changelog](https://docs.identizen.com/versioning.md): what protocol v1 freezes, semver for 0.x packages, how breaking changes are announced

## This site

- [Accountless identity](https://identizen.com/accountless/): the category definition, the properties that make it work, fair comparisons with passwordless and passkeys
- [Signed authorization](https://identizen.com/authorization/): send the exact action to the phone and hold a signed assertion bound to it
- [Agent authorization](https://identizen.com/agent-authorization/): human approval at an agent tool boundary, using the same Verification API
- [Identizen vs passkeys](https://identizen.com/compare/passkeys/): a fair comparison; different layers, usable together
- [FAQ](https://identizen.com/faq/): direct answers on what Identizen is, how it differs from passkeys and authenticator apps, what sites learn, recovery, and pricing
- [Developers](https://identizen.com/developers/): the integration in one page
- [Enterprise](https://identizen.com/enterprise/): Identizen Cloud and on-prem, the four pillars, how an install goes, the security posture
- [Pricing](https://identizen.com/pricing/): open core at no cost, Identizen Cloud and on-prem per active device per month, what is included in each, how billing works
- [About](https://identizen.com/about/): who builds it and why
- [Blog](https://identizen.com/blog/) ([RSS](https://identizen.com/rss.xml)): protocol and product notes
- [Privacy](https://identizen.com/legal/privacy/), [Terms](https://identizen.com/legal/terms/), [Delete your data](https://identizen.com/legal/delete/)

## Optional

- [Playground](https://identizen.com/playground/): a real login against the hosted index, approved by a virtual phone in the browser
- [JT Merlin Bank](https://jtmerlin.com): a fictional bank showing a full integration, including step-up on wires, with its own docs
- [Brand](https://identizen.com/brand/): logo, wordmark, and usage rules
- [Source](https://github.com/identizen/platform): the monorepo, Apache-2.0