Licensing
ProxCenter ships in two editions, and licensing is managed from Settings > License by a provider administrator.
Editions
| Edition | Description |
|---|---|
| Community | Free, with a limited feature set. No license key required. |
| Enterprise | Licensed. Unlocks advanced automation, security, reporting, and MSP / IaaS capabilities. |
The License tab shows your current edition, who the license is issued to, the node quota, and the expiry date.
Activating a license
- Go to Settings > License.
- Click Activate Enterprise License.
- Paste your license key and confirm.
The license defines a node quota, that is, how many Proxmox nodes the install may manage (some licenses are unlimited). You can deactivate a license from the same screen.
Node quota and enforcement
Enforcement is based on the total number of nodes across your managed clusters against your licensed capacity. If you exceed the capacity, the install switches to read-only until you are within the limit again. Read operations and visibility are never blocked.
Stacking multiple licenses
A single ProxCenter install can carry more than one license at once. This is useful in two situations:
- Central NOC aggregation -- A central install supervises several remote sites that are already licensed locally. Stacking lets each site keep its own license without being counted twice against a single quota.
- Capacity expansion -- Instead of regenerating a larger license when you add nodes, you import a supplemental license. The fleet quota grows by the additional nodes, the original license is untouched, and the supplement lapses on its own expiry.
Importing an additional license
- In Settings > License, click Import a license.
- Paste the additional license key under License key.
- Optionally map it to a cluster under Map to a cluster (optional), or leave it as Floating (no cluster).
- Click Import.
A floating license contributes to your capacity whenever it is active. A cluster-mapped license contributes while it is mapped to a cluster.
Fleet capacity
With stacking, the License tab shows a Fleet capacity summary: the sum of all active licenses, compared against the total number of nodes. The install stays within capacity as long as that total does not exceed the sum, and switches to read-only beyond it.
Editing a mapping
Use Edit mapping on a license to select the clusters it covers. A cluster already covered by another license is disabled in the picker, so a cluster is never double-counted.
Removing an imported license
Use Remove on an imported license. The nodes it covered fall back under the primary license quota.
Per-tenant attribution
In an MSP deployment, the License tab shows a Per tenant breakdown: license coverage attributed to each customer tenant, with the Licensed to name (the customer's company, or their name).
Attribution is derived, not configured directly. A license is mapped to a connection (a cluster), and that connection is owned by a tenant, so coverage flows from the license to the connection to the owning tenant. There is no direct license-to-tenant link to maintain. The per-tenant view is for visibility and reseller billing; enforcement remains based on the fleet total.
Licensing, license stacking, and the per-tenant rollup are Enterprise capabilities, managed by provider administrators.
Permissions
| Permission | Description |
|---|---|
super_admin | Full access to license management |
admin.settings | Required to manage the license and imports |
License management is provider-only: it is performed from the provider tenant.