Maison-Retail-Management-International parks Mike's backend on Render after Cloudflare won't take it
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.
The team briefly tried moving Mike's backend onto Cloudflare Workers, a serverless platform that runs code on Cloudflare's global edge network. It didn't work - Mike leans on a bundled document-processing engine to handle files, and that engine simply can't run in Workers' stripped-down environment. So the stub got torn back out.
The resolution: the backend now runs on Render, a more conventional cloud host that runs full Node applications, while the lighter front end stays on Cloudflare. Almost nothing new was added to the codebase here - the value is the answer to a question, not a feature. If you're sizing up where a document-heavy legal AI can actually be deployed, this fork has done the homework for you: edge-serverless is out, standard Node hosting is in.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?