superweb

DEVELOPER PREVIEW · 2026.10

An HTTP server.
C and assembly.

Serve static files with a bounded memory cache, cached gzip, and native event loops. Built for macOS and Linux ARM64.

Download free Compare page loads

Built by SiteVue

~/projects/siteshell 
# Start serving a directory
$ superweb --root ./public \
    --bind 127.0.0.1 --port 8080 \
    --workers 2

superweb listening
http://127.0.0.1:8080/

# Request a compressed response
$ curl -I --compressed \
    http://127.0.0.1:8080/app.js

HTTP/1.1 200 OK
Server: superweb
Content-Encoding: gzip
One process. Native worker threads.
C11 + assembly ARM64 NEON / x86 AVX2HTTP/1.1 + HTTP/2 TLS via OpenSSL32 MiB / worker Bounded file cache

01 / MEASUREMENTS

Numbers you can inspect.

Method & raw results ↗

Three complete rounds from a separate AWS load generator, before network throttling interrupted the planned five-round run. Four t4g.nano hosts in the same availability zone, two CPU workers each, identical SiteVue files. Median requests per second; higher is better.

16,017 B · home page, gzip
Loading AWS measurements…AWS private network · HTTP/1.1 · 64 connections · 10 s per run

Measured October 17, 2026. These are burst measurements. The fourth round hit a network limit and Superweb recorded nine timeouts; all 78 samples are preserved in the report. Several JavaScript results reach the instance network ceiling; they do not establish a software-speed ranking. See every round, errors, resource counters, and limits. Earlier M5 Max results.

02 / INSTALL

Download. Unpack. Run.

FREE PREVIEW · NO ACCOUNT
macOS Apple Silicon

ARM64

macOS 26+. HTTP/1.1, TLS, HTTP/2.
OpenSSL and nghttp2 bundled.

Download .tar.gz ↓
Linux Graviton / ARM64

AArch64

Ubuntu 24.04 · Graviton2 or newer.
OpenSSL 3, nghttp2, and zlib required.

Download .tar.gz ↓

Or use the installer

Installs to ~/.local. Detects your platform and verifies the archive checksum.

Inspect install.sh ↗ 
curl -fsSLO https://superweb.to/install.sh
sh install.sh

Preview binaries are not Apple-notarized. SHA-256 checksums · Requirements and manual installation · Third-party notices

03 / TRY THE SAME SITE

Four servers. Try your connection.

The public SiteVue build on four separate AWS t4g.nano instances. Same availability zone, OS image, content snapshot, and two CPU workers. Each server handles HTTP and HTTPS directly. Open a timed preview, or run all four in a shuffled sequence.

Superweb C + ARM64 assemblyLoad with timer ↗nginx Event-driven workersLoad with timer ↗Caddy Go · GOMAXPROCS=2Load with timer ↗lighttpd Event-driven workersLoad with timer ↗

t4g.nano: 2 vCPUs, 512 MiB RAM. CPU credits are set to Unlimited on all four. Network distance, burst capacity, and credit usage matter: record them with any comparison. Authenticated SiteVue tools remain on the original site. 

wrk -t2 -c32 -d15s \
  -H 'Accept-Encoding: gzip' \
  http://superweb.superweb.to/

Warm each server first, alternate their order, and use the same path and client settings. The preview timer measures the iframe load event, including browser and network costs. Lazy resources may finish later. Benchmark notes ↗

04 / UNDER THE HOOD

A small, explicit stack.

The hot path is native code. Configuration is a command or a plain text file.

Read the server docs ↗
Native I/O
kqueue on macOS. epoll on Linux. sendfile for large unencrypted responses.
Cache by file version
Up to 512 files per worker. Original bytes, gzip bytes, and complete responses share a 32 MiB budget.
HTTP details included
Keep-alive, ranges, HEAD, conditional requests, SHA-256 content digests, and configurable revalidation.
Current boundaries
No HTTP/3 or Brotli. The Intel macOS preview has no TLS. Read the docs before putting a preview in production.