gercyc is moving Mike off the cloud and onto your own servers

This fork rips out the managed-cloud foundation so the whole system can run inside a firm's own walls.

infrastructuresecurity

gercyc has re-platformed Mike away from the hosted services it normally leans on - swapping out Supabase, a managed database-and-login provider, for a setup the fork owner can stand up and run themselves. Storage gets the same treatment: alongside the existing cloud option, the fork now supports MinIO, a self-hosted alternative to Amazon's S3, so documents can live on hardware the firm controls.

That storage piece is a clean, optional add-on. The database switch is a deeper rebuild, and it ships with a home-built login-and-password system rather than the off-the-shelf one it replaces. Useful as a blueprint for anyone wanting to escape managed cloud - but the custom login path is exactly the kind of thing that deserves a proper security look before anyone trusts it with client matters.

So what Worth a look for any firm or legal-ops team that needs Mike running on-premises for data-control or sovereignty reasons - with eyes open about the hand-rolled login.

View this fork on GitHub →

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

Commits in this thread

2 commits from gercyc/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
4c217864 Migrate to pgsql Gercy Campos 2026-05-23 ↗ GitHub
699d40ca Add miniio storage Gercy Campos 2026-05-25 ↗ 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-606.md from inside the repo you want the changes in.

⬇ Download capture-thread-606.md