Licensing
anonymix validates its license fully offline — it never phones home. Here's how the trial and commercial licenses work, and what to configure.
Trial vs. commercial
To get a trial license, you have to add your email during download. The trial license is valid for 30 days. After that, you can purchase a commercial license key for continued use.
Buy a licenseActivating a key
Set the license key and deployment ID in config.yaml:
license: key: "<your-license-token>" # or key_file: "/path/to/token" deployment_id: "<your-registration-email>"
key and key_file are mutually exclusive — use whichever fits your deployment (pasting the token directly, or mounting it as a file/secret). deployment_id must match the email you used to obtain the trial or commercial key exactly, or the license is treated as invalid.
Or activate via environment variables (handy for Docker/Compose)
docker run -p 8080:8080 \ -e ANON_LICENSE__KEY="<your-license-token>" \ -e ANON_LICENSE__DEPLOYMENT_ID="<your-registration-email>" \ anonymixdev/anonymix:latest
What happens at expiry
After a trial key expires (plus a short grace period), the protected routes — /v1/anonymize* in REST mode, or the forwarding route in proxy mode — start returning 401 until a valid key is supplied. /healthz, /readyz and /metrics keep working the whole time, so the instance stays diagnosable and orchestrators don't kill a pod that's simply waiting on renewal.
During the grace window, responses carry X-License-Status: grace and X-License-Expires headers, and the same status is included in the /healthz//readyz JSON body — so you can alert on an approaching expiry before it becomes an outage.
Need a custom arrangement or an invoice? Contact us.