CaseMark hands you the exit map for Case.dev

The fork now documents, in plain terms, exactly how deeply it leans on its underlying AI platform - and how hard each piece would be to swap out.

integrationinfrastructure

CaseMark's fork is built on Case.dev, the commercial legal-AI platform that supplies its document storage, matter management, legal research and other building blocks. The headline change here isn't a feature - it's honesty about dependence. A new section spells out five ways to adopt the fork, from running it fully on Case.dev, to bringing your own AI models or your own database, to stripping the platform out entirely (possible, but not effortless). A companion table walks through every underlying service and marks whether it's actually wired in, merely supported, or not used yet.

The team also loosened demo mode so evaluators can plug in their own account key and bypass the shared budget, and added an operator switch to pause a public demo without touching code.

So what If you're evaluating this fork for real work, this is the rare repo that tells you upfront how locked-in you'd be - and gives you a credible path to bring your own infrastructure.

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
4a979679 Allow Case key override in demo mode kveton 2026-05-04 ↗ GitHub
ecea50ce Merge pull request #4 from CaseMark/codex/demo-case-key-override Scott Kveton 2026-05-04 ↗ GitHub
Allow personal Case.dev keys in demo mode
f7126a1b Polish public demo launch kveton 2026-05-04 ↗ GitHub
3bae2c9e Document Case.dev integration options kveton 2026-05-04 ↗ GitHub
8eddf21a Merge pull request #5 from CaseMark/codex/public-demo-polish Scott Kveton 2026-05-04 ↗ GitHub
Polish public demo launch

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

⬇ Download capture-thread-35.md