Does Pocket ID support passwords or TOTP?
No. Pocket ID signs users in with passkeys; an admin can also send a one-time login code so someone adds a first passkey or gets back in after losing them.
One passkey can sign you into the apps you connect through OpenID Connect, with Pocket ID as the provider behind the login. Each app sends its users to it, and it returns a token once the passkey checks out and any group restriction is met.
Compare Pocket ID with other security apps. Add or remove apps to see how they differ.
| Requirement | Pocket ID | ||
|---|---|---|---|
| Price | Free | Free | Free + Paid |
| Licence | BSD-2-Clause | Apache-2.0 | MIT |
| Web UI | Yes | Yes | Yes |
| Minimum hardware | Not stated | Not stated | 2 cores · 2 GB RAM |
| Docker Containers | 1 (app only) | 1 (app only) | 3 (app + PostgreSQL) |
| Database | SQLite | SQLite | PostgreSQL |
| Architecture | x86 + ARM | x86 + ARM | x86 + ARM |
| Tech stack | Go | Go | Python |
| Docker | Yes | Yes | Yes |
| Linux package | Yes | Yes | – |
Compare | |||
| Full comparison | This app | Authelia vs Pocket ID | authentik vs Pocket ID |
No. Pocket ID signs users in with passkeys; an admin can also send a one-time login code so someone adds a first passkey or gets back in after losing them.
Yes for real use. Browsers only allow passkeys on HTTPS pages, so put Pocket ID behind a reverse proxy at something like id.example.com. Localhost is the exception while you try it out.
Only through an authentication proxy. Apps that speak LDAP or SAML, or nothing at all, need a proxy service in front of them that asks Pocket ID.
Put a single login and a second factor in front of your self-hosted apps: your reverse proxy asks Authelia whether each request is allowed. Rules match by domain, user, group or network, and the portal handles passwords, WebAuthn keys and TOTP.
One login in front of every app you host, from an identity provider that speaks OIDC, SAML, LDAP and proxy auth. One account and a second factor then open Jellyfin, Nextcloud and the rest of the stack.
Put one login in front of a dashboard of your self-hosted apps, and show each person only the tiles they should see. Accounts come from local users, LDAP, OIDC or your reverse proxy. New containers found in Docker, Traefik, Nginx or Unraid wait in a list for you to publish.
Tinyauth puts one login screen in front of the apps on your network. It checks the session for Traefik, Caddy or Nginx and signs people in from users you define, an LDAP server or an OAuth provider, and it also serves OpenID Connect for apps that support it.
Apps such as Nextcloud, Jellyfin and Grafana authenticate against LDAP, and LLDAP gives them a small directory server with a web page for users, groups and passwords. The data sits in SQLite unless you point it at PostgreSQL or MariaDB, and Authelia or authentik can use it as the user source.
Scan files on your server for viruses, trojans and other malware with an antivirus daemon, while freshclam keeps the signature database current. A mail gateway can feed it mail to scan, and a file server can run clamscan on the host. Once its socket is shared, other services on the box can call clamd too.
Browse YouTube without ads or tracking through a front-end you host. Subscriptions, playlists and watch history live in your own database, and the player works with JavaScript turned off.
Run a private metasearch instance on your own server that pulls results from many search services.