License
CertAutoPilot has two tiers, and the only thing that separates them is how many certificates and distribution targets you can hold. Every feature — LDAP/Active Directory, mandatory 2FA (OTP policy), syslog/SIEM forwarding, and everything else — is available in both tiers. Activation is either online (validated against the CloudNativeWorks license API) or offline (a cryptographically signed license file verified locally, no network required). Managed at Settings → License (admin role; org-scoped).
Tiers
| Tier | Certificate limit | Distribution target limit | Features |
|---|---|---|---|
| Free (no license key) | 1 | 1 | All features |
| Enterprise (valid license) | Set by your license (unlimited if not specified) | Unlimited | All features |
Without a valid license the installation runs on Free: one certificate, distributed to one target. Any valid license makes it Enterprise; the certificate cap is carried in the license itself, so different Enterprise licenses can allow different numbers of certificates (a license with no explicit limit is treated as unlimited).
Activation
The page has an Online / Offline mode switch.
Online
- API key — enter the CloudNativeWorks license API key and save it (stored envelope-encrypted; only the last 4 characters are shown afterwards). The license-key form stays disabled until an API key is configured.
- License key — enter your license key and click Activate. The backend validates the key against
https://license-api.cloudnativeworks.comtogether with a cluster fingerprint, then registers the activation (you get an Activation ID).
Once activated, the license is re-validated when a server starts — at most once per 24-hour window across the cluster (deduplicated via the database) — and whenever you click Validate; the result is shared cluster-wide. A network failure during re-validation does not invalidate the license: valid and expires_at are left unchanged and only Last Error is updated.
Offline
For air-gapped installations. Paste the contents of your signed offline license file (JSON: {"license": {...}, "signature": "...", "public_key": "..."}) and click Activate Offline License. The signature is verified locally against an Ed25519 public key embedded in the binary at build time — no outbound connection is made. An already-expired file is rejected at upload (offline license expired on <date>).
Deactivate Offline License removes the offline license and reverts to online mode. If an online license key is still stored, it is validated at once. The action is only available while an offline license is active; on an online license the API answers 409 LICENSE_NOT_OFFLINE and changes nothing.
Status panel
The right-hand panel shows: validity badge (Valid, or the invalidity reason), mode (online/offline), plan, masked license key, cluster fingerprint, expiry, activation ID, activation time, last check time, and the last validation error if any. The Validate button in the header checks the license immediately: an online key against the license server, an offline license against its signature. It reports success only when the check actually confirmed the license, and otherwise shows why (no key, API key missing, server unreachable, license not valid).
Certificate and target usage
The Certificate Usage card shows count / limit with a progress bar (or "Unlimited certificates" on Enterprise). The count is the total number of certificate records in the installation — across all projects, regardless of status. Below it, Distribution Target Usage shows the targets that exist in the installation (all projects, all target types) against the target limit, or "Unlimited targets" on Enterprise.
Programmatic access:
GET /api/v1/license/status— validity, plan,cert_limit,target_limit, grace state (any authenticated user; used for the UI banner).GET /api/v1/license/usage—{count, limit, remaining, is_unlimited, can_create, can_renew, plan, targets: {count, limit, remaining, is_unlimited, can_create}}.
What happens at the limit
Only creating certificates is limited — existing certificates are grandfathered:
| Situation | New certificates | Renew / reissue | Scheduled renewals |
|---|---|---|---|
count < limit | allowed | allowed | run normally |
count ≥ limit (at or over the limit, e.g. after a plan downgrade or licence expiry) | blocked — 403 certificate_limit_reached | still allowed | run normally |
A certificate requested through the approval workflow is checked
twice: when the request is submitted, and again when the approved request is executed, because
several requests can be approved against the same free slot. If the cap is reached by then, the
execution fails (400 VALIDATION_ERROR) and the certificate moves to rejected — delete it and
resubmit once a slot is free or the licence is upgraded.
Deleting certificates until count < limit restores creation.
Distribution targets
On Free the installation can hold one distribution target at a time. The limit counts the targets that exist right now, so it is not a one-time allowance: deleting the target frees its slot, and a new target can then be created — of any type, in any project.
- Creating a second target is refused with 403
target_limit_reached(the response carriesmessage,plan,limitandcurrent). Cloning a target counts as creating one. In the UI, Add Target and Clone are disabled with an explanation while the slot is in use. - An operator whose target creation needs approval is refused before the request is filed; a request approved later is checked again when it runs, and fails with the same message if the slot was taken meanwhile.
- Targets that already exist keep working. After a licence expires (or a downgrade), an installation with several targets keeps deploying to all of them — only creating another target is blocked until enough have been deleted or a licence is installed.
- Editing a target, adding it to a target group or a module, and linking a certificate are not limited. Renewals, reissues, revocation and distribution are never stopped by the certificate count, so a downgrade cannot silently stop auto-renewal of the certificates you already have.
Expiry & grace period
When the license expires_at passes, a 7-day grace period begins: the license keeps working (Enterprise certificate cap intact) and the UI banner shows the remaining grace time. After the grace period the license is treated as invalid and the installation reverts to Free — the one-certificate and one-target caps apply to new certificates and new targets. All features stay available throughout; only the caps change.
See also
- Auth & RBAC — only admins manage the license; owner-level actions
- Renewal — how scheduled renewals work
- Administration overview