CaseMark rips out Supabase and runs Mike on its own platform

A clean-room re-platforming that makes CaseMark's own Case.dev the engine behind everything Mike does.

infrastructuresecurity

CaseMark has taken Mike off Supabase - the hosted backend (login, database, file storage) the original project leaned on - and rebuilt every piece on its own Case.dev platform. Logins, the database, document storage, the AI routing, and the grounding that lets Mike answer questions from your files now all run through Case.dev. The fork no longer touches Supabase at all.

The same push hardened the fork for a public launch: limits on repeated login attempts, signed webhooks and signed download links, and a demo mode that caps how much each user can spend. The team also dropped old database columns that stored AI provider keys as plain text - a real liability carried over from the upstream version.

So what If you're weighing a hosted, commercial flavour of Mike over self-hosting, this is what a vendor-owned build looks like.

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 CaseMark/mikeoss-casedotdev, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
2e6b6604 Prepare Case.dev public fork kveton 2026-05-02 ↗ GitHub
1c8769ce Complete Case.dev integration polish kveton 2026-05-04 ↗ GitHub
b81944c4 Trigger Vercel review checks kveton 2026-05-04 ↗ GitHub
e2ee94d0 Harden public release security kveton 2026-05-04 ↗ GitHub
bd36bdd5 Merge pull request #1 from CaseMark/codex/public-casedev-release Scott Kveton 2026-05-04 ↗ GitHub
Complete Case.dev integration polish

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

⬇ Download capture-thread-32.md