Shiven Singh
All writing

Three companies run their whole operation on it, and none of them are mine

June 2026

ZeroCrossLMS is a white-label platform that education businesses run their entire operation on: content, payments, certificates, and open-ended AI grading, each on their own domain. The problem with horizontal infrastructure is that nobody buys the empty box. You need proof it survives contact with real, different businesses running their actual operation on it, not a pilot with an easy way out.

Three external companies do exactly that today, and they are about as unalike as education businesses get. One runs self-paced certifications with verifiable credentials. Another runs cohort training that ends in a real job-placement pipeline. A third runs branching career simulations, where learners are graded on the calls they make, not what they can recall. Three very different shapes, one shared engine, and none of them are mine. That is the point: a platform only proves it is horizontal when businesses that look nothing alike can all live on it.

The engine's hard part is the evaluation. It grades essays and branching-simulation transcripts, open-ended work with no answer key, against a rubric: zero to four per criterion, each with a written justification, plus a read on how the person actually reasoned. It runs one model first, falls back to a second, then a third, and tracks token cost the whole way, so no single vendor's outage or price hike can take the product down.

Multi-tenant underneath, done properly: each client is a subdomain with tenant claims in the token, tenant scoping in the database, and row-level security so one client's data physically cannot appear in another's. Feature access and student quotas gate on the plan.

The proof of a horizontal bet is not a demo, it is three different real businesses trusting it with their whole operation. The vendor-independent fallback chain is the engineering half of the same instinct: if companies are going to run their business on your grading, you never let one dependency quietly own your uptime.

If you have a view on this, or you disagree, .