Building Institution OS: architecture decisions for a multi-tenant education platform
How we approached tenancy, communication costs, transport tracking and long-term maintainability in our own product. An internal engineering case study — not client work.
The challenge
Schools in our launch region typically combine several disconnected tools with heavy use of personal messaging. A platform for them had to be affordable for small institutions, scale to multi-campus groups, protect children's data, and keep messaging costs predictable.
What we did
We chose a modular monolith with database-enforced tenant isolation, a channel router that sends routine updates in-app and reserves paid channels for important events, per-vehicle tracking links for families with several children, and adapters around every external vendor so providers can be replaced.
Where it stands
The platform is in private beta with pilot institutions. We are deliberately not publishing performance or adoption numbers until they are measured over a full academic term and can be verified.
Technologies and sector
We label every item by what it is. Client projects appear here only after the client has approved what we publish.
Services involved
Planning something similar?
Tell us about your situation. We will share what we learned and what we would do differently.