Multi-tenant describes software where one shared copy of an application and its infrastructure serves many customers, while each customer's data stays separate.
Systems · Reviewed by Ray Rasouli
Ask about multi-tenant
Plain answers, with your setup in mind.
Ask anything about multi-tenant. For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
Think of an apartment building: everyone shares the structure, plumbing and elevator, but each unit has its own lock. Most SaaS products work this way. A distributor and a bakery might both use the same inventory app on the same servers without ever seeing each other's records.
Because everyone runs the same version, the vendor can ship fixes and features to all customers at once. The trade-off is less room for deep custom changes, since one customer's tweak would affect everyone.
When evaluating a multi-tenant product, ask how data is isolated and what you can configure on your own.
In practice
Custom code is not allowed.
Businesses expecting deep changes find they can only configure settings, not rewrite how the product works.
Upgrades happen on the vendor's schedule.
Every tenant gets the new version at the same time, ready or not.
Busy neighbours slow things down.
Heavy use by other tenants can sometimes affect performance, so vendors set limits on API calls and large jobs.
Data isolation is assumed, not checked.
Buyers rarely ask how tenants are separated, which matters for security reviews and public sector contracts.
Multi-tenant shares one application across many customers. Single-tenant gives each customer its own copy, which allows more control but usually costs more to run.
It may sit in the same database, but a well-built multi-tenant system keeps it logically separated so other tenants cannot see or change it.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.