Pocket ID review
A focused, open-source identity provider for passkey-only OIDC sign-in on self-hosted services.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Pocket ID is a self-hosted OpenID Connect and OAuth 2.0 identity provider for people securing self-hosted services, custom applications, and APIs. Its defining choice is passkey-only passwordless sign-in for connected OIDC applications. The project is open source and offers a free plan, making it a focused option for solo developers and small teams willing to operate their own identity service. It can be installed with Docker or as a standalone binary, and supports sign-in with a passkey on the current device or approval from another device. Administrator-generated login codes support setup and recovery.
Its feature set extends beyond sign-in into identity administration. Administrators can manage users and groups, synchronize both from LDAP, and use group-based access control for applications. SCIM provisioning and deprovisioning is available for connected applications, while an administrative REST API provides another way to work with the service. Global and per-user audit logs add visibility into activity. This combination suits environments that already depend on self-hosted infrastructure and want directory synchronization and application provisioning alongside passkeys. Pocket ID is narrower than an identity platform intended to support varied authentication approaches: its sign-in model is explicitly passkey-only.
The main trade-off is operational ownership. A self-hosted deployment gives the operator responsibility for installation and ongoing operation, rather than relying on a hosted service. Support channels are documentation and community, so teams seeking vendor support or a managed deployment may prefer another option. Pocket ID is a good fit when passkeys are the required sign-in method and OIDC, LDAP, SCIM, and audit capabilities match the surrounding environment. It is less suitable for organizations that need hosted identity management or a broader authentication approach.
Pocket ID pros and cons
- Where it wins
- Passkey-only sign-in for OIDC applications, including QR approval from another device
- LDAP sync, SCIM provisioning, and group-based application access control
- Global and per-user audit logs plus an administrative REST API
- Where it doesn't
- Requires self-hosting rather than a hosted deployment
- Focused on passkey-only sign-in rather than broader authentication methods
- Support is through documentation and community
Pocket ID fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update