I built Sentinel , a small self-hostable security monitoring platform, as three separate repos:
sentinel-api : Node 22, TypeScript, Express 5, PostgreSQL, Prisma 7. It ingests security events and scan results, raises alerts from threshold rules, tracks incidents and streams alerts live over SSE.
sentinel-dashboard : Next.js. Live alert feed, events explorer, incident timeline, scan reports, admin screens.
sentinel-scanner : a Python CLI that scans a site you own, checks dependencies, analyses logs and writes incident post-mortems, then sends results to the API.
Everything worked on my laptop with Docker Compose. Putting it online for free (Neon for Postgres, Render for the API, Vercel for the dashboard) is where the interesting bugs were. This is the account of those, in the order I hit them.
The design decision that shaped the deployment
The dashboard keeps the short-lived access token in memory only . The long-lived refresh token lives in an httpOnly; Secure; SameSite=Strict cookie set by the API.…