juanjo puts the Supabase exit on the record, warts and all

A new set of decision documents explains why this fork is cutting ties with its hosted backend, and is unusually frank about what still isn't finished.

infrastructuresecurity

Supabase is a hosted service that handled both this fork's database and its user logins. juanjo's latest work doesn't just swap it out for software that runs entirely on a developer's own machine, with no outside accounts needed to get started. It writes down the reasoning: you couldn't develop offline, and the hosted setup tangled logins and data storage together in a way that was awkward to unpick.

What makes it worth a read is the candour. The same record lists what the move left for later, including password resets, email verification, and sign-in through outside accounts, and flatly admits that the app's error messages currently expose internal database details, the kind of leak a security reviewer would flag.

So what Anyone weighing whether to move a legal tool off a hosted platform onto infrastructure they control will find a rare, unvarnished worked example here.

View this fork on GitHub →

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

Commits in this thread

2 commits from juanjo/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
ac9ea169 chore: add CLAUDE.md, Serena workspace files, and gitignore stray lockfiles Juan Vidal 2026-05-08 ↗ GitHub
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
c47ab161 docs: add runbooks, ADRs, and deferred-items tracker Juan Vidal 2026-05-08 ↗ GitHub
commit body
- Slim README to point at runbooks under docs/
- runbooks/: local-development, schema-changes, architecture, troubleshooting
- adr/: README + template + ADR-0001 capturing the Supabase removal decision
- deferred.md: consolidated tracker for known follow-ups (pre-prod hardening, code quality, auth features, operational gaps)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.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-188.md from inside the repo you want the changes in.

⬇ Download capture-thread-188.md