elitan cuts Supabase out of Mike
The fork swaps a hosted backend-as-a-service for plain Postgres plumbing so Mike can run on someone's own servers.
elitan's biggest move in this run is also the riskiest: ripping out Supabase, the hosted backend platform that handled both the database access layer and user authentication, and replacing it with self-hostable parts - vanilla Postgres, a query builder called Kysely, and an open-source auth library called better-auth. Nearly every backend route and the entire login surface had to be rewritten by hand to make the swap.
The payoff is control: a firm or vendor can now stand Mike up on their own infrastructure without depending on a third-party SaaS account. The cost is that security guarantees Supabase used to enforce inside the database - refusing unauthorised reads at the data layer - are now the application's job to get right. Paired with elitan's other work on local AI models and Docker packaging, this looks like a deliberate push to make Mike something you host yourself.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?