VaultPilot license verification works offline: the server checks each license code with public verification material. Issuer-side private signing material is never installed on customer servers.
Normal lifecycle
| Stage | Operator view | Action |
|---|---|---|
| Trial | VaultPilot runs with trial limits and an expiry date. | Validate the deployment, backup flow, HTTPS and owner access before production use. |
| Active license | License page shows plan, capacity, expiry, signature status and enabled modules. | Review capacity and expiry during monthly operations. |
| Renewal window | Expiry is close enough to plan replacement. | Request the next offline license code privately from support@vaultpilot.io. |
| Replacement | A new code is pasted into the License screen. | Confirm signature verification, capacity, expiry and module availability. |
| Expired or over capacity | VaultPilot can restrict writes while keeping safe read and backup-export paths available. | Reduce usage, apply a valid license, or work with support before adding users or enabling new workflows. |
Read-only behavior
When trial or license time expires, VaultPilot can keep login, secret viewing, audit review and backup export available while blocking writes, user creation, sharing, extension pairing and update install actions. This keeps operators from losing access to encrypted data while preventing unlicensed expansion.
What to record
- License state, plan and expiry date.
- Active user count and capacity.
- Signature verification status.
- Modules that are enabled or unavailable.
- Date and approver for replacement.
Do not put license codes or screenshots with real user data into tickets, chat or shared documents.