Solutions · Enterprise

Self-Hosted License Management

Run PermitCore on infrastructure you control — the exact same Api/Admin/Public images that run PermitCore's own SaaS, no separate self-hosted build. For teams whose compliance, procurement, or continuity requirements need the whole stack on their own side.

Why a vendor's SaaS isn't always the answer

Cloud licensing SaaS is the right default for most teams — no infrastructure to run, always up to date. But some organizations have a real requirement the SaaS model can't satisfy: data must never leave their own network, procurement requires on-prem software, or they need a documented answer to "what happens to our license validation if the vendor disappears." Self-hosting is the direct answer to that last question — there's no vendor left in the runtime path once it's running.

How it works

1. Request
Request a deployment from the admin panel (Enterprise plan). Generates a dedicated self-host license, hashed the same way customer license keys are — never stored in plaintext.
2. Provision
Download a pre-filled .env and run the provided docker-compose file. Same images, real infrastructure, on your servers.
3. Continuity
A long-lived, cryptographically signed continuity token can permanently disable the license check-in requirement — verified entirely locally, zero network calls.

What this doesn't change

Self-hosting still gets you the same validate/activate API, the same 6 SDKs, the same zero-knowledge encryption design — it's the same product, running somewhere you control instead of PermitCore's own infrastructure.

Honest scope note: self-hosting is an Enterprise-tier capability with a real provisioning step (a SuperAdmin reviews and provisions each request) — it's not a one-click download today. Automated self-service provisioning may come later; this is the current, accurate state of the feature.

Talk to us about a self-hosted deployment

Enterprise plan. Full details in the docs.