Skip to content
Oday Bakkour
Back to Knowledge Hub

Authentik: Open-Source Identity Provider for Modern SSO

Oday Bakkour profile photo
Oday Bakkour
5 min read
Share
Authentik: Open-Source Identity Provider for Modern SSO

Authentik: Open-Source Identity Provider for Modern SSO

Authentik is a powerful open-source identity provider (IdP) designed to modernize single sign-on (SSO) across diverse environments. Whether you're managing a homelab or an enterprise-scale cluster, Authentik offers protocol flexibility, scalability, and self-hosting capabilities without vendor lock-in.

Key Features

  • Multi-Protocol Support: Native compatibility with SAML, OAuth2, OIDC, LDAP, and RADIUS.
  • Self-Hosted: Deploy anywhere from small homelabs to large Kubernetes clusters.
  • Modern Architecture: Built on Python/Django with API-first design for easy integration.
  • Scalable: Handles authentication from small setups to high-traffic enterprise applications.
  • Extensible: Customize workflows, policies, and integrations via flexible configuration.

Use Cases

  • Homelabs: Securely manage access to personal servers and services.
  • Startups: Implement cost-effective SSO for developer tools and cloud services.
  • Enterprises: Centralize authentication across complex multi-cloud environments.

Getting Started

  1. Installation: Deploy via Docker, Kubernetes, or bare-metal using official documentation.
  2. Configuration: Set up user sources, applications, and protocols via web UI or API.
  3. Integration: Connect supported services (e.g., Nextcloud, GitLab, cloud apps) using pre-built templates.

Authentik bridges legacy (LDAP) and modern (OIDC) authentication needs while offering seamless self-hosting flexibility.

Conclusion

Authentik empowers organizations to build robust, self-sovereign identity infrastructure without vendor dependencies. Its protocol support and scalability make it a compelling alternative to commercial IdPs.

--- Explore the official Authentik GitHub repository for deployment guides and community resources.

Authentik vs Keycloak vs Authelia

These three come up every time someone asks about self-hosted SSO. They overlap, but they are built for different jobs.

  • Authentik: a full identity provider with a web admin UI. It speaks OIDC, SAML, LDAP, SCIM, RADIUS, Kerberos and proxy-based access, and its OpenID Connect implementation is OpenID Certified. The open-source edition is free, and the core is MIT licensed.
  • Keycloak: a mature open-source identity and access management server and a CNCF incubation project. It supports OpenID Connect, OAuth 2.0 and SAML 2.0, federates users from existing LDAP and Active Directory servers, and has a full admin console.
  • Authelia: a 2FA and SSO authentication server that extends your reverse proxy. It works with nginx, Traefik, Caddy, Skipper, Envoy and HAProxy, is Apache 2.0 licensed and OpenID Certified for several OP profiles. Users come from a file or an LDAP backend.

Which one I would pick

If you want a single place to manage users, apps and login flows through a UI, and you need LDAP or RADIUS for older services, Authentik is the one I would start with.

If you only want a login wall and 2FA in front of a few self-hosted apps behind a reverse proxy, Authelia is smaller and simpler.

If your organisation already runs Java services or needs a long-established, standards-heavy IAM platform, Keycloak is the safe choice.

Docker Compose setup outline

The official Docker Compose guide asks for at least 2 CPU cores, 2 GB of RAM and Docker Compose v2 (Podman works too). The compose file runs three services: PostgreSQL, the authentik server and the authentik worker. Here is the flow on Linux (on macOS, use curl -O instead of wget):

bash.txt
wget https://docs.goauthentik.io/compose.yml

echo "PG_PASS=$(openssl rand -base64 36 | tr -d '\n')" >> .env
echo "AUTHENTIK_SECRET_KEY=$(openssl rand -base64 60 | tr -d '\n')" >> .env

docker compose pull
docker compose up -d

After the first start

By default authentik listens on port 9000 for HTTP and 9443 for HTTPS. To use 80 and 443, set COMPOSE_PORT_HTTP=80 and COMPOSE_PORT_HTTPS=443 in .env and run docker compose up -d again. Then open the server in your browser and follow the initial setup, which asks you to set a password for the default akadmin user.

Two things worth knowing. The worker container mounts the Docker socket so it can deploy outposts automatically, so review that if you run other sensitive containers on the same host. And keep the .env file safe: losing AUTHENTIK_SECRET_KEY or the database password makes recovery painful.

Outposts and common integrations

Some providers need an outpost, a small service that runs the provider logic and talks to authentik through its API. There are four types: Proxy, LDAP, RADIUS and RAC. The Proxy outpost is how you protect apps that have no login of their own, and the docs have guides for running it behind nginx, Traefik and Caddy.

For apps that support OIDC or SAML, the integrations catalogue has step-by-step guides. A few popular ones:

  • Nextcloud
  • Gitea and GitLab
  • Grafana
  • Proxmox VE
  • Immich and Jellyfin
  • Home Assistant
  • Vaultwarden

Pricing in 2026

The open-source edition is free and includes all the protocols above, with community support on Discord. Enterprise costs $5 per user per month, or $0.02 per external user per month, billed annually, and adds features such as Google Workspace and Microsoft Entra ID integrations, privileged access management, mTLS certificate authentication and enhanced audit logging. Enterprise Plus starts at $20k per year. The authentik team states that open-source features will not be moved into the paid tier.

When not to use Authentik

  • You have one or two apps and just need a password prompt. A reverse proxy with basic auth or Authelia is less to maintain.
  • Your server has under 2 GB of RAM to spare.
  • You already use a hosted identity provider your team is happy with, and nobody wants to own patching and backups of an SSO server.
  • You cannot keep it updated. Your identity provider is the key to every other app, so an outdated one is a real risk.

Comments

Share your thoughts and join the conversation

Leave a Comment

Loading comments...
RELATED