Activation limits

Understand per-license seats, total active device capacity, and same-device reactivation.

Seats and total active device capacity

A per-license seat limit controls one key. Your account cap covers occupied seats across every key: Free 50, Starter 1,000, Professional 10,000, Enterprise unlimited. Active top-ups add capacity. Creating keys does not use seats.

ActionOccupied seats
Validate a keyNo change; normal license and API rate limits apply
Activate a new deviceUses one seat on the key and account
Same-device node-locked reactivationReuses its primary seat, even above the account cap
Repeated count-based activationUses another seat each time
Test, revoked, expired and imported keysTheir occupied seats count
Renewal or plan changeNo reset; all occupied seats remain counted
Confirmed device removal or key reset/transferReleases the removed occupied seats

Application flow

Activate a new installation with a stable device ID. On later launches validate its license; do not repeatedly register count-based licenses. A local activation flag is not proof of validity. A changed device ID may use a new seat. The same device on two keys occupies a seat on each key. See the team license guide for customer seat packs and device reassignment.

When a limit is reached

New activation returns HTTP 200 with isValid: false and ActiveDeviceLimitReached when the account cap is full. SeatsExhausted still means the particular key is full. PoolExhausted is deprecated and no longer returned. All eight SDKs preserve the new code.

After a downgrade or top-up expiry, existing devices retain normal validation and entitlement rules. Only new activations are blocked until capacity is available. There is no monthly reset. Revoking a key, letting it expire or marking it as test does not free capacity. Remove a device or reset/transfer the key to release its seats. Already issued offline proofs remain valid only until their signed deadline.

The client message is: This software's license server has reached its active device limit. Ask the vendor to free a device or upgrade. Every account-cap rejection records an ActivationFailed audit with errorCode and reason. The owning tenant can see this fixed reason in Activity where its plan and permissions allow access; other detailed audit changes remain restricted. Vendors with a subscribed webhook receive tenant.device_limit_reached, throttled to once per tenant per five minutes. Notification failures do not change activation refusal.

Read your usage

Billing and the Dashboard show the same account usage. The license list shows per-key currentActivations / maxActivations. A 1,000-seat cap can support roughly 1,000 one-device customers or 500 two-device customers in total, rather than that many new customers every month.

Capacity and subscription validity are separate. Existing vendor subscription lapse, warning, grace and license expiry rules still apply. Review pricing and Billing for your plan and active top-ups.