About the Project
WildFly is a flexible, lightweight, managed application runtime that helps you build amazing applications.
SAVE TIME WITH FASTER DEVELOPMENT
WildFly supports the latest standards for REST based data access, including Jakarta RESTful Web Services, Jakarta JSON Processing and Jakarta Data.
Building on EE provides rich enterprise capabilities in easy to consume frameworks that eliminate boilerplate and reduce technical burden.
The quick boot of WildFly combined with the easy-to-use Arquillian framework allows for test driven development using the real environment your code will be running in. Your test code is separate and simply deployed along side your application where it has full access to server resources.
SAVE RESOURCES WITH EFFICIENT MANAGEMENT
WildFly takes an aggressive approach to memory management and is based on pluggable subsystems that can be added or removed as needed.
The quick boot of WildFly combined with the easy-to-use Arquillian framework allows for test driven development using the real environment your code will be running in. Your test code is separate and simply deployed alongside your application where it has full access to server resources.
Configuration in WildFly is centralized, simple and user-focused. The configuration file is organized by subsystems that you can easily comprehend and no internal server wiring is exposed. Subsystems use intelligent defaults, but can still be customized to best fit your needs. If you are running in domain mode, the configuration for all servers participating in the domain is specified in a well-organized manner within the same file.
SAVE MONEY WITH OPEN SOURCE
WildFly is an open source community project sponsored by the Commonhaus Foundation. WildFly is fully open. All components are open source and follow a community-focused development process.
WildFly follows a roughly time-boxed development model, producing a major or minor release every three to four months. In nearly all cases this will be a major release; minors are rarely produced. The use of a minor version indicates a smaller than typical number of changes, likely because the team is working in the background on a large scale change that can't be implemented in a normal release cycle.
If we ever choose to move temporarily away from our practice of producing a major or minor every three to four months, we will announce that in a post in the news section of this site.
For each major or minor we produce a beta about two weeks before the final release.
Approximately a month after each major or minor release we will produce a micro, bug-fix-only release. Once we release the final version of a new major or minor, our practice is to no longer produce bug-fix releases for the previous series.
Planned release dates can be seen in the WildFly project calendar. Note that release plans can change at any time.
WildFly endeavors to keep up with the broader enterprise Java ecosystem, moving forward with our support for Java SE versions and enterprise Java standards. Within that broader context, however, we take great pains to maintain compatibility over time.
Currently, we maintain the WildFly 41 series, and expect to continue doing so until the WildFly 42 release in October 2026. All previous releases of WildFly are no longer maintained.
We encourage users interested in end-of-life support offerings for WildFly to investigate the Commonhaus Foundation Open Source Sustainability Initiative.
The Commonhaus Foundation Open Source Sustainability Initiative (OSSI) recognizes organizations that take responsibility for the security and stability of open source software beyond its end-of-life (EOL). For organizations that depend on EOL software but cannot yet upgrade, OSSI partners provide continued security support and compatibility fixes.
