Skip to content
Self-hosted

Self-hosted overview

Deployment options, data boundaries and responsibilities for self-hosted Permafrost.

Test-environment key

One test key per account is available from your account page. Test keys need version 0.1.2 or later. It is valid while your production licence is valid. You are billed on the larger of your production and test installs each day, independently for human and non-human identities. A test install cannot be switched to production: use a new install to change environment. Requesting the test key again replaces its key and releases its install. Only an operator can restore an operator-revoked test key.

Run it in your environment

Permafrost is identity attack surface management. Microsoft collection is in the first release. AWS and GCP are next.

Use Docker Compose or a standard Kubernetes cluster with one Helm chart. See the support levels below. You own the database, backups and upgrades. We support the two most recent versions and ship security fixes for both.

Deployment targets

Deployment targets
Environment
Support
Docker (Compose)Tested
Standard Kubernetes (k3s 1.31, restricted Pod Security Standard)Tested
On-premises KubernetesTested on an on-premises-style k3s cluster. Other standard distributions should work.
Azure AKSInstallation tested on AKS (Kubernetes 1.36, release 0.1.2, bundled database, restricted Pod Security).
Amazon EKSPlanned, not yet tested
Google GKEPlanned, not yet tested
Docker Desktop KubernetesShould work
Other standard Kubernetes clustersShould work
OpenShiftOn request
Install with no internet connectionBy special request. Pricing may differ. Contact us.

On AKS, Microsoft sign-in, first sync, ingress, an external Azure database and workload identity have not yet been tested.

The image is published for linux/amd64 and linux/arm64; we have not yet tested the ARM (arm64) image.

Data boundary

At activation and every six hours on schedule, the install sends its licence key, install ID and app version. Scheduled checks also send human and non-human identity counts. The licensing service sees the source IP and stores a salted hash for abuse control when IP hashing is configured. Open /licence inside the install to see the check audit log, reported version and counts, result and pass expiry. It shows the key prefix, never the full key.

What leaves your network for licensing
Field
Value sent
Licence keyYour licence key
Install idThe identifier of this installation
App versionThe installed app version
Count of human identitiesThe human identity count
Count of non-human identitiesThe non-human identity count

Your identity data, findings, reports and cloud credentials stay in your environment. You create your own app registration in your own tenant. There is no third-party app with standing access to your directory.

Account and installation

Register with your company email at /self-hosted/register and verify it for one 30-day trial per company. Save the licence key when it is shown once. Your account lets you replace a key, release an install before moving it, and download the Compose file and environment example.

The image is published at registry.permafrostepm.com/permafrost/app. Use username license and the licence key as the pull password. The Helm chart is at oci://registry.permafrostepm.com/charts/permafrost. Follow the Compose steps or Kubernetes steps, then complete the five-step setup at /setup.

Start a 30-day trial

Before installation

The container image is about 1.8 GB including the PDF browser. Use Postgres 16. The app container has a 2 GB memory limit by default. Run one app replica. Allow outbound HTTPS to permafrostepm.com for licensing and to Microsoft APIs for sign-in and collection.

Installs with no internet connection are by special request. Pricing may differ. Contact us to discuss access.