brainbytes-dev packages Mike to run on your own servers

The fork adds everything needed to self-host Mike instead of relying on the original author's hosting.

infrastructure

brainbytes-dev has bundled Mike into a container setup - a standard, portable way to ship an app so it runs the same on any server. Point it at Coolify (an open-source tool for hosting apps on your own machines) and the whole system stands up: the app, its interface, file storage on Cloudflare R2, a Supabase database, and keys for three AI providers (Anthropic's Claude, OpenAI, and Google). The recipe also installs LibreOffice, the free office suite, so the server can open and convert Word, Excel, and PowerPoint files on its own.

A follow-up fixes a real bug that broke the first build, so the recipe now works cleanly end to end. There's one caveat: secrets and configuration are left to whoever runs it, so this is a starting point rather than a turnkey install.

So what Firms and legal-ops teams that can't send matter data to someone else's cloud now have a working blueprint for running Mike on infrastructure they control.

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

Commits in this thread

2 commits from brainbytes-dev/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`95742559`	feat(deploy): add Dockerfiles and docker-compose for Coolify self-hosting	BrainBytes	2026-06-24	↗ GitHub
`93cc2b3e`	fix(backend): multi-stage build so tsc is available during npm run build	BrainBytes Studio	2026-06-24	↗ GitHub

SHA

Subject

Author

Date

95742559

feat(deploy): add Dockerfiles and docker-compose for Coolify self-hosting

BrainBytes

2026-06-24

↗ GitHub

93cc2b3e

fix(backend): multi-stage build so tsc is available during npm run build

BrainBytes Studio

2026-06-24

↗ 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-689.md from inside the repo you want the changes in.