IT Glossary
What does multi-tenant mean?
The architecture in which a single installation of an application serves many customers, with each one’s data strictly separated from the others.
The economics of software-as-a-service rest on a single architectural decision, and this is it. An apartment building houses dozens of families on one foundation, under one roof, with one heating system — yet every flat has its own lockable door. That is how a multi-tenant application works: one installation of the software serves every customer, each of them called a tenant, while each tenant’s data stays isolated and invisible to the rest. Instead of maintaining a separate copy per customer, which is expensive to run and painful to update, you maintain exactly one, and an improvement reaches everybody the moment it ships. The concept matters in both directions. If you are building a SaaS product, the quality of the multi-tenant architecture decides whether your margin grows or melts as the customer count rises, because badly separated data eventually forces a rewrite. If you are merely buying SaaS, ask how your data is isolated from the other tenants — the answer, and how readily it arrives, says a great deal about the maturity of the provider you are about to sign with.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
Cost per customer that keeps falling
The same infrastructure serves ten customers or a thousand — each new one costs marginally less, and the product margin rises along with the count.
One update, every customer current
Fixes and new features ship once into the shared installation — the nightmare of maintaining dozens of different versions installed at client sites disappears.
A new customer live in minutes
Onboarding means creating a tenant, not installing a system — the gap between signed contract and actual use is measured in minutes rather than weeks.
Frequently asked questions
How is customer data isolated in a multi-tenant application?
On a scale that runs from a separating column inside shared tables, through a separate schema per customer, to a dedicated database for each one. The stronger the isolation, the higher the running cost — which is why enterprise customers and regulated sectors normally insist on the stricter end of that scale and expect to pay for it.
What is single-tenant, and when is it preferred?
Each customer receives their own separate installation: more expensive to operate, but sometimes required by banks, public institutions or contracts carrying strict data-sovereignty clauses. Many SaaS products therefore offer single-tenant deployment as a premium option rather than refusing the requirement outright and losing the deal.
Can one heavy customer slow the application down for other tenants?
The risk is real and has a name: the noisy neighbour problem. It is handled with per-tenant resource limits and monitoring of each tenant’s consumption. It is also one of the better questions to put to any SaaS provider before signing, because a vague answer usually means nobody has ever measured it.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247