juanjo is unbundling Mike from Supabase, rebuilding it on a self-hostable local stack you can run on your own machine.
This fork of Mike is a focused infrastructure project: juanjo is methodically swapping out the hosted services Mike depends on and replacing them with components that run locally. The work is plan-driven - specs and implementation plans go in first, then the code follows - and it's organised into discrete phases that each close cleanly before the next begins.
So far the trajectory is clear. A first phase replaced the Supabase-backed auth and database layer with a Postgres-and-cookie-based setup, sweeping every call site on both frontend and backend. A second phase has begun on object storage, moving away from a hosted bucket toward a local S3-compatible service. Alongside the rewiring, juanjo has built up a project-level scaffolding of runbooks, ADRs and a deferred-work tracker - the kind of housekeeping that suggests this is meant to be picked up and contributed to, not just run solo.
If you want a Mike you can stand up entirely on your own laptop or your own infrastructure - no third-party accounts in the loop - this is the fork to watch.
infrastructureintegration
juanjo ↗ analysis ↗ GitHub The second leg of juanjo's self-hosting push swaps a cloud file-storage dependency for something that runs entirely on the developer's own machine.
The fork is now Supabase-free - no code paths, no env vars, no setup steps pointing at it.
The frontend now talks to its own backend through a cookie, not a hosted auth service - and the whole stack boots from a single command.
The fork's database rewrite is done - every backend route now talks to plain Postgres through a different toolkit, with the frontend none the wiser.
After proving the pattern on a single slice, juanjo ported every remaining database call in the backend to a self-hosted setup.
A plan-driven excision of the hosted backend in favour of a self-contained local stack - and the planning docs are the real artifact.
One docker command now stands up the whole stack - no third-party accounts, no cloud sign-ups, no credit card.
The fork can now be brought up end-to-end with one command and no third-party accounts.
juanjo · opened 18d ago · merged 18d ago by juanjo