What actuallyruns the OS.
Six layers, one repo, zero standing servers. The reason eleven divisions ship from one operator is the stack — not the willpower. Below is what it actually is.
From spine to companion.
Spine
Next.js 16 App Router on Vercel. One repo, one operator. Eleven divisions ship from the same publishing pipeline so the voice and the visual stay locked.
Voice + Validation
Anthropic Claude + DeepSeek V4 routed through a 10-gate phrase tracker. No chapter ships unless every gate passes — including a cross-book repetition floor.
Render + Storage
Sharp + SVG composer for covers, ffmpeg for podcast video, Polly generative for narration. Output lands in Cloudflare R2 (free egress) and AWS S3 mirrors for KDP.
Commerce
Stripe for checkout, Supabase + Postgres for catalog state, R2-presigned URLs for delivery. Zero middleware between sale and download.
Cluster
Vast.ai on-demand boxes for the catalog blitz. 16-core CPU at $0.20/hr renders 636 books in 12 hours. No standing servers, no idle bill.
Companion
A retrieval AI trained on the whole stack — every book, every framework, every property — so it routes you to the exact one that breaks your block.
See it operating.
The catalog is live. The companion is online. The stack runs in public, every day.