Multi-tenant SaaS architecture template
Tenant routing, a shared stateless app tier, pooled and siloed data, the control plane, and the trade-offs between tenancy models.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- Shared application tier (stateless)
- Web app · API services (tenant context on every request) · Workers (fair queues per tenant)
- Data tier
- Pool: shared Postgres, tenant_id + row-level security · Silo: dedicated database for Initech · Object storage: files/{tenant_id}/
- Control plane
- Tenant onboarding + provisioning · Plans and feature flags per tenant · Usage metering → billing (Stripe) · Rate limits + quotas per tenant · Tenant admin console + audit log · Noisy-neighbour alerts per tenant · Per-tenant backup and data export · Data residency: EU / US cells
Table columns: Tenancy model, Isolation, Cost per tenant, Operations, Use for.
Also on the board
- Acme Corp (acme.app.io)
- Tenant resolver: subdomain → tenant_id
- Globex (globex.app.io)
- DNS + CDN + WAF (*.app.io)
- Auth: SSO / OIDC per tenant
- Initech, enterprise (initech.app.io)
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
- Ask Kelvo right on the board (Pro). With Pro, type @kelvo and what you want in any box or text, for example “@kelvo add error handling”, and press Enter. The change is made there and the request disappears; ⌘Z undoes it.
- One page per level. Put the C4 context view on one page and the container view on the next, so each diagram stays readable.
Good for
- architect
- multi-tenant
- saas
- architecture
- isolation
- Agreeing on boundaries and responsibilities between services
- Recording why a design was chosen (and what was rejected)
- Comparing integration options side by side
Related templates
C4 system context diagram
C4 level 1: the system in scope, the people who use it and the external systems it depends on, with a legend.
C4 container diagram
C4 level 2: the apps, APIs, databases and queues inside the system boundary, with the technology on each link.
Microservices with API gateway
Clients behind an API gateway, services that each own their database, and an event bus for asynchronous work.
Event-driven architecture
Producers publish facts to a broker; independent consumers react — with the design rules that keep it reliable.
LLM application architecture
Production building blocks around a model: gateway, guardrails, orchestrator, cache, vector DB, tools and observability.
LLM agent loop
How a tool-using agent plans, calls tools, observes results and updates memory until the goal is met, with guardrails.