Diabolarius tears out the managed backend and rolls his own

One sweeping, AI-assisted rewrite swaps Mike's hosted backend-and-login service for a self-hosted stack Diabolarius now owns end to end.

infrastructuresecurity

Mike normally leans on Supabase, a hosted service that bundles a database and user login so teams don't have to run their own. In a single large commit, Diabolarius rips it out and replaces it with a self-managed database, containerized so the whole app spins up together, plus hand-built signup, login, and account endpoints. To avoid rewriting everything that talked to the old service, the fork bolts on a custom translation layer that mimics the old one's shape - clever as a one-day move, but bespoke plumbing nobody upstream maintains.

It's a fresh-install-only rebuild with no path off existing deployments, and it ships with a placeholder login secret and a few auth rough edges. Worth a look if you're wary of leaning on a managed vendor - but read the code before trusting it.

So what Anyone weighing whether to build legal-AI on a managed backend or self-host will find this a candid, warts-and-all case study.

View this fork on GitHub →

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

Commits in this thread

1 commit from Diabolarius/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
6b8283a5 Mike The Bullshit LegalAI Andreas E 2026-05-05 ↗ GitHub
Co-authored-by: Copilot <copilot@github.com>

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

⬇ Download capture-thread-147.md