Isolated services
Seven services, one private network, one Caddy edge — no shared state between them.
Private developer infrastructure
A private developer platform, built and run end-to-end.
Auth, private files, scoped API keys, IRC chat, a private booking calendar, and cookieless analytics across isolated services — on a deliberately minimal surface.
Live service status
LIVE · 6/6 online · checked
- Auth Online
- IRC Online
- Files Online
- API Online
- Booking Online
- Analytics Online
These six services are probed live at the public edge. This frontend — server-rendering the page you're reading — sits behind the same Caddy edge and isn't self-probed.
Architecture
Seven services behind one edge.
Every request enters through a single Caddy edge and is server-rendered — the services never face the public internet directly.
How it's built
Decisions you can inspect.
Least-privilege API keys
Scoped bearer keys: a chat client can't touch your files.
Health-gated deploys
Cutover polls a real health gate before shifting traffic — never a blind restart.
Honest observability
Every health card answers one question: is the service reachable?
The stack
Deliberately boring.
Server-rendered, SQLite, no SPA — chosen for clarity and low overhead, not novelty.
- Edge
- Caddy (TLS, routing)
- App
- Node Express EJS Tailwind
- Realtime
- WebSocket (IRC)
- Data
- SQLite
- Ops
- Docker Compose npm-workspaces monorepo
See it running.
The demo signs you into the full platform as a read-only reviewer — every screen, populated with fabricated data, nothing saved. Registration here stays invite-only.