Azul Systems licensing covers the terms under which Azul Systems, Inc. provides its Java products. These are commercially supported builds of OpenJDK (Azul Core), a performance-oriented Java platform (Azul Prime), a software-as-a-service runtime analytics product (Azul Intelligence Cloud) and the Azul Payara application servers. The runtimes and their support are sold as “Software Services” under the Azul Software Agreement. The Agreement defines Software Services, together with Units and Third-Party Software Licenses, by reference to a product exhibit and the customer’s Order.[1] Intelligence Cloud has a separate agreement.[3] Azul’s builds of OpenJDK are also offered free of charge as Azul Zulu Builds of OpenJDK, which Azul describes as “Free to download and use”.[4] For a practitioner the key point is which of three licence types applies. Azul Platform Core carries a perpetual right to use with time-based support. Azul Platform Prime is a time-based subscription licence. Intelligence Cloud is a SaaS subscription metered in Distinct JVMs.[1][3] Many Azul customers are replacing Oracle Java SE, whose employee-based subscription is described in Oracle Java SE licensing.
Editions
Azul’s website names five product lines: Azul Core, Azul Prime, Azul Payara Micro, Azul Payara Server and Azul Intelligence Cloud. The contract templates still use the earlier names Azul Platform Core and Azul Platform Prime.[4][1] Azul lists Azul Core, Azul Prime, Azul Zulu, Azul Zulu Prime and Zing among its trademarks.[16] The Azul Core page says the product was formerly Zulu Enterprise and Zulu Embedded.[5]
| Offering (current name) | Contract name and contents | How it is priced |
|---|---|---|
| Azul Zulu Builds of OpenJDK | Free Community Availability (CA) builds; Java 8, 11, 17, 21, 25[4] | Free to download and use[4] |
| Azul Core | Azul Platform Core: Azul Zulu Builds of OpenJDK and Azul Mission Control (Exhibit A-2)[1] | Per vCore or Desktop; contact sales[4] |
| Azul Prime | Azul Platform Prime: Azul Zulu Prime Builds of OpenJDK, Azul Zulu Prime System Tools, ZVision, Connected Compiler, Azul Mission Control (Exhibit A-1)[1] | Per vCore, annual; Premium Support level[8] |
| Azul Intelligence Cloud | SaaS product (Code Inventory, JVM Inventory)[14] | Base Fees plus Units of Distinct JVMs[3] |
| Azul Payara Server and Azul Payara Micro | Jakarta EE application server and runtime; free Azul Payara Community edition[11] | Per vCore; request a quote[12][4] |
Azul publishes list prices only for Azul Support for OpenJDK. These are starting prices of $25 per Desktop per year, $20 per vCore per year and $40 per physical core per year, reduced by volume and support tier.[7] They are recorded as SKUs such as Azul Support for OpenJDK - vCore, annual. Everything else is priced by quote. See Azul Core and Zulu OpenJDK licensing, Azul Prime licensing and Azul Intelligence Cloud licensing.
Metrics
| Azul term | Catalog row | Where it applies | What Azul says |
|---|---|---|---|
| Unit (Virtual Core) | Azul Core Unit (Virtual Core) | Azul Core on servers and cloud | Software Services with one or more Azul Zulu instances on one Virtual Core, plus Azul Mission Control on unlimited Virtual Cores[1] |
| Unit (Desktop) | Azul Core Unit (Desktop) | Azul Core bought for Desktop-only use | One physical desktop or laptop computer[1] |
| Unit (Virtual Core) | Azul Prime Unit (Virtual Core) | Azul Prime | Azul Zulu Prime or Azul Zulu instances on one Virtual Core[1] |
| Distinct JVMs | Distinct JVMs | Azul Intelligence Cloud | Monthly average of unique JVM Streams connecting per hour[3] |
| vCore (Payara) | Azul Payara vCore | Azul Payara Server and Micro | “Transparent per-vCore pricing, not per pod or per container”[12] |
| Supported Instance | Supported Instance (2019 agreement) | Zulu Enterprise and Zing contracts on the 2019 paper | One Physical Node of up to two sockets, or one Virtual Node of up to 32 virtual cores[15] |
Azul’s metrics count processing capacity where the runtime runs. They do not count people. The Oracle Java SE Universal Subscription, by contrast, is counted per Employee (see Oracle Java SE licensing). For the general model, see processor and core licensing.
Counting / floors
Units purchased (Rev July-2025). The customer may only use the Product on the number of Units purchased. It may not use Software Services or Support Services for installations on more Units than it bought.[1] Catalog proof: Product may only be used on the number of Units purchased.
Virtual Core arithmetic (Rev July-2025). A Virtual Core maps to a single hardware thread. A customer that can only count physical cores counts each one as two Virtual Cores.[1] Azul Mission Control does not add to the count, because a Unit includes it on an unlimited number of Virtual Cores.[1] Catalog proof: One Virtual Core equals one hardware thread; one physical core equals two Virtual Cores; Azul Mission Control runs on an unlimited number of Virtual Cores within a Unit.
Desktops (Rev July-2025). Azul Platform Core may not be deployed on Desktops unless an Order Form says so. Desktop-only purchases count one Unit per Desktop.[1] Catalog proof: Azul Platform Core may not be deployed on Desktops unless the Order Form says so.
Support tier per installation (Rev July-2025). Support bought at one tier cannot be used for installations bought at a lower tier. Premium Support, for example, cannot cover Standard-only installations.[1] Catalog proof: Higher-tier support cannot be used for installations bought at a lower tier.
Floors. None of the retrieved documents sets a minimum purchase quantity. The Azul Prime pricing page says Prime is available for the Premium Support level.[8]
Virtualization & partitioning
The Virtual Core definition counts processing power “in a single hardware virtualization that can run its own operating system”. Each Virtual Core maps to one hardware thread.[1] The retrieved agreements publish no hard or soft partitioning policy. They also offer no host-level licensing option that would let a customer license a hypervisor host instead of its guests, and nothing on cluster mobility. A virtual machine or cloud instance is counted by its own virtual cores. The September 2019 agreement used a different model. There, one Supported Instance covered a physical system of up to two sockets, or a virtual machine of up to 32 virtual cores.[15] Contracts still on that paper therefore count differently. Catalog proof: 2019 agreement: one Supported Instance per two-socket Physical Node or 32-core Virtual Node. For the cross-vendor background, see virtualization and partitioning.
Cloud / BYOL
Azul prices Azul Core server support per vCore “for cloud-based deployments”.[7] The Virtual Core definition therefore applies to cloud instances in the same way as to on-premises virtual machines.[1] The retrieved documents contain no bring-your-own-licence rule and no list of authorized clouds. Azul Payara is priced per vCore rather than per pod or container.[12] One historical cloud program existed. Zulu for Azure binaries were free only for Java applications developed and deployed in Microsoft Azure, Azure Stack or Microsoft SQL Server. Their updates ended on 2021-12-31.[17] Catalog proof: Zulu for Azure binaries were free only for Azure, Azure Stack and SQL Server use; updates ended 2021-12-31. Purchases through cloud marketplaces are outside the retrieved documents.
Programs
- Azul Software Agreement (Rev July-2025). This is the master terms for Azul Platform Core and Azul Platform Prime. Software Services are ordered by a mutually executed Order Form and paid up front.[1] The main azul.com agreement page links the July 2023 revision, which has the same product exhibits without Exhibit D.[2]
- Azul Intelligence Cloud Agreement (Version May 2025). A separate SaaS agreement with Base Fees, Distinct JVM Units and monthly overage billing.[3]
- Support tiers. Standard, Premium and Platinum tiers set response times, ticket limits, update SLAs and the scope of indemnification.[1] See Azul support tiers and lifecycle.
- Legacy Production Support. A paid option for Java 6 and 7, Java Applets and IcedTea-Web, governed by Exhibit D.[1] The roadmap shows Java 6 and 7 support to December 2029 for customers who buy it.[10]
- Distribution Rights. OEM and ISV redistribution of the Product inside a Combination Product, under Exhibit C.[1]
- Evaluation License. Free or nominal-charge use falls under a separate Evaluation License Agreement.[1] Azul Prime Stream Builds are free for development, testing and evaluation.[9]
- Azul Prime open source developer access program. Free annual subscriptions for open source committers.[9]
- Business Partner purchasing. Azul supplies the Product and support. The Business Partner sets payment terms.[1]
Contract terms
What survives the subscription (Rev July-2025). Exhibit A-2 grants a perpetual right to use Azul Platform Core. The Software Services it sells are time-based Support Services.[1] The FAQ confirms that customers can keep using Azul OpenJDK products after their support subscription expires.[7] Exhibit A-1 grants Azul Platform Prime only as a time-based subscription licence.[1] On termination, all licences end except perpetual ones, and those survive only if the customer has not materially breached the Agreement.[1] Catalog proof: Azul Platform Core licence is perpetual; the subscription buys time-based support; Azul Platform Prime is a time-based subscription licence for internal business operations; On termination all licences end except perpetual ones, absent customer breach.
Fees and renewal (Rev July-2025). Fees are paid up front for each term. Renewals are invoiced no earlier than 60 days before the term ends, and payment is due within 30 days of invoice.[1] Software Services renew automatically for equal terms unless either party gives notice at least 60 days before the end. Renewal is at the same price unless Azul notifies otherwise. Payments are non-refundable.[1] Catalog proof: Software Services renew automatically unless notice is given 60 days before term end; Fees are paid up front for each term and are non-refundable.
Use restrictions (Rev July-2025). The customer may not distribute the Product externally unless an Exhibit A or Order allows it. Nor may it post the Product publicly, use it for timesharing or service-bureau purposes, or sell any Azul product without paid and active Software Services for it.[1] Assignment needs the other party’s consent, except to a successor to the licensed business.[1] Catalog proof: No external distribution, public posting or third-party use without authorisation; Licences are not assignable without consent, except to a successor of the licensed business.
Free builds. Anyone who downloads or uses Azul Zulu Builds of OpenJDK without a support agreement accepts the Azul builds of OpenJDK Terms of Use. Under these terms the builds are provided as is, with no support obligation. Azul’s liability for direct damages is capped at $100.[6] Azul distinguishes these Community Availability builds from the Subscriber Availability builds supplied with Azul Core.[5] Catalog proof: Free Azul Zulu builds are provided as is, without support, under the Terms of Use; Zulu CA builds carry no licensing fee; Zulu SA builds come with an Azul Core subscription.
Audits and compliance
The retrieved Azul Software Agreement does not give Azul a right to audit the customer on site or through a third party. Section 6 instead provides for self-certification. On written request, no more than once per calendar year, the customer reviews its use of the Software Services. It then delivers a certificate, signed by an authorized signatory, stating that it is in material compliance and has paid all applicable fees. Any underpayment found must be paid promptly.[1] The Intelligence Cloud Agreement contains the same clause.[3] Catalog proof: Annual self-certification of compliance on Azul’s request; no audit clause.
In practice, compliance means reconciling Virtual Cores and Desktops that run Azul Zulu Subscriber Availability or Azul Zulu Prime builds against the Units and Support Tier in each Order. Free Community Availability builds on the same estate do not consume Units. Distinguishing CA from SA builds therefore matters.[5] A signed agreement may add terms that the templates lack. The general discipline is covered in license compliance and software license audit.
Out of scope
This page does not cover the following:
- Oracle Java SE subscriptions: see Oracle Java SE licensing.
- Terms of third-party software bundled with Azul products, which the agreements leave to the listed third-party licences.
- Marketplace listings.
- Azul professional and migration services.
- The licence terms of the Azul Payara products, which are not published on azul.com. Azul Payara pricing and the published lifecycle are summarised here and in Azul support tiers and lifecycle. Azul’s own pages differ on packaging. The Micro page says one subscription covers both Server and Micro,[12] while the Micro data sheet says Azul Payara Server is sold as a separate subscription.[13]