Classhub
A decade-old, single-tenant school system rebuilt from the ground up into a multi-tenant platform now serving 40 institutions from one codebase.
Numbers that moved
The challenge
Classhub ran a separate deployment per school — every update meant redeploying dozens of instances, and onboarding a new institution took weeks of manual setup.
The original codebase had no clean separation between tenants, making a rewrite unavoidable if the business wanted to scale past a handful of schools.
Our approach
We mapped every school-specific customization in the legacy system to decide what became configuration versus what was genuinely one-off.
A phased migration plan let us move institutions one at a time onto the new platform, validating data integrity at each cutover.
What we built
A single multi-tenant platform with per-institution configuration, role-based access, and a self-serve onboarding flow that replaced weeks of manual setup.
A migration toolkit automated data validation for each school moving over, catching discrepancies before they ever reached a live classroom.
We used to dread onboarding a new school. Now it happens in days, and one engineer can ship an update to every institution at once.
What we used
Related work
Outgrowing a single-tenant system?
We rebuild legacy platforms into multi-tenant systems that scale without a rewrite every year.