One platform, multiple tenancy models
SaaS platforms do not have a single correct tenancy model. Some customers expect shared infrastructure, while others require strict separation for security, compliance, or contractual reasons.
whitesky allows SaaS providers to choose the tenancy model per customer, without changing how the platform is operated.
The core concept
On whitesky, a SaaS provider operates one cloud platform, but can deploy customers in different ways:
- shared, multi-tenant environments
- fully isolated, single-tenant environments
Both models coexist and are managed:
- from one portal
- through one API
- with one operational process
Multi-tenancy is a decision made by the SaaS provider — not a constraint imposed by the platform.
What this means for different stakeholders
For platform and application architects
You can deploy your SaaS application:
- once, in a shared environment
- or multiple times, in isolated environments per customer
Both approaches use the same underlying cloud primitives, allowing architectural consistency without forcing a specific tenancy model.
For security and compliance teams
Customer isolation is enforced structurally:
- separate virtual networks
- isolated compute and storage domains
- independent access control
This supports customers with elevated security or regulatory requirements without exceptions or special handling.
For business and product owners
Tenancy becomes a commercial choice:
- standard shared environments for most customers
- premium isolated environments for specific customers
- ability to enter regulated or enterprise markets
This flexibility expands the addressable market without increasing operational complexity.
Virtual Cloud Operator model
Customer environments are created and managed within a single Virtual Cloud Operator (VCO) portal.
Each customer environment can have:
- independent lifecycle management
- separate access roles
- dedicated infrastructure if required
This provides clear boundaries while keeping operations centralized.
Operational simplicity at scale
Even with many isolated customer environments:
- automation remains uniform
- monitoring remains centralized
- lifecycle management remains consistent
Isolation does not multiply operational effort.
Relationship to other SaaS topics
This tenancy model connects directly to:
- Cost Control & Economics
- Portable SaaS Architecture
- Federated & Local Deployment
- Security & Compliance
Together, these allow SaaS providers to scale without sacrificing control.
Next steps
- Define customer segmentation and isolation requirements
- Decide which customers require dedicated environments
- Automate tenant creation and lifecycle
- Design a tenancy strategy aligned with your product roadmap