Azul Intelligence Cloud is Azul Systems’ software-as-a-service product for analysing Java runtimes in production. Its agreement defines it as “Azul’s proprietary Internet enabled software-as-a-service Product, including the API services”.[1] The documentation says it collects runtime data to inventory JVMs and find unused code. It works “with any JVM from any vendor or distribution including Azul, Oracle, Amazon, Microsoft, RedHat, and Temurin”.[3] The product is sold under its own agreement, separate from the Azul Software Agreement that covers the runtimes. Customers pay Base Fees plus Units, and Units are counted in Distinct JVMs.[1] Azul positions the JVM Inventory feature for Oracle Java migration and licence compliance.[2] This page covers only how Intelligence Cloud itself is licensed. For the Oracle obligations it is used to assess, see Oracle Java SE licensing.
Editions
The retrieved documents describe no named editions. The product page lists two features, Code Inventory and JVM Inventory, and two support tiers, Standard and Premium.[2] The documentation lists three services built on the collected data: Explorer (individual JVM runs), Code Inventory (code execution at class and method level) and JVM Inventory (JVMs that have connected).[3] Pricing is by quote.[5] Catalog SKU: Azul Intelligence Cloud subscription - Base Fees plus Distinct JVM Units.
| Feature | Vendor description | Licence relevance |
|---|---|---|
| JVM Inventory | Catalogs all running JVMs and their workloads in real time[2] | Each monitored JVM sends a JVM Stream, and JVM Streams are what Units count[1] |
| Code Inventory | Catalogs which libraries, classes and methods run in production[2] | Same Distinct JVM measure; no separate metric published |
| Explorer | Information about individual JVM runs[3] | Same |
Metrics
| Azul term | Catalog row | Contract definition |
|---|---|---|
| Distinct JVMs | Distinct JVMs | “the monthly average number of unique JVM Streams that connect to the Product per hour as reported by Azul in each monthly billing cycle during the Order Term”[1] |
| Units | same row | The number of Distinct JVMs the customer purchases and is permitted to use, as described in an Order[1] |
| Overage Units | same row | The number of Distinct JVMs used in a month above the Units purchased[1] |
| Base Fees | (commercial term) | The base annual fees in an Order for use of the Product[1] |
Several further definitions determine what is counted.[1] A JVM Stream is a single stream of Customer Artifacts that a Connected JVM sends to the Product while running Customer Software. A Connected JVM is an Azul JVM, “or any third-party Java virtual machine”, that connects to the Product through a local agent or another mechanism and sends a JVM Stream. Customer Artifacts are the data produced by Customer Software on a Connected JVM. They include metadata describing application byte code, logs, environment data, classes and methods, operating system data and virtual machine inventory. The documentation adds that each run of a JVM is a separate instance with its own ID. When the same application is run several times, each run is a separate instance.[6]
Counting / floors
Hourly unique streams, averaged monthly (Version May 2025). Azul counts the unique JVM Streams connecting per hour and averages that number over each monthly billing cycle. Azul reports the figure.[1] An estate with many short-lived JVMs, such as autoscaled containers, is therefore counted by how many are connected concurrently in an average hour. It is not counted by the total number of JVM starts in the month. Catalog proof: Intelligence Cloud Units are Distinct JVMs: the monthly average of unique JVM Streams per hour.
Third-party JVMs count (Version May 2025). Oracle, Amazon, Microsoft, Red Hat or Temurin JVMs connected through the agent are Connected JVMs, so they count toward Distinct JVMs.[1][3] Catalog proof: Third-party JVMs connected to Intelligence Cloud count as Connected JVMs.
Overage (Version May 2025). The customer pays the Base Fees and Units set in the Order. “If Customer exceeds the number of purchased Units in a calendar month, Azul will invoice Customer for such Overage Units at the end of the month when Customer incurs such charges.”[1] The General Terms also say the customer will not use the Product on more Units than purchased, so overage billing does not make excess use a permitted entitlement.[1] Catalog proof: Intelligence Cloud overage is invoiced monthly.
Floors. No minimum Units are published. Base Fees apply in addition to Units.[1]
Support contacts by volume. The number of Designated Support Contacts depends on the Distinct JVMs purchased:[1]
| Distinct JVMs | Designated Support Contacts |
|---|---|
| 1 to 100 | 2 |
| 101 to 999 | 4 |
| 1,000 to 4,999 | 6 |
| 5,000 to 9,999 | 8 |
| 10,000 and over | 12 |
Virtualization & partitioning
The metric counts JVM Streams, not processors or hosts, so virtualization and partitioning do not change the count. What matters is how many distinct JVMs connect in an average hour.[1] Connection runs through a Forwarder, which relays traffic between JVMs on an internal network and the service. On Azul JVMs, the built-in Connected Runtime Service is disabled by default and has to be enabled.[6] JVMs that are never connected are therefore not counted.
Cloud / BYOL
Intelligence Cloud is itself a hosted service. The agreement defines it as “offered as a software-as-a-service subscription”.[1] No bring-your-own-licence mapping applies. The customer is responsible for the connectivity, hardware and software it needs to reach the service.[1]
Programs
- Azul Intelligence Cloud Agreement. The customer receives a non-transferable, nonexclusive right to use and access the Product during the Order Term, without rights to sublicense. The right is limited to use “solely in connection with Customer’s internal business operations”.[1]
- Support tiers. Standard offers Standard Business Hours, a next-business-day SLA and 6 Tickets per year. Platinum or Premium offers 24x7x365 support, a one-hour SLA and unlimited Tickets.[1] The product page shows Standard and Premium.[2]
- Evaluation License. A Product licensed free or for a nominal charge falls under a separate Evaluation License Agreement. The customer “may not use any Azul products that are licensed under an Evaluation License during the Order Term”.[1] Catalog proof: Under an Intelligence Cloud Order, Azul products may not be used under an Evaluation License.
Contract terms
No third-party access (Version May 2025). The customer may not share login credentials or access with third parties, and may not make the Product available to any third party. It also may not use the Product to create a competing product.[1] Reports produced by the Product are Azul’s Confidential Information. They “may not be communicated to third parties without Azul’s written permission”.[1] This matters when an outside consultant or licensing advisor is to work with JVM Inventory output. Azul may suspend access without notice if it reasonably suspects a breach of these restrictions.[1] Catalog proof: Intelligence Cloud access and Reports may not be shared with third parties.
No warranty of completeness. Azul does not warrant that the Product will identify all vulnerabilities, or that its Reports are accurate or complete.[1] An inventory from JVM Inventory therefore supports a licence position but is not a contractual statement of one. The JVM Inventory data sheet says the data helps determine “if a bundled license exists to authorize use or if there is a commercial obligation” for Oracle JVMs.[4]
Data (Version May 2025). The Product receives JVM Streams but not source code or data locally accessed by Customer Software. The customer licenses Customer Artifacts and Customer Software to Azul to provide and improve the Product. Azul may use aggregated quantitative data that contains no Customer Artifacts. Azul deletes Customer Artifacts within a reasonable time after the subscription ends.[1]
Uptime (Version May 2025). Azul commits commercially reasonable efforts to keep the service available 99.9% of the time, measured monthly. Below 99.9% but above 90%, the remedy on request is a written improvement plan. Below 90%, Azul may provide additional Units or extend the Order Term. These are the sole remedies.[1] Catalog proof: Intelligence Cloud uptime commitment is 99.9% monthly, with plan or Unit remedies.
Renewal and fees (Version May 2025). Fees are paid up front. Renewals are invoiced no earlier than 60 days before the term ends. Terms renew automatically for equal periods unless notice is given 60 days before the end, and renewals are at the same price unless Azul notifies otherwise. Payments are non-refundable except when Azul fails to cure a material breach.[1] Catalog proof: Software Services renew automatically unless notice is given 60 days before term end.
Audits and compliance
The General Terms include the same self-certification clause as the Azul Software Agreement. On written request, no more than once per calendar year, the customer reviews its use and delivers a signed certificate of material compliance. Any underpayments must be paid promptly.[1] Because Azul reports Distinct JVMs itself each billing cycle, usage is also measured continuously by the vendor.[1] Catalog proof: Annual self-certification of compliance on Azul’s request; no audit clause.
Out of scope
This page does not cover the Azul runtimes (see Azul Core and Zulu OpenJDK licensing and Azul Prime licensing), the Oracle licence questions that JVM Inventory is used to answer (see Oracle Java SE licensing), or AI-assisted features, which the May 2025 agreement does not address separately.