Why SaaS Is Built This Way

What sharing buys and what it costs

Sharing infrastructure gives three big wins. Cost: idle capacity is pooled, so a thousand small tenants can fit on hardware that would otherwise sit mostly unused. Operations: you ship one version to everyone, so there is no zoo of customers stuck on old releases. Speed: onboarding a tenant is creating rows and config, not provisioning a server. The costs are real too. Blast radius: a bad deploy or an overloaded database hits every tenant on it. Noisy neighbours: one tenant's heavy report can slow others. Isolation risk: a single missing filter can leak data across companies, which is usually the most damaging bug a SaaS can have. Compliance pressure: some customers demand dedicated resources or data in a specific country. Good architectures keep the sharing benefits while adding guard rails for each of these risks.

Control plane vs application plane

It helps to split a SaaS platform into two halves. The application plane is the product itself: the APIs, workers and databases that serve tenants' day-to-day requests. The control plane is the machinery that manages tenants as a whole: sign-up and onboarding, provisioning resources, plans and billing, tenant-level configuration, metrics per tenant, and offboarding. The control plane is mostly global and serves your own team and the billing system, while the application plane may be sharded or split per tenant. Keeping them separate means you can change how tenants are placed (shared database today, dedicated database tomorrow) without rewriting product code, because product code asks the control plane where a tenant lives instead of assuming. Many later topics, from provisioning to metering, are control-plane features.

A mall and its management office

The shops in a mall are the application plane: they serve customers all day. The mall management office is the control plane: it leases shops, decides who gets a bigger unit, collects rent and evicts tenants who leave. Shoppers never see the office, but the mall cannot run without it.

Quick check: Which of these is a control-plane responsibility?

• Rendering a tenant's dashboard page
• Provisioning resources for a newly signed-up tenant
• Serving a product search API call
• Running a tenant's scheduled report query