Looking Towards the 1.0.0 Release

Post date: 20 Mar 2026

As we approach the 1.0.0 release of Gruxi, it’s a good time to reflect on where we are, what we’ve accomplished, and where we’re headed.

Current State of the Project

Gruxi has come a long way since its inception at the beginning of 2025. We have a solid core that handles HTTP requests very efficiently, a growing set of features that covers the most common use cases, and a codebase that is designed for maintainability. All features are built with a common mindset: keep things simple and easy to understand while still being powerful enough for production use.

We have also focused on making it easy to get started with Gruxi. The documentation has been improved, and we have added more examples and guides to help new users get up and running quickly. We have also added things like a Docker image and Debian packages to make it easier to deploy Gruxi in various environments. This is in line with our goal of making Gruxi easy to get started with and accessible to a wide range of users.

Performance has been a key focus throughout the development process. We have made significant improvements in request handling, reduced latency, and optimized resource usage. We are especially proud of the very tight latency curve, with very few outliers. To us, that tells the story of a predictable and stable system, which is what we are aiming for. Even at a few thousand concurrent connections, we are seeing very good performance with low CPU usage. This is a testament to the efficiency of our async execution model and the careful attention we have paid to minimizing allocations on hot paths.

Performance is not just about raw throughput; it’s also about predictability and stability under load. But we are not just focused on benchmarks, which can be misleading. We want to ensure that Gruxi performs well in real-world scenarios, and that it can handle the demands of production workloads with ease. That is one of our core motivations for building Gruxi: to create a web server that can be trusted to perform well under real-world conditions, not just in synthetic benchmarks.

On the downside, we have yet to truly prove Gruxi in production environments at scale. While our internal testing and benchmarks are promising, real-world usage will be the ultimate test of Gruxi’s robustness and reliability. We are actively seeking early adopters and production users to help us validate Gruxi in a variety of environments and workloads. We are also working on improving our monitoring and observability features to make it easier for users to understand how Gruxi is performing in their specific use cases.

In summary, we are very happy with the current state of the project. We have a solid foundation to build on, and we are excited about the future of Gruxi. We are looking forward to getting more users and, in turn, more feedback, which will help us continue to improve and evolve Gruxi in the coming months and years.

How we feel about the 1.0.0 release

Feature-wise, we are very close to what we want to have in the 1.0.0 release. We have a few remaining features and pieces of functionality that we want to add, but they are not critical for the initial release. We are prioritizing stability and performance over adding new features at this point, as we want to ensure that the core functionality of Gruxi is solid before we start adding more features.

We are also focused on improving the documentation and making it as comprehensive and user-friendly as possible. We want to make sure that users have all the information they need to get started with Gruxi and to use it effectively in their projects.

Moving toward a 1.0.0 release always comes with mixed feelings. On the one hand, it’s a significant milestone that represents a level of maturity and stability in the project. It’s a signal to users that Gruxi is ready for production use and that it has reached a certain level of quality. On the other hand, it can also create pressure to meet certain expectations and to deliver on promises that may not be fully realized yet.

Overall, we fully understand that the 1.0.0 release is not the end, but rather a phase change that indicates we are ready to start getting more users and feedback, which will help us continue to improve and evolve Gruxi in the coming months and years. We are excited about the future of Gruxi, and we are looking forward to seeing how it will be used in the wild.

What is next for Gruxi

We have many features on the drawing board for later releases, such as:

• HTTP/3 support
• Metrics and observability improvements
• Rate limiting
• Improved redirects and rewrites
• Easier deployment options (RPM, MSI, etc.)
• Improved proxying and load balancing features
• Web Application Firewall (WAF) features
• User management
• And more.

User input is key to shaping the future of Gruxi, so we encourage users to share their feedback and feature requests with us. We are committed to building a web server that meets the needs of our users, and we are always looking for ways to improve and evolve Gruxi based on user feedback.

Thanks for reading, and we look forward to sharing more updates and insights about the development of Gruxi in the future!

• Brian Søgård Jensen