The questions to answer across tenancy, identity, data, integrations, delivery and operations. This guide gives buyers a structured way to frame the decision, identify risk and ask more useful questions of an internal team or delivery partner.
Architecture begins with business boundaries
Define the customer, tenant, user, subscription, data ownership and service commitments before choosing cloud services.
Identity and tenancy
Document how users join organisations, hold multiple roles, move between tenants and recover access. Every data query and background job must preserve tenant boundaries.
Data and integrations
Choose authoritative systems, idempotent integration patterns and recovery procedures. Include migration, retention and deletion from the start.
- Tenant isolation and encryption
- Audit history
- Backups and tested recovery
- API versioning and rate controls
- Webhook retries and dead-letter handling
Delivery and operations
A growing SaaS needs automated deployment, observability, security updates and capacity signals. The team should know how to detect an incident, roll back and communicate before the first major customer arrives.