hoogvliets ships a hardened backend for upstream review

A sweeping backend disclosure that quietly reveals what a production Mike fork actually looks like under the hood.

infrastructuresecurity

This isn't a feature drop - it's hoogvliets opening the kimono on a forked production codebase, carved into companion pull requests so upstream reviewers can actually digest it. The backend slice alone touches almost everything: app startup, typed configuration, tightened authentication, and a real account-lifecycle story with encrypted per-user model keys, account deletion, restore tokens, and a worker that handles the cleanup.

The chat and AI layer gets the biggest rework. The monolithic tools module is broken into focused pieces - tool schemas, the runner, document context, citations, streaming - and model routing now goes through a dedicated endpoint that handles Anthropic and Gemini, with the older OpenAI-only path removed. Around it sit upgraded document and upload flows, request logging via Pino (a popular Node logging library), and rate limiting on AI calls.

So what Worth a look for anyone running a Mike fork in production - it's a credible reference for what hardening, multi-provider AI routing, and account lifecycle look like at scale.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?