juanjo is cutting Mike's cord to Supabase

The fork is moving its database and logins off a hosted service and onto plumbing it controls.

infrastructure

juanjo is rebuilding the layer everything else in Mike sits on: the database. Right now Mike leans on Supabase - a hosted service that handles both data storage and user logins. juanjo is swapping that out for a database that runs locally on standard, open-source Postgres, with no third-party account required to get started.

This piece of the work lays the foundation: the full map of what Mike actually stores, from users and projects to documents, chats, workflows and review tables. It's plumbing, not a feature you'll click. But it's the kind of plumbing that decides whether a firm can stand Mike up on its own terms rather than renting someone else's cloud - and every later change in this thread builds on it.

So what Anyone weighing whether this fork can be self-hosted should watch this thread - it's the groundwork that makes running Mike without outside accounts possible.

View this fork on GitHub →

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

Commits in this thread

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

SHA Subject Author Date
258d1a7a feat(infra): add Postgres docker-compose with pgcrypto extension Juan Vidal 2026-05-08 ↗ GitHub
5e645c6d feat(backend): add Drizzle ORM scaffolding (client + drizzle-kit config) Juan Vidal 2026-05-08 ↗ GitHub
64ac55ac chore(backend): clarify connection-pool comment Juan Vidal 2026-05-08 ↗ GitHub
267ec65a feat(backend): Drizzle schema + initial migration (replaces Supabase auth schema) Juan Vidal 2026-05-08 ↗ GitHub
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
c9b98685 chore(backend): add trailing newline to initial migration Juan Vidal 2026-05-08 ↗ 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-182.md from inside the repo you want the changes in.

⬇ Download capture-thread-182.md