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.
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.
Common questions
Can either one protect an app with no login of its own?
Yes. Your reverse proxy asks Authelia whether each request is allowed, and authentik has a proxy provider that does the same job, so an older app with no modern login still gets single sign-on and a second factor. Both need the app to sit behind the proxy for that to work.
Which sign-in methods does each one serve?
authentik serves OpenID Connect, SAML, LDAP, RADIUS and proxy auth, so an app that only speaks SAML or LDAP can still use it. Authelia is an OpenID Connect provider and answers forward-auth checks from your reverse proxy, and it reads its users from a YAML file or an LDAP server.
What does each one need to run?
Authelia is one Go container with SQLite for lite deployments, with PostgreSQL and Redis for production. The authentik compose file runs a server, a worker and PostgreSQL, and the project asks for two CPU cores and 2 GB of RAM.
Where do I write the sign-in rules?
Authelia holds its users, rules and storage in static YAML files, with no settings UI. authentik assembles flows and stages in its admin interface, and can export them as YAML blueprints.
Sources: Authelia docs and authentik docs.