The fork adds everything needed to self-host Mike instead of relying on the original author's hosting.
brainbytes-dev/mike
A self-hostable spin on Mike, packaged so you can stand the whole stack up on your own servers with Docker.
This is brainbytes-dev's fork of Mike, and so far it's pointed squarely at one thing: making Mike easy to run on infrastructure you control. Where the upstream project leaves deployment largely to you, brainbytes-dev has wrapped the backend and frontend into containers and stitched them together so the whole thing can come up with a single orchestrated setup - the kind of arrangement that plays nicely with self-hosting platforms like Coolify.
If you tried it today, the draw isn't a new feature inside the product - it's the packaging around it. You'd get a container-based deployment path: a backend service and a Next.js frontend wired to talk to each other, ready to sit on your own box rather than a managed host. For legal teams that need to keep an AI assistant inside their own walls, that operational story is the pitch.
It's early. The fork sits just two commits ahead of upstream, all of it deployment plumbing rather than product changes, so there's no rebrand or legal-tech niche staked out yet. If you're curious about the self-hosting setup specifically, it's worth a click through to GitHub.
What's in it
- Container-based self-hosting The backend and frontend are each containerized, so you can run Mike on your own infrastructure instead of a managed host.
- One-shot stack orchestration A single orchestrated setup brings the backend and Next.js frontend up together and wires them to communicate.
- Coolify-friendly deployment The packaging suits self-hosting platforms like Coolify, aimed at teams that want to keep the whole thing in-house.
Direction
infrastructure
Activity
Threads of work (detailed view)
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.