Zeroserve 0.1 hit GitHub on June 6, 2026, promising a zero‑config HTTP server that can be extended with eBPF programs.
The project ships a single binary (about 2 MB) and a Rust‑based CLI. It listens on port 80 by default, auto‑detects the host IP, and exposes a /ebpf endpoint where users can upload or reload eBPF bytecode without restarting. The source lives at https://github.com/su3/zeroserve and is released under the MIT license. The initial build targets Linux kernel 5.10 and newer, and the README lists a basic benchmark: serving static 1 KB files at roughly 850 kreq/s on a single‑core VM, comparable to lightweight servers like Caddy.
For developers who already use eBPF for observability, the ability to script request handling directly in the kernel could eliminate a layer of proxy configuration. It also lowers the barrier for experiments that would otherwise require a full web framework. However, the performance claim rests on a single test case, and the server lacks TLS management, so it fits niche use cases rather than production front‑ends.
In short, Zeroserve is a tidy proof‑of‑concept that blurs the line between traffic routing and kernel‑level instrumentation, but it remains to be seen whether the trade‑offs pay off beyond hobby projects.