elitan makes Mike runnable on a laptop in one command

The fork now stands up its full backend - database, file storage, and a local AI model - with a single docker command.

infrastructureintegration

elitan has been steadily turning Mike into something a solo developer or small team can host themselves, without renting infrastructure from anyone. This change is the keystone: a single configuration file that spins up a Postgres database, a MinIO object store (an open-source clone of Amazon S3 for storing files), and wires them together with the previously added local AI engine. Clone the fork, run one command, and the whole legal-AI stack is running on your own machine.

It completes a thread that started with swapping out the hosted database and hosted AI for local equivalents. The compose recipe ships on non-default ports to avoid clashing with anything else you already have running, which is a small but telling sign that this is meant to be used, not just demoed.

So what Anyone evaluating Mike for an on-premise or air-gapped deployment - common asks from law firms with data-residency constraints - should start with elitan's fork rather than upstream.

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 elitan/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
a0a60f92 fix(local): support docker dev setup Johan Eliasson 2026-05-15 ↗ 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-415.md from inside the repo you want the changes in.

⬇ Download capture-thread-415.md