/Glossary · Architecture
What is Multi-tenant SaaS?
Multi-tenant SaaS is a software-as-a-service application in which multiple customers, called tenants, share the same platform and codebase while their data and permissions stay isolated from each other. It lets you scale to many customers at a lower operating cost.
How a multi-tenant architecture works
Every request carries a tenant context, usually inside the authentication token issued by Amazon Cognito or another provider. Services use that context to filter data, enforce limits, and record metrics per customer. A control plane handles onboarding, configuration, plans, and billing for each tenant.
There are three models: silo, with dedicated resources per customer; pool, with shared resources and logical isolation; and bridge, which mixes both depending on the layer or the plan. On AWS, isolation is reinforced with tenant-aware IAM policies, row-level security in Aurora PostgreSQL, or partition keys in DynamoDB.
When each model makes sense
The pool model is the most efficient in cost and operations, and it suits many small and mid-sized customers. The silo model fits large or regulated customers, or those with contractual isolation requirements, though it multiplies cost and maintenance work. Many platforms offer silo only on the enterprise plan.
The decision does not have to be final for the whole system. You can share the application layer and isolate only the database for certain customers, or the other way around. What matters is designing the tenant context and control plane from day one so you can move customers between models.
Best practices and common mistakes on AWS
Enforce isolation in a shared layer, not in every hand-written query. Measure cost and consumption per tenant, and set limits so one noisy customer cannot degrade everyone else. Automate end-to-end tenant onboarding and review the SaaS Lens of AWS Well-Architected.
Common mistakes: relying only on a tenant ID filter in the code with no second security barrier, being unable to attribute costs per customer and finding out when it is time to set prices, and creating an account or database per customer without automation, which makes operations unmanageable as you grow.
/FAQ
Questions about Multi-tenant SaaS
Another question? Write to hello@nubent.com and an engineer will answer.
What is the difference between single-tenant and multi-tenant?
In single-tenant, each customer gets its own instance of the application and infrastructure. In multi-tenant, multiple customers share the platform with isolated data. Multi-tenant lowers costs and simplifies upgrades; single-tenant offers stronger isolation at a higher operating cost.
How do you isolate each tenant's data on AWS?
With several layers: tenant context in the token, IAM policies that restrict access based on that context, row-level security in Aurora PostgreSQL, partition keys in DynamoDB or separate databases per customer, and per-tenant KMS keys for encryption when needed.
What is a noisy neighbor in SaaS?
It is a tenant that consumes so many resources that it degrades performance for the other tenants sharing the infrastructure. You mitigate it with per-tenant usage limits, queues and throttling in API Gateway, data partitioning, and, in extreme cases, by moving that customer to dedicated resources.
How we help with Multi-tenant SaaS
AWS Application Development
Backends, APIs, frontends on CloudFront and Amplify, databases and CI/CD: cloud-native software built on AWS and ready to run in production.
Learn moreSecurity and compliance
AWS security: access, network, encryption and secrets fixed, with automated controls and continuous evidence for SOC 2, ISO 27001, PCI DSS, HIPAA or Spain's National Security Framework (ENS).
Learn moreWell-Architected Review
A review of your workloads across the 6 AWS Well-Architected pillars, with Generative AI and SaaS lenses and a remediation plan you can actually execute.
Learn moreNext step
What should we build next on AWS?
30 minutes with an engineer. Concrete next steps, whether or not you work with us.