How this site is built

A quick tour of how this site works under the hood.

The public side

Every public page — this post included — is plain HTML built ahead of time and served from a global CDN (CloudFront in front of S3). There’s no server to keep running, so it’s fast and costs almost nothing.

The private wing

Anything behind login is reached through an authenticated API. Private content never sits in a public bucket; you only get it after signing in. Accounts are invite-only — there’s no public sign-up.

Why this shape

• Cheap: pay-per-request, scales to near-zero when idle.
• Secure: the public/private split is physical, not just a UI toggle.
• Low-ops: no servers, managed auth, infrastructure defined as code.

If you want the full breakdown, ask me — I keep the project plan as a versioned deck.