Reference
Licensing and plan behavior
Understand licence enforcement, customer portal access, and early-access plan controls.
- For
- Buyers and administrators
- Updated
- August 17, 2026
Current release behavior
Active-node and active named-user limits support UI reporting, capacity checks, create/reactivation blocking, and decommissioning behavior. Commercial deployments should install a signed licence; deployment configuration is intended for unlicensed development and explicit operator overrides.
- CONTROL_NODE_REGISTRATION_LIMIT controls enabled rnode registrations.
- CONTROL_USER_SEAT_LIMIT controls active human login accounts.
- Zero or an unset value means unlimited for these configuration-backed limits.
- Shared-inbox counts and other plan feature entitlements are not yet enforced by a licence authority.
- External token guests remain separate from named login accounts and do not consume user seats.
Upgrades and downgrades
The customer portal can create authenticated, account-scoped renewal, tier-change, and node-add-on sessions through the configured customer-account service. The service remains authoritative for ownership and eligibility. Lowering a node or user limit does not terminate running transfers or automatically delete resources; it reports over-capacity and blocks actions that would add or reactivate capacity.
Frequently asked questions
| Question | Answer |
|---|---|
| Does the product phone home? | The current configuration-backed enforcement has no activation call. Future activation behavior will be documented before release. |
| Will expiry stop an active transfer? | No expiry state exists today. The planned policy is to avoid interrupting active transfers. |
| Do Desktop workstations count as nodes? | No. Enabled rnode registrations are the currently counted node resource. |
| Do package recipients count as users? | Token-only guests do not. A normal active login account does, even if it is labelled external. |