How this is
built.
This site isn't a template: it's a system with a private panel, custom monitoring, and a payment gateway. Here's its anatomy (layer by layer) and the reasoning behind each decision.
External services
Decisions and trade-offs
The private panel needs live data and per-request auth. Public pages are cached at the edge, so I pay for SSR only where it pays off and serve the rest almost for free.
Logins without touching the database and zero session infrastructure. The blind spot - revocation - I solved with a signed sid inside the token and a device table, without giving up the JWT.
SQLite at the edge: minimal latency, replicas, and a simple mental model for a domain that does not need massive concurrency. Drizzle keeps the schema typed and migrations in git.
The Hobby plan limits you to one daily cron, useless for uptime. An external cron hits a token-authenticated endpoint every few minutes; Vercel's cron becomes a safety net. The platform's constraint was the start of the design, not the end of it.
Telemetry, session logging, and notifications must never take down the main flow. If an observability subsystem fails, it degrades silently instead of breaking the experience.
All the code lives in a public repository as a portfolio. The decisions here are not theory: each one has its commit, its tests, and - where it applies - its security finding documented at /security.