What this site is built with.
A short, honest accounting of the stack behind the page you're reading — including what we chose not to use, on purpose.
Frontend and backend in one project — server components by default.
A custom design system via CSS variables — no Tailwind, no CSS framework.
A single document store, no separate cache layer.
Serverless/edge, first-party Next.js support, one weekly cron job.
No third-party auth provider.
Self-hosted at build time via next/font — no runtime request to a font CDN.
Deliberately not used
Each of these was a considered omission for a project at this size, not an oversight — fewer moving parts means fewer things that can quietly break.
Compliance and craft, not just code
Cookie consent with real Global Privacy Control handling, a live status page, a published security.txt, an accessibility statement, and admin audit logging are all part of the same build — see Security & Trust for the full picture.