rglauco/mike
rglauco is reworking Mike into a fully self-hostable legal AI, free of cloud dependencies for teams that need to keep everything in-house.
This fork, maintained by rglauco, takes Mike in a clear direction: making it runnable entirely on a team's own infrastructure. Where the upstream project leans on hosted services, this version is being reshaped so a legal team can stand it up on their own hardware, with their own database, their own model runtime, and their own file storage.
The work so far points at firms or in-house legal groups that either can't put client data on third-party platforms or simply prefer not to. Alongside the self-hosting push, rglauco is keeping pace with upstream Mike, pulling in fixes and security work as they land.
It's early, and the fork hasn't strayed far from upstream in surface behaviour - but the deployment story is the thing to watch here. If you're evaluating Mike for an environment where the cloud isn't an option, this is the variant worth a closer look.
What's in it
- Self-hosted deployment path A containerised setup with a local database, so the whole stack can run on your own servers without depending on a hosted backend.
- Local language models Support for running models on your own machine rather than calling out to a cloud provider - useful when client data can't leave the building.
- On-disk file storage Documents and uploads live on local storage instead of a third-party object store, rounding out the cloud-free deployment story.
- Tracking upstream Mike rglauco is actively merging in upstream fixes and security work, so the fork keeps pace with the main project rather than drifting.
Direction
infrastructuresecurity
Activity
Threads of work (detailed view)
rglauco cuts Mike loose from Supabase
A self-hosted deployment path for teams that can't or won't run their legal AI on a third-party backend.
rglauco wires Mike for self-hosting
A fork aimed at keeping legal data on your own hardware just got its first half.