readystack/authentik repository overview

⁠authentik (Community build)

readystack/authentik:2026.8.4-CE-ubuntu24.04-r1

A cosign-signed build of github.com/goauthentik/authentik version/2026.8.4 (MIT core; EE components stripped at build), built clean-room from official upstream source by ReadyStack⁠.

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:bcd704dddaa57823d6c9cbfd4d1b3ebc85446b9a6543336f9e9c010260eecd4f on 2026-10-20.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with ce.rodeo's published rubric) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products.html#authentik⁠
• ReadyStack release check — passed at release on 2026-10-20: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:bcd704dddaa57823d6c9cbfd4d1b3ebc85446b9a6543336f9e9c010260eecd4f; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/authentik:2026.8.4-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (1000).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 2026.8.4-CE-ubuntu24.04-r1 — the release on sale at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/authentik:2026.8.4-CE-ubuntu24.04-r1

# ✗ unsupported (do not pull)
docker pull readystack/authentik:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/authentik:2026.8.4-CE-ubuntu24.04-r1 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

ONE product container (the upstream Rust authentik binary runs ak allinone: it serves the UI/API on :9000 (HTTPS on :9443) itself, runs the embedded proxy outpost and spawns the gunicorn ASGI app plus Python task workers on a Postgres-backed dramatiq broker) PLUS one required datastore sidecar the customer provides: PostgreSQL. NO REDIS — authentik 2026.5 moved cache/channels/sessions/broker to Postgres. NOT a single self-contained image: Postgres is a hard external dependency.

docker network create authentik-net
docker run -d --name db --network authentik-net -e POSTGRES_DB=authentik -e POSTGRES_USER=authentik -e 'POSTGRES_PASSWORD=YOUR_POSTGRES_PW' -v authentik-db:/var/lib/postgresql/data postgres:16
docker run -d --name authentik --network authentik-net -p 9000:9000 -e 'AUTHENTIK_SECRET_KEY=YOUR_LONG_RANDOM_SECRET' -e AUTHENTIK_POSTGRESQL__HOST=db -e AUTHENTIK_POSTGRESQL__NAME=authentik -e AUTHENTIK_POSTGRESQL__USER=authentik -e 'AUTHENTIK_POSTGRESQL__PASSWORD=YOUR_POSTGRES_PW' -e 'AUTHENTIK_BOOTSTRAP_PASSWORD=YOUR_ADMIN_PW' -e [email protected] -v authentik-data:/data -v authentik-media:/media -v authentik-certs:/certs readystack/authentik:2026.8.4-CE-ubuntu24.04-r1

Both containers share the authentik-net network; db is the PostgreSQL container the backup and restore steps name. Use the same database password in POSTGRES_PASSWORD and AUTHENTIK_POSTGRESQL__PASSWORD, keep each -e value in single quotes, and generate AUTHENTIK_SECRET_KEY once (for example openssl rand -base64 60 | tr -d '\n') and keep it: changing it later invalidates sessions and signed data. AUTHENTIK_BOOTSTRAP_PASSWORD sets the password of the akadmin administrator on the first start. The first start migrates the database, which takes a minute or two; /-/health/ready/ answers 200 afterwards. The archive ships no Compose file.

⁠The full ReadyStack Agent-ready Archive

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is at readystack.dev/buy.html⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:a0cca3dacb2bd0316366b84e54eccf95b48e1af824f34ca70397d2e538b4e0a4 on 2026-10-20.

— ReadyStack · readystack.dev