← Directory

Pocket-ID

A simple OIDC provider that allows users to authenticate with their passkeys to your services.

  • Network Services
  • Other
  • Productivity
  • Security
  • Tools & Utilities
A simple OIDC provider that allows users to authenticate with their passkeys to your services.

Platform availability

Available on 5 of 9 platforms

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

88/100 Excellent

Maintained
100last commit 6 days ago
Popular
809,488 GitHub stars
Easy to install
755 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 7 days ago

GitHub stars
9,488
Open issues
98
Last commit
2026-10-09
Latest release
v2.18.0
License
BSD-2-Clause
Activity
rising

Checked 6 days ago - source: GitHub (pocket-id/pocket-id)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Create and save your API key An API key is a secret token that proves your app is allowed to use Pocket, so create one and save the full key shown in the response. If you do not keep it, later access steps will fail. source
  • Use the API key in requests In the Authorization header, which is the part of a web request that carries login proof, put Bearer followed by your API key. If that is missing or wrong, Pocket will reject the request. source
  • Set the MCP client to your key MCP client settings are where an app stores how it connects to external tools, so add the Pocket entry and replace the placeholder with your real API key. If you leave the placeholder, the client cannot reach Pocket. source

Fetched 17 days ago - each note links to its source

Alternatives (7)

  • Amazon Cognito
  • Authelia - Authelia is an open-source authentication and authorization server that provides login, multi-factor authentication, and single sign-on for…
  • Keycloak - Keycloak is an open-source Identity and Access Management platform for adding authentication to self-hosted applications.
  • Microsoft Entra ID - Microsoft Entra ID (formerly Azure Active Directory) is a comprehensive identity and access management cloud solution that provides a robus…
  • Okta - Okta's Workforce and Customer Identity Clouds enable secure access, authentication, and automation—putting identity at the heart of busines…
  • authentik - Authentik is an open-source identity provider that adds flexible single sign-on, user management, and common sign-in protocol support to se…
  • pomerium - Pomerium is an identity-aware reverse proxy that adds authentication and access control to internal web applications, even those without bu…

Checked 14 days ago - source: AlternativeTo

Common questions

Does Pocket ID require passwords for user authentication?

No. It only supports passkey authentication, so users can sign in without a password.

How do I point an Incus OIDC client at Pocket ID?

Copy the client ID, then set the issuer and scopes in Incus.

Answers sourced from discuss.linuxcontainers.org, github.com

Community

Collected 11 days ago - public community threads