Commercial
Licensing and activation
Authkits Django uses explicit activation and a signed local entitlement so commercial ownership can be verified without turning Authkits.com into an authentication runtime dependency.
Explicit activation
The license key is used only when an operator deliberately activates an installation.
Signed offline proof
Authkits.com returns a compact Ed25519-signed entitlement that the package verifies locally.
No runtime phone-home
Login, signup, MFA, recovery, sessions, and ordinary requests do not depend on Authkits.com.
Activate an installation
AUTHKITS_LICENSE_KEY=AK_PRO_...AUTHKITS_ENTITLEMENT_FILE=/run/secrets/authkits-entitlement.jwspython manage.py authkits_activateActivation sends the commercial license key and the fixed django-authentication product identifier to Authkits.com. The command verifies the returned signed entitlement locally before atomically replacing the configured entitlement file.
Local verification
The package accepts a configured entitlement string or entitlement file. It verifies the protected key ID, Ed25519 signature, v1 payload format, Django product, and production_use capability locally.
Reliability-first licensing
A successful self-hosted entitlement has no mandatory short runtime expiry. Authkits.com remains authoritative for future activations, downloads, and updates, while an already activated deployment keeps authenticating locally if the Authkits service is unavailable.
Key rotation
Released wheels contain trusted public verification keys only. New public keys ship before Authkits.com begins signing with the matching private key, and older public keys can remain trusted for previously issued entitlements.
Production validation
Run Authkits' deployment and security checks after activation.
Deployment and operations