This site: overview
A public, live view of how this site is built, protected and monitored. Not a Cloudflare dashboard pasted in — it is my own observability: the same discipline I apply in production, exposed for anyone who wants to inspect it.
Map of this section
Security, evidence and telemetry are facets of the same project — each page covers one layer:
- Security — posture, headers and why
- Honeypot — decoy endpoints, ATT&CK correlation and the log of whoever touches them
- Cloudflare — what the Internet tries against the whole zone, and what gets stopped
- Evidence — everything verifiable, generated at build
- Performance — traffic, cache, latency and Core Web Vitals
This site, in numbers
Four different sources, not a funnel: the firewall sees the whole zone — including challenges solved by legitimate visitors — while the honeypot only sees the decoy endpoints. These numbers do not subtract, and they do not have to decrease left to right.
Architecture
What reaches your browser is static: HTML/CSS generated at build, no database, no sessions. The little that genuinely needs a server (honeypot, password checker, telemetry) lives in an isolated Cloudflare Worker with no personal state — and the site stays whole without it. Everything at Cloudflare's edge, deployed automatically from GitHub.
📐 The why behind each architecture decision — Astro with no client-side framework, the monorepo with the Worker kept separate from the static site — is told in the project that serves this site. See the This site project →
Stack
The pieces and what each one does:
- Frontend
- Astro
- Backend
- Cloudflare Workers
- Edge / CDN
- Cloudflare
- Hosting
- Cloudflare Pages
- State
- Workers KV
- CI / Deploy
- GitHub Actions
- Source
- GitHub