wildfly/wildfly

WildFly Application Server

View on GitHub ↗Jump to charts ↓

wildfly/wildfly has 3k+ stars and 2k+ forks on GitHub, is written in Java, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 55 minutes ago
Type:Server / PlatformCategory(s):Backend FrameworksWeb Development
Added to GitGenius on September 21st, 2026
Created on July 8th, 2010
Open Issues & Pull Requests: 106 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 2,263
Total Stargazers: 3,196 (+0)
Total Subscribers: 176 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

WildFly is a Java application server that provides a runtime environment for deploying and running enterprise Java applications.

WildFly addresses the need for a flexible, modular application server capable of running Jakarta EE and other Java-based workloads. The server uses a modular architecture that allows developers to include only the subsystems and features their applications require, reducing memory footprint and startup time compared to monolithic alternatives. This approach enables both traditional on-premises deployments and cloud-native containerized environments.

Organizations should consider WildFly for enterprise Java applications that benefit from Jakarta EE compliance, microservices architectures, or scenarios where resource efficiency matters. The modular design makes it suitable for teams wanting to customize their runtime rather than accept a one-size-fits-all application server. It works well in containerized deployments where minimal image size and fast startup are priorities, as well as in traditional application server contexts where stability and standards compliance are required.

The project maintains steady development activity with regular contributions across core subsystems, security updates, and feature enhancements. Work spans multiple areas including clustering, web services, messaging, and datasource management, indicating active maintenance of the full application server stack. The codebase receives ongoing attention to compatibility with evolving Java platform standards and emerging deployment patterns.