Stack
Edge-first by default. Every product runs on Cloudflare Workers, talks to Neon Postgres through Hyperdrive, and pulls language work from a three-tier LLM cascade. Everything below is in production right now across the brand surfaces — not a roadmap, not a wishlist.
Why this stack
Every API runs on Workers, not on a single-region container or serverless function. We get sub-100ms TTFB to every user on Earth without managing capacity, and cold starts vanish because there are no cold starts. The cost: no fs, no process.env, no Node built-ins. Worth it.
Hono is the only router we found that treats Workers as a first-class runtime and not a polyfill target. The whole framework is smaller than Express's middleware loader. Type-safety on routes and middleware is real, not vibes.
Postgres because it's still the most reliable thing we can run a business on. Neon because branching gives every PR a real database. Hyperdrive because connection-pooling from the edge is otherwise a load-bearing footgun — we get a sane env.DB binding and no connection storms.
We sign and verify JWTs ourselves with the Web Crypto API. No jsonwebtoken, no framework auth helpers. The verification path is ~40 lines, every line is auditable, and we never get bitten by a transitive CVE in a parsing library we never used.
Tier 1 is Anthropic for anything where output quality is product-defining. Tier 2 is Grok for high-volume work that tolerates more variance. Tier 3 is Groq when latency dominates correctness. All three go through Cloudflare AI Gateway so we get one rate-limit ceiling, one cache, one set of logs, and an instant failover path if any provider goes dark.
Pages serve static HTML from the edge. JavaScript loads only where it earns its weight — pulse hydration, contact form, video playback. This page you're reading is under 5KB of JS. Most landing-page React bundles are 30× that for less.
No secrets in GitHub Actions repo settings, no secrets in wrangler.jsonc vars, no secrets in source. CI authenticates to GCP via WIF (no service-account JSON), fetches what it needs at job start, exports to step env, and the secrets are gone when the job ends. Rotation is one place, not seventeen.
The pulse data on the landing page is a build-time JSON file, same origin, no auth — because there's nothing to auth. Operator endpoints stay behind authenticated Admin Studio routes. The public surface advertises proof, never plumbing.