Dispatch 120
Week ↗

Launching Cognitive Companion and shipping two APIs

Tuesday was one of those days where a website goes live and the infrastructure catches up at the same time. I launched cognitivecompanion.dev today, the whole site from scratch. React + Vite project, docker…

Commits
13
Systems
3
Read
2min
Product capture

Ops-Center — user dashboard.

Tuesday was one of those days where a website goes live and the infrastructure catches up at the same time.

I launched cognitivecompanion.dev today, the whole site from scratch. React + Vite project, docker compose, nginx config, the works. The initial commit was 9,522 lines across 35 files, then I went through the day refining it. Updated the hardware page to rename the product as the Genesis Flow Z13, rewrote the architecture pages to reflect the Cognitive Companion 1L design, and added an animated neural network background that actually looks decent. Also dropped robots.txt, sitemap.xml, and a Formspree setup guide so the contact form isn't just a dead end.

On the ops-center side, two things shipped that I've been meaning to get to for a while. First, a proper image generation API with OpenAI SDK compatibility. That was a 3,321-line addition across six files, including full docs. The goal is straightforward: developers can call it the same way they call OpenAI's images endpoint, which removes a whole category of integration friction.

The initial commit was 9,522 lines across 35 files, then I went through the day refining it.

Second, I added model categorization to the LiteLLM API layer. The distinction between BYOK (bring your own key) models and Platform models matters for routing, billing, and access control, so separating them at the API level was the right move. That was about 791 lines plus a deployment summary in the docs. Both features got their CLAUDE.md updated and integration guides written so people aren't guessing.

There was also a smaller but annoying fix for API key and LLM provider key caching issues. Keys weren't refreshing properly, which meant stale tokens were getting used. The fix touched the backend and three frontend components, about 145 additions and 132 deletions. Nothing glamorous, but it's the kind of thing that silently breaks integrations until someone actually tries to rotate a key.

uc-cloud got the corresponding documentation updates and a big ops-center bump. The main commit was nearly 19,000 lines added across 54 files, mostly docs, config changes, and monitoring extensions. The kind of update that makes git blame cry but keeps the platform coherent.

The day added up to a website going live while the API layer got two features people have been waiting for. Not a record-breaking day, but the kind of Tuesday where everything actually ships.

Also in the frame

Real product captures — click any to enlarge.

ops center
uc cloud
uc cloud