Multi-tenant describes a software setup where many customers share one deployment, with their data kept separate by the application or the database. Most SaaS products work this way: a single running system serves all customers, and each customer sees only its own data.

It matters because sharing is what keeps costs down. One deployment is cheaper to run, update and monitor than a separate copy for every customer, and new customers can be added quickly.

The trade-offs concern isolation. A bug in the way data is separated can expose one customer's data to another, and heavy use by one customer can slow the others. Some customers, such as those in regulated industries, may require stronger separation, and there are several designs in between, from shared tables with a tenant identifier to separate databases per tenant.

When designing or choosing one, decide what level of isolation each customer needs, test that data cannot cross between tenants, monitor usage per tenant and be ready to offer more isolated options for customers that require them.