mikeOnBreeze/mike-oss
Local-only Mike fork: Supabase and R2 replaced with a JSON file and the filesystem
mikeOnBreeze/mike-oss replaces all cloud dependencies in Mike with local equivalents. Supabase Postgres, Supabase Auth, and Cloudflare R2 are removed in a single commit; state persists to backend/data/local-db.json and documents go to backend/data/storage/. Auth accepts a single hardcoded local user via bearer token. Nothing leaves the machine except LLM API calls.
The author is explicit about the purpose: they are a personal injury lawyer who wants to evaluate the tool against real client materials without pushing them to a third-party cloud. The fork is a desktop proof-of-concept, not a multi-user deployment. The README itself says to use upstream for production.
What's in it
- Runs without a cloud database Replaces the managed Postgres dependency with a local data store, so Mike can run without an external database account.
- No hosted auth required Strips out the dependency on a hosted authentication provider, simplifying setup for self-contained deployments.
- Local file storage instead of object storage Uses the local filesystem in place of cloud object storage, keeping uploads and assets on the machine running Mike.
- Self-contained deployment The combined effect is a Mike you can run end-to-end on your own infrastructure, with no third-party services in the loop.
Direction
infrastructure
Activity
Threads of work (detailed view)
mikeOnBreeze pulls Mike off the cloud completely
A personal injury lawyer rebuilt Mike to keep client files on the laptop and nowhere else.
Supabase and R2 stripped out; JSON file and local filesystem take their place
mikeOnBreeze forked Mike to run entirely on a laptop without any cloud dependencies. One commit removes Supabase Postgres, Supabase Auth, and Cloudflare R2, replacing them with a hand-rolled JSON store and direct filesystem reads/writes. The author is a personal injury lawyer who doesn't want client materials leaving their machine.