projects · the platform

The machinery the apps stand on.

None of the other projects carry their own edge security, monitoring, alerting, or theme. They plug into shared machinery — built once, hardened by incident, and documented as the patterns this site is named for. This page is the machinery's own case study.

The edge

Private by default, public by exception

One proxy for every app. The few public routes — this site and the commute app's API — arrive through a managed CDN + WAF and an outbound-only tunnel, so the origin has no inbound port to find. Every other app answers only to devices on the private network: Tailscale identity is the login, and a stranger gets a 404 at the edge before the request ever reaches the origin.

the request path
Internet the public CDN + WAF Cloudflare Outbound tunnel Cloudflare Tunnel Proxy + gate Caddy · gate runs first Tailnet only Tailscale identity The apps signal · security…
Sanitized by design — the internal reference carries the ports, hostnames, and orderings.

The rest of the machinery

Boring on purpose

Monitoring on four axes

Alive, correct, drifted, wasteful — per-project smoke tests, deploy and image drift checks, and lifetime-average resource watching, with per-job heartbeats and outside-in synthetics in Grafana Cloud.

One notifier

A single shared library owns "send me an email"; every job uses it. Alert plumbing is written once, tested once, rotated once.

One design language

The token layer from the styleguide skins first-party apps, server-rendered dashboards, and third-party tools alike — this site included.

Deploys a person can hold

Git as transport, checkouts as artifacts, drift checks keeping the simple path honest. This very site deploys by git pull.

The second engineer is a model

An AI pair helps build and run the platform — under the AI-leverage pattern: a hard spend cap, git review, and smoke tests that don't care who wrote the change.

Proof

The platform documents itself

The styleguide renders from the live design tokens; the patterns pages carry dated, statused decisions; and the whole site runs on the same machinery it describes.

the styleguide — living documentation
The styleguide's masthead: One crimson, dusk and cream
Swatches on the styleguide are read from the computed stylesheet at render time — the documentation cannot drift from the truth.
Copied