Zeroserve: A zero-config web server you can script with eBPF

A tiny new website server drops with big promises — and commenters instantly smell chaos

TLDR: zeroserve is a new lightweight website server that says it can serve a whole site from one bundled file and let tiny scripts control every request. Commenters were torn between impressed curiosity and deep suspicion, with AI-authorship, trust, and the weird tarball packaging becoming the real story.

A new project called zeroserve is pitching a very bold fantasy: upload one bundled website file, press go, and let a tiny server handle the rest. It promises modern security, fast performance, easy updates, and even little built-in programs that can rewrite pages, check logins, block spammy visitors, or send traffic to another app. In plain English, the creator wants to replace the usual giant pile of config files with one package and one script that controls everything.

But the real fireworks are in the comments, where the crowd is split between "this is clever" and "absolutely not, show receipts first". One skeptical reader basically said the whole thing feels too polished and too synthetic, especially because the post openly says it was co-written by AI. That instantly turned the launch into a trust drama: not just "is the server fast?" but "is any of this real enough to trust?" Another commenter liked the idea but wanted friendlier programming tools and seemed disappointed it wasn't some magical system-level speed demon. Meanwhile, one person delivered a brutal reality check by saying focusing on serving simple website files might miss how people actually run sites today.

And then came the funniest mini-meltdown of all: "Why a tarball?" In other words, why wrap an entire site into one giant package file at all? That tiny question became the thread's unofficial meme, because it perfectly captured the mood: people aren't just debating speed, they're side-eyeing the whole vibe. The project may be fast, but the comments moved faster.

Key Points

  • The article presents zeroserve as a zero-configuration HTTPS server that serves websites directly from a single tarball with HTTP/2, TLS 1.3, hot reloads, and a small memory footprint.
  • zeroserve uses userspace eBPF programs as request middleware, allowing routing, rewriting, authentication, rate limiting, and reverse proxying without a separate configuration file.
  • The system treats the eBPF program as the full server configuration, contrasting this with nginx and Caddy’s combination of declarative configuration and optional scripting.
  • Files are served directly from indexed byte ranges inside the tarball, with deployments and reloads handled by swapping the archive and sending SIGHUP.
  • The implementation uses io_uring for all network and disk I/O and executes eBPF scripts in userspace via async-ebpf and uBPF, with JIT compilation and pointer-cage-based sandboxing.

Hottest takes

"the spark does not ignite on my side because it feels too artificial" — bflesch
"I think I'd feel more comfortable if I could drop an .rs file into the eBPF dir instead of a .c one" — mmastrac
"Why a tarball?" — rashkov
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.