The most secure system is one with nothing to attack.

This site has no database, no admin panel, no login, no API endpoints, no sessions, no cookies. Just static HTML served from the edge. If an attacker compromises the server, they find only public HTML files — the same content visitors see.

The Architecture of Nothing

Traditional web applications are castles. They have walls, gates, drawbridges, and guards. Every one of those is an attack surface. A wall can be climbed. A gate can be forced. A guard can be bribed.

This site is different. It’s not a castle — it’s a void. There’s nothing to attack because there’s nothing here except the content you’re reading right now.

// The entire attack surface
fn serve(path: &str) -> Response {
    static_file(path) // That's it. That's the whole thing.
}

Defense in Depth

Even with nothing to attack, we add layers:

  • Content Security Policy enforces script-src 'none' — the browser will refuse to execute any JavaScript, period
  • Raw HTML is stripped from markdown during build — even accidental <script> tags can’t survive
  • HSTS with preload ensures HTTPS-only, forever
  • All CI/CD actions are pinned to immutable commit SHAs

The result: a site that is technically impossible to hack unless there’s a vulnerability in Rust, Cloudflare, or GitHub itself.

Why Rust?

Memory safety. A static site generator doesn’t need to be fast — but it does need to be correct. Rust guarantees that at compile time.

No garbage collector pauses. No null pointer exceptions. No buffer overflows. Just correct code that does exactly what it says.

The binary compiles in seconds and generates the entire site in milliseconds. But that’s a side effect, not the goal.