Licensing
VIN uses online, signed licenses. Each key is signed with the vendor's Ed25519 key and validated against the vendor portal. Licensing is online-only for every deployment, including on-prem: your install must be able to reach the portal.
What a license controls
- Edition — Community, Professional, or Enterprise (feature set)
- Seats — maximum active users on the install
- Environments — in-instance team isolation (Professional: 3; Enterprise: unlimited). Community does not include environments.
- Machines — how many installs the license covers
- Expiry — subscription term (perpetual licenses do not expire)
Editions at a glance
| Edition | Seats | Environments | Notes |
|---|---|---|---|
| Community | 3 | — | Core ops; self-serve free term |
| Professional | 25 | 3 | Automation, Cloud Hub, FinOps, approvals |
| Enterprise | unlimited | unlimited | Site licensing + priority support |
Activation
- Copy the signed key from your portal dashboard.
- In VIN, open License, paste the key, and save.
- VIN confirms the license online with the vendor portal.
Activation requires portal reachability. There is no offline / air-gapped licensing mode.
Online validation
While VIN is running, it periodically re-checks the license with the portal so edition limits stay accurate and revoked keys stop working. Seat, environment, and machine limits are enforced against your organization's entitlement on the portal.
Secrets & backups (product)
These apply to the self-hosted VIN install, not the public portal:
- At rest — cloud credentials and SSH keys use Fernet (AES-128-CBC + HMAC) by default, scoped per user and environment.
- Built-in Vault — optional HashiCorp Vault service shipped with VIN; enable from Backup / Secrets settings to store SSH keys and cloud secret fields in KV v2.
- Backups — export as passphrase-protected
.vinbak(PBKDF2-HMAC-SHA256 + AES-256-GCM). Legacy zip restores still work with a warning.