Skip to main content

Full development environment

Prerequisites

Before you begin, ensure you have the following tools installed. You can run the provided script below in Installing platform-specific dependencies to install these required tools.

Understanding the architecture

authentik is primarily a Django application running under gunicorn, proxied by a Go application that serves static files. Most functions and classes have type hints and docstrings. For better code navigation, we recommend installing a Python type-checking extension in your IDE.

1. Prepare your local working repository

Verify that you have a local working repository of authentik and that it is initialized and up-to-date with the authentik repository.

Unless otherwise specified, all commands described below should be run from the project root of your local authentik repository.

2. Set up required services

authentik depends on several external services:

The easiest way to set up these services is using the provided Docker Compose configuration:

docker compose -f scripts/docker-compose.yml up -d

3. Installing platform-specific dependencies

Install the required native dependencies on macOS using Homebrew. You can edit the following command if you already have some of these and want to skip installing them again, or run brew install --dry-run to preview the changes:

brew install \
libxmlsec1 \
libpq \
pkg-config \
uv \
postgresql \
node@24 \
golangci-lint \
krb5

4. Set up the backend

info

All make commands must be executed from the root directory of your local authentik Git repository.

Install dependencies

Install all required JavaScript and Python dependencies and create an isolated Python environment:

make install

Generate development configuration

Create a local configuration file that uses the local databases for development:

make gen-dev-config

Initialize the database

Run all migrations with the following command:

make migrate
info

If you ever want to start over, use make dev-reset which drops and restores the authentik PostgreSQL database to the state after make migrate.

5. Running authentik

Now that the backend has been set up and built, you can start authentik. In two different tabs in your terminal, run the following commands from the root of your installation directory:

make run-server
make run-worker
info

The very first time a worker runs, it might need some time to clear the initial task queue. Adjust AUTHENTIK_WORKER__THREADS as required.

Both processes need to run to get a fully functioning authentik development environment.

Initial setup

To set a password for the default admin user (akadmin):

  1. Navigate to http://localhost:9000/if/flow/initial-setup/ in your browser.
  2. Follow the prompts to set up your admin account.

From now on, you can now access authentik at http://localhost:9000 using the credentials you defined in Step 2.

6. Build the frontend

Even if you're not planning to develop the UI, you need to build the frontend because no compiled bundle is included by default. Run the following command to build the authentik UI:

make web-build

For real-time feedback you can view the UI as you make changes. Run this command and then in your browser go to http://localhost:9000/.

make web-watch

Hot-reloading

When AUTHENTIK_DEBUG is set to true (the default for the development environment), the authentik server automatically reloads whenever changes are made to the code. However, due to instabilities in the reloading process of the worker, that behavior is turned off for the worker. You can enable code reloading in the worker by manually running uv run ak worker --watch.

End-to-End (E2E) Setup

Start the E2E test services with the following command:

docker compose -f tests/e2e/docker-compose.yml up -d

You can then view the Selenium Chrome browser via http://localhost:7900/ using the password: secret.

Alternatively, you can connect directly via VNC on port 5900 using the password: secret.

info

When using Docker Desktop, host networking needs to be enabled via Docker Settings > Resources > Network > Enable host networking.

Contributing code

Before submitting a pull request

Ensure your code meets our quality standards by running:

  1. Code linting:

    make lint-fix
    make lint
  2. Generate updated API documentation:

    make gen
  3. Format frontend code:

    make web
  4. Run tests:

    make test

You can run all these checks at once with:

make all

Submitting your changes

After your code passes all checks, submit a pull request on GitHub. Be sure to:

  • Provide a clear description of your changes
  • Reference any related issues
  • Update any related documentation
  • Follow our code and documentation style guidelines
  • Include tests for your changes where appropriate

Thank you for contributing to authentik!