About this site
This is a real, multi-page static site — clean URLs (/about/ served
from about/index.html), shared assets, an SVG logo — all delivered by
one small C binary.
How a request is served
When your browser asks for /about/:
1 · TLSportico terminates TLS 1.3 with a Let's Encrypt cert it issued itself via ACME (HTTP-01 on :80).
2 · Routethe directory request resolves to
about/index.html under the docroot.
3 · Readthe file is read off disk on portico's async I/O path (io_uring where available), off the event loop.
4 · Encodeif you sent Accept-Encoding: br, portico serves the precompressed .br sibling; else .gz; else raw.
The certificate is the interesting part
There is no certbot cron job and no nginx in front. portico runs the full RFC 8555 flow itself — directory, account, order, HTTP-01 challenge, finalize, download — writes the cert to disk, and hot-reloads it. A background thread renews well before expiry, with zero downtime.
It was first proven offline against the Pebble test CA, then against Let's Encrypt staging, then production. The cert serving you this page right now is a real, browser-trusted Let's Encrypt certificate.