juanjo cuts Mike loose from the cloud
The fork now runs end to end on your own machine - no hosted accounts, no external storage, one command to start.
Until now, getting Mike running meant signing up for Supabase - a hosted service that handled both the database and user logins - and wiring in cloud storage for documents. juanjo has pulled all of that in-house. The fork now boots from a single command, with the database, the login system, and document storage all running locally. No third-party accounts, no outside dependencies just to get a working copy.
The payoff is control. Anyone evaluating Mike can run the whole thing without handing credentials or client files to an external provider, and a firm that wants to self-host has a far shorter path to doing it. juanjo also wrote up the architecture choices and a first-run guide, so the next person isn't left reverse-engineering the setup.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?