When you subscribe to a SaaS (software as a service) product, you usually share the same software with hundreds of other businesses, yet you only see your own data. The structure that makes this possible is called multi-tenant architecture. In this article we explain what multi-tenancy is, how data isolation works, its advantages and challenges, and which questions to ask when choosing a SaaS product.
What Is Multi-Tenant Architecture?
In a multi-tenant architecture, a single application and its infrastructure serve multiple customers (tenants) at the same time. Each tenant's data is kept separate from the others, and each tenant can define its own users, settings and logo. The code and servers underneath are shared.
The most common analogy is an apartment building: the foundation, elevator, water and electricity are shared, but every flat has its own door, key and furniture. Your neighbour cannot walk into your flat. In multi-tenant software the infrastructure is shared too, but one business cannot see another's customer list, invoices or reports.
Single-Tenant vs. Multi-Tenant
In a single-tenant architecture, every customer gets a separate copy of the application and usually a separate database. It is like building a detached house for every customer instead of an apartment building.
- Single-tenant: Isolation is physically as strong as it gets and customer-specific changes are easy. On the other hand, every new customer means a separate installation, separate updates and separate maintenance; cost grows linearly with the number of customers.
- Multi-tenant: All customers run the same version, a new customer can be onboarded in minutes and infrastructure cost is shared. In return, data isolation must be designed very carefully in software and customer-specific changes must be limited.
How Is Data Isolated?
There are three common approaches to separating data in multi-tenant systems:
- Shared database, separated by tenant ID: All customers' data lives in the same tables, and every record carries a field showing which tenant it belongs to. The application filters by this field on every query. It is the most economical and most common approach; its security depends on that filter never being forgotten.
- Shared database, separate schema per tenant: Each customer's tables are kept in their own section of the same database. Isolation is stronger, but management gets harder as the number of tenants grows.
- Separate database per tenant: The application is shared but each customer has its own database. It provides the strongest isolation and is preferred by large enterprise customers handling sensitive data; it is also the most expensive.
In practice, many products start with the first approach and prevent cross-tenant leaks with database-level safeguards (for example row-level security policies) and automated tests. Some products combine the first approach for most customers with the third for large enterprise customers.
Advantages of Multi-Tenant SaaS
Cost efficiency. Server, database, backup and monitoring costs are shared across all customers. This is why SaaS products can be offered at much lower monthly prices than software installed separately for each customer.
Central updates. A bug fix or new feature reaches every customer with a single deployment. Nobody is stuck on an old version, and security patches are applied to everyone at once.
Fast onboarding. No server needs to be set up for a new customer. A business that signs up can open its account and start working right away.
Scalability. Infrastructure is scaled to the combined load of all tenants. A business adding branches, or new businesses joining, does not require a separate installation project.
Better product development. Because everyone uses the same product, it is much clearer which features are used and where people struggle, and the product improves accordingly.
Challenges and What to Watch Out For
- The noisy neighbour problem: One tenant running a very heavy report or bulk import can affect others' performance. Well-designed systems use per-tenant resource limits and background queues.
- Limits on customisation: Writing custom code for each customer can break the shared version, so customisation should happen through settings and configuration.
- Per-tenant restore: Restoring a single customer's data to a specific date is more complex in a shared database and must be planned from the start.
- Security testing: Every release should verify with automated tests that cross-tenant access is impossible.
- Legal requirements: Under data protection laws (KVKK, GDPR) it must be defined where data is stored and how a customer's deletion request is handled.
Questions to Ask When Choosing a SaaS Product
As a business using a multi-tenant product you do not need to know the infrastructure details, but you should get clear answers to these questions:
- In which country and how is our data stored? How is it separated from other customers?
- How often are backups taken? After an incident, to what point can our data be restored?
- If we cancel, in what format and how can we export our data?
- Can we define user permissions by role?
- How often are updates released, is there downtime, and are we notified in advance?
- When we have a special need, can it be solved through settings, or does it require custom development?
Which Businesses Is It Suitable For?
Multi-tenant SaaS is ideal for products that serve many businesses doing the same kind of work: auto service shops, clinics, accounting firms, franchise networks, retail chains and service businesses. Their processes are largely similar, and differences can be handled with settings.
On the other hand, organisations with very specific security requirements, those that require the software to run entirely on their own servers, or those whose processes resemble no existing product may be better served by a single-tenant installation or custom software development.
A Real Example: Auto Service Software Pro
Oto Servis Yazılımı Pro, developed by Progsan, is multi-tenant architecture in the field. Auto service shops in different cities use the same platform; each shop sees its own work orders, stock, appointments, e-invoices and customers. Businesses with multiple branches manage them from a single account. When a new feature or improvement is released, every shop benefits at the same time. Our CRM product CRModular, which brings sales and service together on one screen, follows the same approach with a multi-tenant structure that keeps each company's data separate.
Want to build your own SaaS product or move existing software to a multi-tenant structure? Get in touch — we will bring the architecture experience from our own products to your project. The first consultation is free.
