elitan rips Supabase out of Mike's foundations
The fork swaps its hosted backend for a self-managed login-and-database stack - without rewriting the app on top of it.
Supabase is an all-in-one hosted service that handles both user logins and the database behind an app. elitan has pulled it out of Mike entirely, replacing it with a setup the team runs itself: a dedicated login layer and a query toolkit sitting on a standard Postgres database. In plain terms, the fork no longer leans on a third party to hold its sign-ins and its data.
The smart part is how quietly it went in. Rather than touching every corner of the app, the team built a thin shim that speaks the old service's language on the surface while running the new engine underneath. The rest of the codebase carried on as if nothing changed, which is why a swap this deep didn't turn into a months-long rewrite.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?