Authelia vs authentik

Editor take

Choose Authelia for one container on SQLite and for configuration you keep as files. Choose authentik for SAML, LDAP and proxy providers, and for sign-in flows built in its admin UI.

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.

Authelia

Where Authelia is stronger

  • One container on SQLiteSQLite suits lite deployments and rules out more than one instance; authentik runs a server, a worker and PostgreSQL, and asks for 2 cores and 2 GB of RAM.1
  • Configuration you keep as filesUsers, rules and storage live in static YAML you can copy, diff and back up; authentik builds its sign-in as flows and stages in an admin interface.2

authentik

Where authentik is stronger

  • SAML, LDAP and proxy providersServes SAML, LDAP and RADIUS, plus a proxy provider that puts it in front of apps with no login; Authelia offers OpenID Connect and forward auth.3
  • Sign-in flows built in a web UIThe admin interface assembles sign-in, enrolment and recovery flows from stages and policies; Authelia keeps its rules and user backends in YAML files instead.4

Authelia vs authentik: 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
PriceFreeFree + Paid
LicenceApache-2.0MIT
Web UIYesYes
DockerYesYes
Linux packageYes–
Tech stackGoPython
Docker Containers1 (app only)3 (app + PostgreSQL)
DatabaseSQLitePostgreSQL
Minimum hardwareNot stated2 cores · 2 GB RAM
Architecturex86 + ARMx86 + ARM

Common questions

Sources: Authelia docs and authentik docs.

Updated