# On-prem (self-hosted) edition

The on-prem edition runs on the customer's own infrastructure. A license controls its member limits and gated features; retention is set
per signal by the system admin, since it's a disk-space choice. It supports local accounts, LDAP/Active Directory and OIDC providers
(Google Workspace, Microsoft Entra ID, Okta or custom), its own email and chat integrations, rate limits, and an offline vulnerability
data source.
After a contract is signed, the customer's people get a Deployments page in their powertraces.com account. There they create a
deployment (single server or cluster, connected or air-gapped), download an installer (Docker or Podman Compose, Kubernetes Helm
chart, Linux, Windows or macOS) with its SHA-256 checksum and signed build provenance, and get a one-time activation code. In the app,
System Settings > License takes the code: a connected server activates and then renews by itself; an air-gapped server downloads a
request file, the customer uploads it on the deployment's page and imports the license file it returns. Reinstalling or restoring the
same data keeps the activation; moving to other servers uses one of the contract's yearly redeploy credits.
If a license ends, the server keeps collecting and storing data and paid features lock until it renews; nothing is deleted. A grace
period (14 days connected, 30 days air-gapped by default) keeps full access after the end date. Clusters run several web nodes and
one worker with Redis and S3-compatible storage.
Sizing, pricing and contracts are handled by the sales team: collect the customer's services count, daily data volume and where it
must run, then hand off.