jpbreda/mike

A fork exploring how to run Mike on AI you host yourself, not just the commercial cloud services.

Early and quiet - a single focused thread of work, last touched in early May, with the fork currently sitting in sync with upstream.

View on GitHub →

This is jpbreda's take on Mike, and the through-line is control over where the model runs. Rather than being limited to the commercial cloud backends Mike ships with, the work here opens a path to point Mike at a model instance you host on your own hardware - an OpenAI-compatible local endpoint sitting alongside the existing options.

The why is easy to guess for anyone in legal tech: a self-hosted model means sensitive matter data never has to leave your infrastructure. jpbreda hasn't wrapped a rebrand or a niche around this - it's a focused, infrastructure-minded change to who Mike can talk to.

There's not much else diverging here yet. If the self-hosting angle matters to you, this is the fork to watch, and GitHub is the place to see how far along it actually is.

What's in it

Direction

infrastructureintegration

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

Threads of work (detailed view)

3 threads have been distilled into posts.

jpbreda adds vLLM as a third LLM provider alongside Claude and Gemini

This fork wires a self-hosted vLLM endpoint into Mike's provider system, letting operators swap the model layer to a local inference server instead of routing all requests through Anthropic or Google. The PR closed without merging upstream on May 10.

Pull requests (detailed view)

2 PRs touch this fork — inbound (filed against it) or outbound (filed from it). State icons match the editorial dashboard.

⛔ Closed without merge (2)