authentik vs Pocket ID
Editor take
Choose authentik for a proxy in front of apps without OIDC, and for SAML and LDAP apps. Choose Pocket ID for one container on SQLite and for passkey sign-in.
Where they differ
Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.
authentik
Where authentik is stronger
- A proxy for apps without OIDCThe proxy provider sits in front of an app with no native login and asks authentik about each request; Pocket ID returns OIDC tokens, so a proxy has to sit in front of those apps.1
- SAML, LDAP and RADIUS providersApps that speak SAML, LDAP or RADIUS can use it directly; Pocket ID is an OpenID Connect and OAuth 2.0 provider, so those apps need a proxy in front.2
Pocket ID
Where Pocket ID is stronger
- One container on SQLiteA single binary or container with its own SQLite file, so no database server beside it; the authentik compose file runs a server, a worker and PostgreSQL.3
- Passkey sign-in, no password storeA passkey unlocks each account, with a one-time login code when someone enrols a device; authentik also keeps passwords.4
authentik vs Pocket ID: specs side by side
Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.
Common questions
Can Pocket ID and authentik sign in to apps without OpenID Connect?
authentik can: its proxy provider puts it in front of an app with no native login, and it also serves SAML and LDAP. Pocket ID needs a separate authentication proxy in front of any app that does not speak OpenID Connect.
What do Pocket ID and authentik need to run?
Pocket ID is a single Go container with SQLite, served over HTTPS because browsers only allow passkeys there. authentik runs a server, a worker and PostgreSQL, and the project asks for two CPU cores and 2 GB of RAM.
Can Pocket ID and authentik limit who opens each app?
Yes. Pocket ID returns a token only when the passkey checks out and, if the app is limited to groups, the user is in one. authentik sets its sign-in rules in a flow editor, where stages and policies decide who may continue.
Sources: authentik docs and Pocket ID docs.