An early-stage fork of Mike focused almost entirely on getting the app deployed and locked down, not yet on new legal features.
If you tried this fork today, you'd find Mike largely as you know it - the visible work so far lives under the hood, in hosting and security plumbing rather than new things a legal user would click. The most telling story is a deployment shuffle: Maison-Retail-Management-International tried to put the backend on Cloudflare's edge, hit a wall, and settled on running it as a conventional Node service on Render while keeping the front end on the edge. It's the kind of pragmatic course-correction you make when you're standing up a real deployment.
The owner handle, Maison-Retail-Management-International, reads like a retail-management organization rather than a law firm or legal vendor - but nothing in the work so far declares a purpose or a rebrand, so take that as a hint, not a thesis. There's no renaming, no niche pitch, and no new legal workflow visible yet.
The other notable change is a security tightening: who's allowed to talk to the backend got narrower, closing a quiet configuration gap in the process. Taken together, this is a fork being prepared to run somewhere, not yet a fork being reshaped into a different product. If you want the specifics, the commits are on GitHub.
infrastructuresecurity
A small, portable fix to the rule deciding which website is allowed to talk to the fork's server - and a quiet config trap it closes along the way.
A short hosting experiment ended where it started: the heavy lifting stays on a conventional Node host, with only the front end living on the edge.