Single-tenant describes a software setup where each customer gets its own separate deployment of the product. Instead of sharing one system, a customer has its own copy of the application and often its own database and servers.

It matters because it offers stronger separation. Problems caused by another customer, such as heavy load or a data-handling bug, are less likely to reach it, and the deployment can be customized, placed in a chosen region or updated on a schedule that suits the customer. Some regulated customers ask for it.

It costs more to run and manage. Every deployment has to be set up, monitored and updated, which takes more effort and money, and it can slow the rollout of new versions. It is also not automatically more secure: a poorly managed separate deployment can be at greater risk than a well-run shared one.

When choosing, compare the isolation the customer needs with the extra cost, consider hybrid models where most customers share a system and a few have their own, and automate deployment so that managing many copies stays practical.