Request a Demo

Multi Use License Specification

MULTI USE LICENSE TERMS & CONDITIONS

The below Cloudamize Platform capabilities and limits are enforced specifically for Customers who purchase the Cloudamize MULTI USE license. Where not specified, all usage capabilities and limits are as defined within the relevant Order Form1.

  • Unless otherwise defined within the Order Form1, the standard Cloudamize online Terms & Conditions apply to the use of MULTI USE licenses.
  • The MULTI USE license term shall commence upon signature of the Order Form1.
  • A MULTI USE license entitle users to 12 months of access to the Cloudamize Platform to utilize the following platform components on a per-Engagement6 basis;
  • The MULTI USE license grants license holder the ability to conduct multiple data collections & analyses, starting at any period within the contract term2
  • MULTI USE licenses limits are set based on the Engagement6 term and total number of Node-Months5 purchased, with the total Node-Months5 consumed not to exceed the total number of Node-Months5 purchased.
  • The consumption of MULTI USE Node-Months5 is based on the the creation date, expiration date, and the number of nodes3 assessed on individual Engagements6 within the contract term2.
  • The MULTI USE license holder will retain access to Engagement6 data until the Engagement Expiration Date9.  All data will be removed from the platform no later than 90 days after the Engagement Expiration Date9. If additional time is required, the license holder can simply adjust the Engagement Expiration Date9, but that will likely increase the total Node-Months5 consumed.
  • At the termination of the contract term2, unused Node-Months5 shall expire unless otherwise granted via written consent by a Cloudamize representative.
  • Basic Support and access to the Cloudamize knowledge base are available to MULTI USE license holders. Enhanced Set-Up and Migration Ready support services can be purchased at an additional cost.

 

MULTI USE LICENSE CONSUMPTION EXAMPLE

Below is an example of 3 Engagements6 with a total consumption of 3700 Node-Months5. To support this type of consumption, a customer would need to purchase 309 MULTI USE Licenses (309 Nodes x 12 months = 3708 Node-Months).

Engagement Creation Date7 Engagement Expiration Date9 Number of Nodes3 Assessed Node-Months5 Consumed
January 20, 2025 March 20, 2025 500 1,000
February 1, 2025 April 18, 2025 200 600
January 1, 2025 June, 5, 2025 350 2,100

Note: The Number of Months used in the calculation is rounded up.

If you like the flexibility of the Multi-Use license mode, but do not like having to track Node-Months, consider the Tier Based plan. Or feel free to contact Sales to have a plan tailored to your needs.

 

TERMINOLOGY

  1. Order Form: Refers to the contractual agreement between Cloudamize and the customer. See Example Order Form.
  2. Contract Term: Duration of license availability and access to the Cloudamize Platform.
  3. Node: An individual server, either physical or virtual.
  4. Cloudamize Agent: A component of the Cloudamize platform, which is installed in the customer’s environment and used to collect data during the assessment phase.
  5. Node-Month: A calculation that involves multiplying a certain number of Nodes by a certain number of months. e.g. 100 nodes over 12 months equals 1,200 Node-Months.
  6. Engagement: A Multi Use contract can support multiple engagements/assessments. Engagements are created/provisioned within the Cloudamize Platform by the customer.
  7. Engagement Creation Date: The date that the assessment is provisioned/created within the Cloudamize Platform. Note: this is different from the Assessment Start Date. 
  8. Engagement Start Date: The date that the Customer clicks the “Start Assessment” button within the individual assessment.
  9. Engagement Expiration Date: The date, set by the Customer, that the assessment closes. Access to assessment data will not be available after this date.

 

SPECIFICATION REVISIONS

Revision Date Revision Description
January 20, 2025 Initial Release of the HTML version, including modernization and clarification of terms.