juanjo finishes ripping Supabase out of Mike's backend
After proving the pattern on a single slice, juanjo ported every remaining database call in the backend to a self-hosted setup.
This is the bulk phase of a larger move: getting Mike to a state where a developer can run the whole thing on their laptop without signing up for any third-party accounts. The original codebase leaned on Supabase, a hosted service that bundles a Postgres database with user authentication. juanjo's fork replaces that with a local Postgres instance and Drizzle, a lightweight library that lets the code talk to the database directly.
The interesting part is the scope. Every backend module that previously reached out to Supabase - projects, documents, chat, workflows, downloads, the tabular data views - now goes through the new pathway. Two follow-up fixes landed quickly after the main push, which is honest signal that a translation this broad will leak a few subtle bugs no matter how careful the team is.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?