License

The platform provides a flexible license mechanism. You can subscribe resources by node count or core count. Licenses support two commercial models:

• Base license: Subscribe for a fixed period (such as yearly or perpetual) to get a fixed quota of nodes or cores.
• License add-on pack: For temporary burst needs. On top of an existing base license, you can purchase node-hour or core-hour packages for elastic scaling and cost optimization.

Base license

Resource counting rules

• Core count: Counts cores across all nodes in clusters and desktops. Cores are counted based on the VM core count. The license does not look through virtualization to count physical host cores.
• Node count: Counts all nodes in clusters and desktops.

Expiration impact

When the license expires or resource usage reaches the limit, platform functionality will be restricted. To ensure normal operation, contact sales to renew before expiration.

License add-on pack

The license add-on pack extends a base license. It offsets temporary overage usage and provides a more flexible payment model.

Purchase rules

• Dependency: Must be purchased together with a base license. Cannot be purchased separately.
• Type matching: The add-on pack type must match the subscription model of the base license.

Usage characteristics

• Automatic deduction: When usage exceeds the base quota, the system deducts from the add-on pack automatically with per-second granularity.
• Stackable purchases: You can purchase multiple times within the validity period; quota accumulates.
• Expiration alignment: Expires on the same date as the bound base license.

Metering and pricing

• Units:
  • Core-hour pack: Measured in core-hours.
  • Node-hour pack: Measured in node-hours.
• Pricing logic: Add-on packs are calculated as "1.5x the lowest-tier annual subscription price".
  • Core-hour pack price = base license lowest-tier annual core-hour subscription fee (0 to 1000 core tier) x 1.5
  • Node-hour pack price = base license lowest-tier annual node-hour subscription fee (0 to 30 node tier) x 1.5

Examples

• Temporary scaling: base license 2000 cores, burst need 3000 cores for 6 hours requires 6000 core-hours add-on; base license 100 nodes, burst need 120 nodes for 8 hours requires 160 node-hours add-on.
• Real-time deduction: base license 100 cores, using 120 cores for 3 hours 25 minutes consumes 68.33 core-hours; base license 50 nodes, using 60 nodes for 4 hours 45 minutes consumes 47.5 node-hours.
• Mixed resources: base license 10 nodes + 5000 node-hours add-on; the system optimizes allocation automatically.

Import process

Separate entries are provided for updating the base license and the add-on pack.

1. Log in with an admin account and click the avatar in the top-right, then Account Settings.
2. Click Update base license or License add-on pack.
3. Upload a file or paste the license content.
4. Confirm the information and click Confirm to import.

FAQ

• Q: How are node count and core count calculated?

  • Core count: number of CPU cores.
  • Node count: all nodes that have joined clusters and desktops, including login nodes, compute nodes, and head nodes.

• Q: How are physical cores handled in virtualization oversubscription scenarios? Virtualization oversubscription means allocating more virtual resources (CPU, memory, etc.) to VMs than the physical host actually has. In this case, core count is calculated based on the VM's core count. The license does not look through virtualization to count physical host cores.

• Q: What is the advantage of add-on packs compared to base licenses? They are suitable for temporary or uncertain needs and help avoid waste from long-term idle licenses.

• Q: What happens to unused add-on quota after the base license expires? Remaining add-on quota is cleared automatically. Even if the license is reactivated later, cleared quota will not be restored.

• Q: How do I audit usage? View and analyze usage via the License usage details report.