ecarjat wires Mike up to KairosVista's own hardware

A self-hosted production deploy path lands, with some quiet reliability fixes bolted on along the way.

infrastructuresecurity

ecarjat has stood up a deployment pipeline that builds Mike's backend and frontend as proper production containers and ships them to KairosVista's in-house servers, behind a public gateway. It's a clear signal of a fork being run for real users on infrastructure the team controls, rather than a hosted cloud setup.

Bundled in are a handful of stability fixes that are arguably more interesting than the plumbing: the server no longer crashes when an authentication check hiccups (it politely returns a temporary error instead), background failures in request handling get caught rather than swallowed, and a sharing-permissions query that wasn't matching the right records has been corrected. Several of these have since been addressed upstream too - so anyone running their own fork should check what they still need.

So what Useful for legal-ops teams considering whether to self-host Mike on internal infrastructure rather than rent it from someone else's cloud.

View this fork on GitHub →

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

Commits in this thread

5 commits from ecarjat/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
f78465c3 Add Gitea deployment pipeline Emmanuel Carjat 2026-05-09 ↗ GitHub
25856c45 Fix frontend Supabase build secrets Emmanuel Carjat 2026-05-09 ↗ GitHub
37141941 Fix Supabase storage S3 region Emmanuel Carjat 2026-05-09 ↗ GitHub
106c9931 Revert "Fix Supabase storage S3 region" Emmanuel Carjat 2026-05-10 ↗ GitHub
This reverts commit 3714194199699729c9e0e3d9dacc75c60704afee.
f64dbcd5 Point frontend build at public proxy URLs Emmanuel Carjat 2026-05-10 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-396.md from inside the repo you want the changes in.

⬇ Download capture-thread-396.md