CaseMark rebuilds Mike on top of Case.dev

The whole point of this fork: rip out the upstream plumbing and stand Mike back up on CaseMark's own platform.

infrastructuresecurity

CaseMark has done a foundational rewrite. Mike originally assumed a particular cloud stack for its database, file storage, and login. CaseMark has swapped all three for Case.dev-native equivalents: documents now live in Case Vault (CaseMark's hosted document store), login moves to Better Auth (an open-source auth library) with per-user AI provider keys held encrypted, and a homegrown compatibility layer keeps the rest of the app talking to the new database without a full rewrite.

The same wave adds a Demo Mode with usage metering and a "Powered by Case" surface for a hosted trial, plus a security pass: rate limiting on the login endpoint, a hard refusal to boot in production with placeholder secrets, and a migration that drops legacy plaintext API-key columns from the database.

It's not pick-and-mix - the pieces are interlocked and assume Case.dev's APIs.

So what If you're watching how a vendor turns an open-source legal-AI codebase into the front door for their own platform, this fork is the textbook example.

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