Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsAzul announced on December 10, 2025, that it had acquired Payara, adding Payara’s enterprise Jakarta EE application-server products and expertise to Azul’s Java portfolio. Azul said it planned to retain the Payara brand, but its acquisition FAQ described the combined product portfolio and roadmap as still under review. The companies did not disclose the financial terms.
What Azul’s acquisition of Payara adds
Azul provides Java platform products; Payara develops enterprise software for Jakarta EE applications and microservices, including deployments in hybrid and cloud-native environments. Jakarta EE is the successor to Java EE. The acquisition therefore broadens Azul’s stated portfolio from Java platform technology into the application-server layer used to run enterprise Java applications.
Azul and Payara said they had worked together for nearly eight years. Their collaboration began in 2018, when Azul Core was embedded in Azul Payara Server Enterprise, according to Azul’s December 10, 2025 announcement.
The companies’ stated strategy
Azul presented the deal as a way to combine its Java platform with Payara’s application-server products, Jakarta EE engineering expertise, and go-to-market experience. The companies described the resulting portfolio as commercially supported open-source software spanning the Java application stack. These are the companies’ strategic claims, not independent evidence that the combined products are faster, less expensive, or superior to alternatives.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Azul cited an estimated $26 billion application-server total addressable market and a projected annual growth rate of 11–14% for 2025–2033, attributed to IMARC Group. That is a market forecast cited by Azul—not the value of the Payara acquisition—and the announcement does not independently substantiate it.
Deal terms and ownership context
Azul’s acquisition FAQ says the financial terms were not disclosed. No purchase price can be established from the company’s announcement and FAQ.
Rank #2
The announcement also noted that Azul had recently completed a majority investment from Thoma Bravo, alongside renewed minority investments from Vitruvian Partners and Lead Edge Capital. That describes Azul’s financing context; it does not disclose what Azul paid for Payara.
What the announcement says about products and customers
Azul said it planned to continue using the Payara brand. Its FAQ said existing customers would gain access to a broader portfolio and partner ecosystem, and that Azul was reviewing the combined portfolio while working on integration. Azul also promised advance notice before changes to product availability. Those statements describe plans at the time of the FAQ, not a final integration roadmap or a guarantee that every product, term, or support arrangement will remain unchanged.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The announcement identifies finance and healthcare as sectors where Payara says it supports mission-critical systems, and names BMW Group, Rakuten, Swisscom, and KCB Bank Group as customers. These are company-reported customer and sector claims, not independently confirmed references.
What it could mean for application-server migrations
Azul’s FAQ identifies Oracle WebLogic and IBM/Red Hat JBoss as traditional application-server migration contexts. It also names open-source GlassFish and WildFly as environments for which the combined offering could provide a commercially supported path. This makes migration and support relevant reasons to assess the portfolio, but the announcement does not establish that a particular application will migrate without code changes, compatibility work, or operational risk.
Rank #4
Enterprises evaluating a move should assess their own applications and contracts against the questions below rather than infer migration ease from the acquisition announcement.
- Compatibility and effort: Check the application’s Java EE or Jakarta EE APIs, server-specific features, libraries, and configuration. Require a proof of concept for representative workloads.
- Support commitments: Confirm the exact product, version, patch policy, security-response terms, support duration, and escalation process in writing.
- Deployment fit: Validate the intended hybrid or cloud-native architecture, including observability, scaling, security controls, and operational tooling.
- Cost and licensing: Compare complete licensing and support terms for the specific deployment; the acquisition announcement provides no comparative pricing.
- Roadmap and availability: Ask Azul for current product names, availability, lifecycle commitments, and any customer notices applicable to the products in use.
What remains unknown
The announcement and FAQ establish the acquisition announcement, the companies’ stated rationale, and Azul’s customer-facing plans at that time. They do not disclose the purchase price or establish a completed product-integration roadmap. Nor do they provide independent comparative evidence that the combined portfolio outperforms Oracle WebLogic, IBM/Red Hat JBoss, GlassFish, WildFly, or other alternatives.
Recommended Free Tools
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
