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.

infrastructuresecurity

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.

So what Relevant if you're a legal-ops lead or GC who'd only consider an AI tool that lives inside your own walls, not in someone else's cloud.

View this fork on GitHub →

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

Commits in this thread

4 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
fe094a66 Merge pull request #1 from elitan/codex/remove-supabase-better-auth-kysely Johan Eliasson 2026-05-15 ↗ GitHub
refactor(db): replace supabase with better auth and kysely

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-414.md from inside the repo you want the changes in.

⬇ Download capture-thread-414.md