Gruxi is an opinionated web server focused on high performance, operational simplicity, and predictable behavior. It is designed to serve as a reliable foundation for modern web applications without exposing users to excessive configuration complexity.
The project is built on practical experience from decades of operating and maintaining production web servers. Gruxi deliberately avoids configuration knobs that rarely provide real‑world value, favoring sensible defaults and a clear administration model instead.
Gruxi is actively developed and tested. New features and improvements are released continuously once they meet stability and quality requirements.
Status: Active development
Gruxi is usable today, but it has not yet reached a 1.0 release. Core functionality is stable, while configuration formats and internal APIs may still evolve. Backward‑incompatible changes may occur prior to 1.0.
- Event‑driven architecture with low per‑request CPU and memory overhead
- Extremely fast static file serving
- High‑performance in‑memory file cache
- Content compression
- HTTP/1.1 and HTTP/2 support
- Reverse proxy with TLS offloading
- Load balancing and health checks
- Caching headers and conditional requests
- Range requests supported
- Native TLS support
- Automatic certificate issuance and renewal via Let’s Encrypt
- Built‑in web interface for administration, configuration, and monitoring
- Live metrics and server status
- PHP support via PHP‑FPM
- Managed PHP‑CGI on Windows, with easy version switching
- System logging
- Access logging
- Log rotation built‑in, no external tools required
Gruxi is designed for developers, agencies, and hosting environments that value clarity, performance, and minimal operational overhead.
Many existing web servers offer extensive configuration surfaces with hundreds of tunables. This flexibility is useful in some cases but often adds unnecessary complexity. In practice, most teams want their web server to behave predictably, perform well, and stay out of the way.
Gruxi intentionally removes low‑value configuration choices. For example, internal buffer sizes and similar micro‑optimizations are not exposed. If a setting is unlikely to materially improve outcomes for the majority of users, it is fixed and carefully chosen.
Comprehensive documentation is available at:
The admin portal provides configuration management, monitoring, and operational insight.
- Username:
admin - Password: Generated on first startup and printed to the server output
The initial password is not displayed again after first launch. It can be reset using the --reset-admin-password on command line.
The following section documents performance characteristics of Gruxi under controlled load. Benchmarks were executed on local developer hardware with repeatable configurations, without any network overhead beyond localhost. These numbers illustrate Gruxi's potential and should be considered directional; real-world results may vary depending on deployment environment, network conditions, and workload.
- CPU: AMD Ryzen 9 9950X3D 4300MHz
- Memory: DDR5 4800 MHz
- Storage: Samsung 9100 PRO 4TB
- Operating system: Windows 11
- Tooling: Oha (https://github.com/hatoo/oha)
- Tested version: 0.1.7
- TLS: Disabled (to focus on raw request handling)
- File cache: Enabled
- Content type: Static file (default index.html for Gruxi)
- Concurrency: 100
- Request count: 1,000,000
- Operation mode: "ULTIMATE" (request/response logging disabled except for errors)
- Command executed:
.\oha-windows-amd64.exe -c 100 -n 1000000 --no-tui http://127.0.0.1
- Requests per second: 173,309 req/second
- Memory usage under load: 10 MB
- CPU utilization: 30 %
Note: These results reflect local lab conditions with no external network traffic. Performance may differ under real-world scenarios with TLS enabled, external clients, and varied content types.
There are several ways to run Gruxi, depending on your environment and deployment preferences.
- Using prebuilt binaries (recommended for maximum performance)
- Running with Docker
- Docker Compose
Detailed instructions are available in the documentation for Grxui..
Gruxi is free to use under the MIT license. Direct support is not included by default.
If you require commercial support, consulting, or wish to sponsor development, please contact:
The source code in this repository is licensed under the MIT License. You are free to use, modify, and distribute the code in accordance with that license.
However, the following are not covered by the MIT License and remain the exclusive property of the Gruxi project and its author:
- The Gruxi name and brand
- Logos, icons, and other graphical assets (including files in the
assets/directory) - Screenshots and promotional images
- Documentation content and website design at gruxi.org
You may not use the Gruxi name, logo, or branding to imply endorsement of or affiliation with your own projects without prior written permission. If you fork or redistribute this software, please rename it and use your own branding.
For licensing inquiries or permission requests, contact: contact@gruxi.org
