
☁️ SaaS & Cloud
Multi-tenant SaaS, Kubernetes, CI/CD, authentication and serverless designs. Open any template to see the finished diagram, then use it as the starting point for your own in the Studio.
11 templates
How a microservices app runs on Kubernetes in the cloud: ingress, namespaces, services with multiple replicas, managed databases and monitoring.
A typical CI/CD pipeline from a pull request to production: build, tests, security scans, staging deploy, approval and a canary release.
The authorization code flow with PKCE used by most modern web and mobile apps to log users in through an identity provider.
A B2B SaaS product serving many customer organisations from one platform: tenant-aware services, per-tenant data isolation, billing and admin.
The classic three-tier web app on AWS: CloudFront and a load balancer, an autoscaling app tier in private subnets, and a Multi-AZ database.
Services that talk through events instead of direct calls: an order service publishes events that inventory, payments, notifications and analytics react to.
The states of a SaaS customer's subscription: trial, active, past due with retries, paused, cancelled and expired.
A GitFlow-style branching model: feature branches into develop, release branches for stabilisation, and hotfixes straight to main.
A serverless backend on AWS: API Gateway, Lambda functions, DynamoDB, S3 events and Cognito for sign-in, with no servers to manage.
How data from apps, databases and events lands in a lakehouse and becomes dashboards and ML features: bronze, silver and gold layers.
An object model for users, organisations, roles and permissions in a B2B SaaS app, with role-based access control.
More SaaS & Cloud templates are being added regularly.
SaaS and cloud diagrams show how one product serves many customers safely: tenancy model, authentication, APIs, background jobs, databases, billing, and how it all runs on Kubernetes or serverless.
They are used in architecture reviews, security questionnaires from enterprise customers and onboarding new engineers.
Show where the tenant is identified (login or subdomain), how requests carry the tenant id, and whether data is separated by schema, database or row-level rules.
Network zones, single sign-on (SAML or OIDC), encryption in transit and at rest, backups, audit logs and which third-party services receive customer data.
Yes. Open a template, then describe your own setup in the Studio, for example "multi-tenant B2B SaaS on AWS with Cognito, ECS, Postgres and Stripe billing", and the AI redraws the diagram with your systems.