CaseMark opens its fork to a hosted demo - and shows you what's actually wired

You can now try CaseMark's take on Mike without standing anything up yourself, and read an honest map of which parts are real.

integrationinfrastructure

CaseMark has put up a live, hosted version of its fork so evaluators can poke at it in a browser. Each visitor gets a small fixed spending cap, and operators get a one-switch pause that swaps the working app for a quiet landing page - useful when the demo gets more attention than the budget can absorb.

The more interesting artifact is the documentation that ships alongside it. CaseMark spells out several "integration depths," from running the whole platform to a stripped-down version that drops its underlying vendor entirely. A companion table walks through eighteen building blocks and labels each one plainly: in use today, a future maybe, or untouched. That answers the question every buyer actually has - what works now versus what's aspirational - without anyone reading a line of code.

So what Anyone weighing whether to adopt or partially borrow from this fork can now scope the work from a webpage instead of a code review.

View this fork on GitHub →

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

Commits in this thread

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

SHA Subject Author Date
f7126a1b Polish public demo launch kveton 2026-05-04 ↗ GitHub
3bae2c9e Document Case.dev integration options 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-285.md from inside the repo you want the changes in.

⬇ Download capture-thread-285.md