rglauco keeps the whole stack in-house

This fork lets you run Mike - models and documents alike - without anything leaving your own hardware.

infrastructuresecurity

rglauco's fork adds two changes that pull in the same direction: privacy and self-hosting. Instead of routing every prompt to a cloud AI provider like Claude or Gemini, Mike can now talk to open models running on your own machine, through tools like Ollama and llama.cpp (both let you run AI models locally rather than calling out to a vendor). Several local models ship as defaults, but you can point it at anything you host.

The second half does the same for files. Documents can now live on local disk as a first-class option instead of a hosted cloud storage service, with short-lived signed links keeping the download experience intact. Cloud storage is still there if you want it - the difference is that you no longer have to.

So what For firms where client confidentiality or privilege makes sending matter data to third-party clouds a non-starter, this is the build to watch.

View this fork on GitHub →

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

Commits in this thread

1 commit from rglauco/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
10d12e77 feat: added ollama provider and local storage for privacy Glauco 2026-05-09 ↗ 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-221.md from inside the repo you want the changes in.

⬇ Download capture-thread-221.md