mikeOnBreeze pulls Mike off the cloud completely

A personal injury lawyer rebuilt Mike to keep client files on the laptop and nowhere else.

infrastructuresecurity

Stock Mike leans on hosted cloud services for its database, logins, and file storage. mikeOnBreeze ripped all three out and replaced them with local equivalents that live entirely on the machine running the app. The motivation, stated plainly in the project's notes: a personal injury lawyer who wants to work with client materials without ever pushing them to a third party's servers.

What's notable is the honesty. The fork doesn't pretend to be production-grade for a firm - the login check trusts anyone, file links don't expire, and there's no protection against two people writing at once. The author flags all of this and points anyone who needs a real multi-user setup back to the original project. A couple of the defensive details that usually get lost in a quick cloud-to-local port survived intact here.

So what Worth a look for solo practitioners or small shops who refuse to put privileged client files in anyone else's cloud - but read it as a one-person tool, not a firm deployment.

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

Commits in this thread

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

SHA	Subject	Author	Date
`24d6a86c`	Localize storage: replace Supabase + Cloudflare R2 with local filesystem	mikeOnBreeze	2026-05-04	↗ GitHub
commit body Swaps cloud dependencies for local equivalents so the app runs entirely on a single machine - JSON file for state, local filesystem for document bytes, single default user. Original Supabase schema kept under backend/migrations for reference. Motivation: working with materials (e.g. legal documents) that shouldn't be pushed to third-party cloud storage during local experimentation. For multi-user / production deployments, use the upstream repo at github.com/willchen96/mike.

SHA

Subject

Author

Date

24d6a86c

Localize storage: replace Supabase + Cloudflare R2 with local filesystem

mikeOnBreeze

2026-05-04

↗ GitHub

commit body

Swaps cloud dependencies for local equivalents so the app runs entirely
on a single machine - JSON file for state, local filesystem for document
bytes, single default user. Original Supabase schema kept under
backend/migrations for reference.

Motivation: working with materials (e.g. legal documents) that
shouldn't be pushed to third-party cloud storage during local
experimentation. For multi-user / production deployments, use the
upstream repo at github.com/willchen96/mike.

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-149.md from inside the repo you want the changes in.