WildFly
Modular Java application server with Galleon provisioning and a Kubernetes operator. Our application servers ranking puts WildFly at #7 of 14.
Commercial relationships can affect which products appear and how prominently. The WildFly link is marked as every vendor link is, see disclosure.
Visit WildFly See it in the application servers ranking
Key facts about WildFly
| Headquarters | Not stated by the vendor |
|---|---|
| Free plan | No free tier on record |
| Pricing model | Apache Licence 2.0 downloads; the pages list no prices, plans or paid support terms |
| Best for | Teams deploying Jakarta EE applications to Kubernetes or OpenShift with provisioning tools |
| Deployment | Vendor does not say, as far as we read |
| API | WildFly mentions an API in the material we reviewed |
What is WildFly?
WildFly is described on its home page as a Java application server with centralised configuration, class isolation based on JBoss Modules and a low memory footprint. The home page says it implements current Jakarta EE and MicroProfile standards, that WildFly 40 was feature-boxed to deliver Jakarta EE 11 support, and that WildFly 42 Final is available.
The downloads page lists 42.0.0.Final, dated 22 October 2026, as a standard distribution and a WildFly Preview distribution, each as zip and tgz. The GitHub repository states the project is licensed under the Apache License 2.0. The news page describes the project as community-focused with all components open source, shows the Commonhaus Foundation logo, and does not name a company that runs it. No country is stated on the pages we read.
WildFly key features
- Modular class isolation. Class isolation is based on JBoss Modules, according to the home page. Applications therefore do not share libraries by accident, though the pages read give no examples of conflicts it avoids.
- Centralised configuration. The home page names centralised configuration as a core trait. How it is edited, through files or a console, is not shown on the pages we read.
- Jakarta EE 11 and MicroProfile 7.1. The documentation's getting-started section links the Jakarta EE 11 Platform API and the MicroProfile 7.1 API. The home page also lists a temporary WildFly EE 10 variant for the 40 and 41 releases.
- Galleon and Prospero provisioning. Galleon feature packs are published in Maven Central, and Galleon and Prospero are named as the provisioning tools for building distributions and feature packs. A team can assemble a trimmed server.
- Maven plugin and bootable JAR. The WildFly Maven Plugin can execute CLI commands, and WildFly Glow and a bootable JAR option are documented for building applications. This suits teams packaging servers as part of a build.
- Kubernetes and OpenShift support. A container image, a Helm chart, an operator for Kubernetes and OpenShift, and Source-to-Image builder and runtime images are listed in the documentation. These cover the main cloud deployment routes.
- Standard and Preview distributions. Two distributions of 42.0.0.Final are offered, each as zip and tgz with SHA-1 checksum and GPG signature. Nightly snapshot builds from the main branch are linked for testers.
Who WildFly suits
- A team moving Jakarta EE applications to Kubernetes. The documentation lists a Helm chart, an operator and Source-to-Image images, so a group deploying to Kubernetes or OpenShift finds the packaging already described.
- A developer building a slim bootable server. With Galleon feature packs, the bootable JAR option and WildFly Glow documented, a developer can build an application together with only the server parts it needs.
- A project that wants to try Jakarta EE 11. WildFly 40 was feature-boxed for Jakarta EE 11 support, and 42 Final is available, so a team can test its code against the newest platform on a released server.
Getting started with WildFly
The pages we read describe downloads and documentation rather than a numbered setup guide. Start on the downloads page, which lists WildFly 42.0.0.Final, dated 22 October 2026, as a standard distribution and a WildFly Preview distribution in zip or tgz format. Each download has a SHA-1 checksum and a GPG signature, so verify the file before use.
For application builds, the documentation covers the WildFly Maven Plugin, WildFly Glow and a bootable JAR option. For Kubernetes or OpenShift, it lists a container image, a Helm chart, an operator and Source-to-Image images. The getting-started section links the Jakarta EE 11 Platform API and MicroProfile 7.1 API, and lists previous releases. Nightly snapshot builds from the main source branch are also linked.
The case for and against WildFly
- WildFly 42 Final, dated 22 October 2026, ships as a standard distribution and a Preview distribution under the Apache Licence 2.0.
- Marked in our records as jakarta EE 11.
- WildFly is tagged MicroProfile in our records.
- Best for: Teams deploying Jakarta EE applications to Kubernetes or OpenShift with provisioning tools.
- Helm and operator, one of the three traits the catalogue lists for WildFly.
- The pages read do not state who develops WildFly day to day or where it is based.
- Look elsewhere if you are Buyers wanting named paid support terms on the project site.
- The pages we read do not say which company develops it day to day or name a country, though the footer shows the Commonhaus Foundation logo.
- The home page calls the WildFly EE 10 variant in releases 40 and 41 temporary, so teams on Jakarta EE 10 face a platform move.
What we make of WildFly
WildFly 42 Final, dated 22 October 2026, ships as a standard distribution and a Preview distribution under the Apache Licence 2.0. It implements Jakarta EE and MicroProfile and provisions through Galleon feature packs, a Maven plugin or a bootable JAR.
The pages we read do not say which company develops it day to day or name a country, though the footer shows the Commonhaus Foundation logo.
WildFly is entry #7 of 14 in the application servers list: it follows Apache Tomcat and comes before Gunicorn. From place 4 the established names follow in their ranked order; we publish no numeric score.
The vendor states no country of establishment, so WildFly is left out of the regional count for this list.
WildFly pros and cons in practice
- The Apache License 2.0 is stated on the GitHub repository.
- Kubernetes, OpenShift, Helm and Source-to-Image packaging is documented.
- Galleon feature packs and a bootable JAR option allow slimmer builds.
- Jakarta EE 11 support and 42 Final are available as of 22 October 2026.
- The pages read show no paid support terms and no company that sells them.
- WildFly 40 and 41 shipped a separate EE 10 variant described as temporary, which adds version choices.
- The pages read do not state who develops WildFly day to day.
- No country is stated on the pages we read.
Setup, support and exit with WildFly
WildFly's home page cites centralised configuration, class isolation based on JBoss Modules and a low memory footprint.
Documentation covers a container image, a Helm chart, an operator for Kubernetes and OpenShift, and Source-to-Image images, with Galleon and Prospero for building distributions.
Downloads carry SHA-1 checksums and GPG signatures, and nightly snapshots are linked.
The getting-started section links the Jakarta EE 11 Platform API and the MicroProfile 7.1 API.
What WildFly costs
In the catalogue: Apache Licence 2.0 downloads; the pages list no prices, plans or paid support terms.
The downloads and home pages show no prices, subscription plans or paid support terms for WildFly. The GitHub repository states the project is licensed under the Apache License 2.0, and the news page describes the project as community-focused with all components open source. The pages read do not name a company that runs the project or sells support, so a paid support contract is not described anywhere we looked. Costs would be hosting, staff time for upgrades and any outside help bought separately. Upgrades are frequent: the home page mentions WildFly 40, 41 and 42, and the downloads page dates 42.0.0.Final to 22 October 2026, so the effort of following releases is a real, if unpriced, cost.
Source: the pricing material on wildfly.org, as read for Best Application Servers in 2026 and last reviewed on 15 November 2026.
WildFly: data and security
WildFly is downloaded and run by the customer, so data stays on the infrastructure where it is installed. Each download carries a SHA-1 checksum and a GPG signature. The pages we read name no security certifications, audit reports or compliance attestations, and they do not describe a vulnerability reporting process.
The source code is public on GitHub under the Apache License 2.0. The news page footer shows the Commonhaus Foundation logo and links to its trademark pages, but the pages read do not state who develops WildFly day to day, and they give no country. Anyone with jurisdiction or contractual questions has no vendor contact on these pages.
WildFly fact sheet
| Product | WildFly |
|---|---|
| Vendor website | wildfly.org |
| Catalogue tags | Jakarta EE 11, MicroProfile, Helm and operator |
| Headquarters | Not stated by the vendor |
| Primary guide | Best Application Servers in 2026 |
| Rank there | #7 of 14 |
| Head-to-head pages | Not paired so far |
| Price visibility | Model recorded, no figure |
| Alternatives page | No dedicated page |
| What we do not hold | funding rounds and staff numbers |
WildFly integrations and ecosystem
Integrations the vendor names (9):
- Jakarta EE 11
- MicroProfile 7.1
- Maven Central
- Galleon
- Prospero
- Helm
- Kubernetes
- OpenShift
- Source-to-Image
Also in our records:
- The getting-started section links the Jakarta EE 11 Platform API and the MicroProfile 7.1 API.
What to look at instead of WildFly
4 products in this guide come closest to WildFly on tags, pricing and region.
- Payara Server (#4 of 14): Jakarta EE 11 server, now sold under the Azul name per vCore. Suits: Teams migrating off WebLogic, WebSphere or JBoss EAP who want vendor support.
- Apache TomEE (#5 of 14): Jakarta EE server built on Tomcat, in four distributions.
- Uvicorn (#10 of 14): Aimed at: Teams running async Python frameworks needing WebSockets and HTTP/2 from one server.
- Red Hat JBoss EAP (#12 of 14): Red Hat's supported Jakarta EE platform for on-premise and cloud. Best for: Organisations running OpenShift that want an application server tuned for it.
Where else WildFly is ranked
| Guide | Position |
|---|---|
| Best Application Servers in 2026 | #7 of 14 |
WildFly FAQ
9 answersWhere does WildFly stand among application servers?
WildFly is #7 of 14 in our application servers ranking.
What are the main alternatives to WildFly?
The closest products in the same guide are Payara Server, Apache TomEE, Uvicorn and Red Hat JBoss EAP. You will find each one reviewed in the application servers ranking.
Is WildFly the right fit for me?
Teams deploying Jakarta EE applications to Kubernetes or OpenShift with provisioning tools. Less suited to: buyers wanting named paid support terms on the project site.
Which country is WildFly from?
The vendor pages we reviewed state no country of establishment for WildFly, so we do not give one.
How much does WildFly cost?
The pricing entry for WildFly reads: Apache Licence 2.0 downloads; the pages list no prices, plans or paid support terms. On free access, nothing is free to use, as far as we recorded.
Is WildFly free?
The downloads and home pages show no prices, plans or paid support terms, and the GitHub repository states the Apache License 2.0.
What is the latest release?
The downloads page lists WildFly 42.0.0.Final, dated 22 October 2026, as a standard and a Preview distribution.
Does it run on Kubernetes?
The documentation lists a container image, a Helm chart, an operator for Kubernetes and OpenShift and Source-to-Image images.
Who runs the project?
The news page calls it community-focused and names no company. It shows the Commonhaus Foundation logo, but does not say who develops it day to day.
WildFly: sources
Read from the vendor’s own pages on 14 November 2026.
- wildfly.org: Description, standards support, WildFly 40 to 42 statements
- wildfly.org/downloads: 42.0.0.Final dated 22 October 2026, distributions, checksums, no prices
- github.com/wildfly/wildfly: Apache License 2.0
- docs.wildfly.org: Maven plugin, Glow, bootable JAR, cloud deployment, Galleon and Prospero
- wildfly.org/news: Community-focused, open source, Commonhaus logo, no company named
How we rank
Feature lists tell little, so positions rest on setup effort, the true price, portability and fit. The result for WildFly: #7, out of 14 ranked. Read the editorial process for the method and where paid visibility fits in.