CaseMark hands firms the keys to their own AI models

You can now wire Mike straight into your own Anthropic or Gemini account instead of routing everything through CaseMark's gateway.

integrationsecurity

Until now, anyone running this fork of Mike reached the AI models through CaseMark's shared gateway. This change lets a firm plug in its own credentials with Anthropic, the company behind Claude, and Google's Gemini - so the bill, the contract, and the data relationship sit directly between you and the model maker rather than through a middle layer.

The plumbing is built for people who worry about credentials. Keys are encrypted where they're stored, and CaseMark checks each one actually works before trusting it. Deleting a key doesn't wipe the record - it marks the key revoked and keeps the audit trail. And in production, the old habit of quietly falling back to a shared house key is switched off, so a firm only ever uses the credentials it deliberately set up. It's all managed from a new models page in account settings.

So what If you care which AI vendor you're contracting with and where matter data flows, this is the setting that puts your firm in control.

View this fork on GitHub →

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

Commits in this thread

4 commits from CaseMark/mikeoss-casedotdev, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
c0ed073a Add BYOK model provider settings kveton 2026-05-04 ↗ GitHub
2032ca81 Address BYOK review feedback kveton 2026-05-04 ↗ GitHub
b3098e8b Tighten BYOK review fixes kveton 2026-05-04 ↗ GitHub
54f5b8b8 Polish BYOK provider feedback 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-288.md from inside the repo you want the changes in.

⬇ Download capture-thread-288.md