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.

infrastructuresecurity

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.

So what Worth a look for anyone who cares where client logins and case data actually live - this is a move toward owning that stack rather than renting it.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

3 commits from elitan/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
dce1302e refactor(db): replace supabase with better auth and kysely Johan Eliasson 2026-05-15 ↗ GitHub
42d38bda refactor(db): clarify kysely query adapter Johan Eliasson 2026-05-15 ↗ GitHub
8923b301 refactor(db): rename kysely instance to db Johan Eliasson 2026-05-15 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-448.md from inside the repo you want the changes in.

⬇ Download capture-thread-448.md