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.

Editor

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.

Spec
PriceFree + PaidFree
LicenceMITBSD-2-Clause
Web UIYesYes
DockerYesYes
Linux package–Yes
Tech stackPythonGo
Docker Containers3 (app + PostgreSQL)1 (app only)
DatabasePostgreSQLSQLite
Minimum hardware2 cores · 2 GB RAMNot stated
Architecturex86 + ARMx86 + ARM

Common questions

Sources: authentik docs and Pocket ID docs.

Updated