Operations
Deployment and operations
Authkits stays inside your Django deployment. The host remains responsible for TLS, secrets, database security and backups, email infrastructure, monitoring, authorization, and the surrounding production environment.
Activate the release build
Use the Authkits license key only for explicit activation. Persist the returned signed entitlement somewhere appropriate for your deployment.
AUTHKITS_LICENSE_KEY=AK_PRO_...AUTHKITS_ENTITLEMENT_FILE=/run/secrets/authkits-entitlement.jwspython manage.py authkits_activateDatabase support
Authkits uses Django-portable database primitives. The v1 test matrix covers SQLite, PostgreSQL 16, and MySQL 8.4. Your project still owns database routing, backups, replication, pooling, and operational tuning.
Redis is not a base requirement for Authkits rate limits, challenges, sessions, or security state.
Migrate and collect static assets
python manage.py migratepython manage.py collectstatic --noinputRun production diagnostics
python manage.py check --deploypython manage.py authkits_check --securitypython manage.py authkits_prune --dry-runauthkits_check --security is read-only. It reviews CSRF, cookie posture, password hashing, MFA readiness, proof lifetimes, session tracking, trusted proxies, migrations, and audit persistence.
Schedule transient-state pruning
Run python manage.py authkits_prune from cron, a systemd timer, Kubernetes CronJob, platform scheduler, or your existing task system. Authkits does not require Celery.
Pruning removes eligible expired/revoked transient security rows. It does not prune append-oriented audit history or active credentials, sessions, devices, MFA state, or host-owned data.
Check for updates explicitly
python manage.py authkits_checkUpdate discovery is an operator action. It does not run during login or ordinary requests.
Licensing behavior
Normal authentication verifies local entitlement state and remains independent of Authkits.com availability.
Licensing and activation