Licensing
Mildport licensing is offline. Signed EdDSA keys are verified against a public key you deploy with the engine — there is no license server and nothing phones home, so it works in air-gapped environments.
How it works
Section titled “How it works”- You hold a signing key pair (issued with your license).
- The engine is configured with the public key.
- Each tenant gets a signed key that the engine verifies locally on every request.
A key encodes its tenant, plan and entitlements, so a single deployment can serve many tenants with different limits.
Issue a tenant key
Section titled “Issue a tenant key”pnpm import:license -- --tenant acme --plan pro# ✔ signed key minted — verifies offlineHand the minted key to the embedding host; it goes in the widget’s license-key attribute
(see Configure).
Revocation & entitlements
Section titled “Revocation & entitlements”- Revocation lists — invalidate a key without re-deploying the public key.
- Per-plan entitlements — features and limits travel inside the signed key.
- Preflight —
pnpm import:config-checkvalidates your key and entitlements before the engine accepts traffic.