juanjo is cutting Mike's cord to Supabase
The fork is moving its database and logins off a hosted service and onto plumbing it controls.
juanjo is rebuilding the layer everything else in Mike sits on: the database. Right now Mike leans on Supabase - a hosted service that handles both data storage and user logins. juanjo is swapping that out for a database that runs locally on standard, open-source Postgres, with no third-party account required to get started.
This piece of the work lays the foundation: the full map of what Mike actually stores, from users and projects to documents, chats, workflows and review tables. It's plumbing, not a feature you'll click. But it's the kind of plumbing that decides whether a firm can stand Mike up on its own terms rather than renting someone else's cloud - and every later change in this thread builds on it.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?