CaseMark lets demo users bring their own Case.dev key

The hosted demo now treats the shared key as a fallback, not a ceiling.

multi-tenantinfrastructure

On CaseMark's hosted demo of Mike, every visitor used to share a single Case.dev API key - the credential that unlocks the Case.dev model catalog. @kveton's change flips that: users can now save a personal Case.dev key from inside Demo Mode, and the shared key only kicks in when they haven't. Clear your key and you fall back cleanly to the demo default.

The Account > Models screen was rewritten to match - demo key as the default, personal key as the override. Direct keys for Anthropic and Gemini stay switched off in the hosted demo for now, so this is narrowly a Case.dev story, not a full bring-your-own-key opening. On the backend, a global demo spending cap was removed so per-user budgets stand on their own without an accidental shared ceiling layered on top.

So what Worth a glance for anyone running a hosted demo of a legal-AI tool and wrestling with how to let serious evaluators use real credentials without ripping the front door off.

View this fork on GitHub →

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

Commits in this thread

1 commit 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

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

⬇ Download capture-thread-286.md