Multi-Tenant
Multi-tenancy is a software architecture in which a single running instance serves many customers (tenants) — here, many schools — while each school’s data is logically isolated and kept private. It lets the vendor deliver updates and security to everyone at once, keeping costs low. Edutris uses a multi-tenant cloud architecture so each school gets its own secure, separated environment.
An architecture where many schools share one software instance while their data stays isolated and private.
Why it matters
For a school buying software, multi-tenancy is what makes cloud pricing possible — and it is also where the data question sits. The concrete asks for the principal or trust are: how is our data separated from another school's, who at the vendor can read it, where is it hosted, and how do we get a complete export if we leave. Those belong in procurement, not IT.
In practice
- One codebase and one database serve many schools; every record carries a tenant key so each query is scoped to your school alone.
- Updates and security patches reach all tenants at once, so schools do not schedule, test or pay for version upgrades individually.
- Trusts and school groups usually map to one tenant per school under a parent organisation, with staff roles scoped per school.
- Isolation is enforced in software rather than by physical separation, so ask how it is tested and whether a cross-tenant leak would be detected.
- Plan the exit at purchase: ask for a complete structured export of your own tenant's data in a documented format.
Common mistakes
- Assuming 'cloud' means a separate database per school; ask specifically how tenant separation is enforced.
- Signing without an agreed export format and exit process, which is where real switching cost hides.
Common questions
Is multi-tenant software safe for student data?
It can be, but the safety comes from how isolation is implemented and tested, not from the label. Ask how records are scoped per school, who at the vendor can reach production data, where the data is hosted, whether backups are separated, and how the vendor handles obligations under Indian data-protection law.
What is the difference between multi-tenant and single-tenant?
In a multi-tenant system, one running instance serves many schools with their data logically separated. In single-tenant, each school gets a dedicated instance or database. Single-tenant gives stronger physical separation and more room for customisation, but costs more and usually means slower updates. Cloud school software is typically multi-tenant.
Can another school see our data on a shared system?
Not if tenant scoping is correctly implemented — every read and write is filtered by the tenant identifier, so one school's queries cannot return another's rows. The risk is a bug in that enforcement rather than the architecture itself, which is why it is worth asking how the vendor tests for cross-tenant access.
Comparing school software categories? Edutris is the all-in-one option — SIS, fees, attendance, exams and a parent app on published tiers from ₹2,999/month.
Related terms
SaaS (Software as a Service)
Software delivered over the internet on a subscription, with no local install and automatic updates.
Cloud vs On-Premise
Cloud software runs on the vendor’s servers over the internet; on-premise runs on the school’s own hardware.
Single Sign-On (SSO)
A login method letting users access multiple applications with one set of credentials.
SIMS (School Information Management System)
A broad system managing a school’s information across students, staff, academics and administration.
Run your school on Edutris
Admissions, attendance, fees, report cards and a parent app — simple tiers from ₹2,999/month, no per-student add-ons.
Book a Demo