SaaS
architecture.
Designed for scale.
Multi-tenant platforms built for enterprise buyers and product-led growth teams. We design the tenancy model, the data isolation, the platform team topology — and the architecture diagram your largest prospect reads before they sign.
Requests / second · sampled
Tenant distribution
§ 01 — The decision
Tenancy is
a spectrum,
not a checkbox.
The right tenancy model is the one that maps to your ICP, pricing, and compliance envelope — not the one that was trendy when the platform was conceived. Slide the marker to see the trade-offs.
Shared runtime with dedicated resources where it matters.
The pragmatic default for most scaling SaaS. Shared where economics demand it (app, auth, queues). Dedicated where customers demand it (DBs, KMS, egress). Engineering-grade tenancy tiers.
Trade-offs
Typical fit
§ 02 — Inside a request
Tenant context
carried end-to-end.
Every request is resolved, scoped, and routed inside the platform — not inside every service. One middleware, five stages, zero per-call boilerplate.
Stage 01 · Edge
Request lands · WAF · mTLS
// stage 01 — edge await validateToken(req)
§ 03 — Six decisions
The six decisions
that decide SaaS margin.
Get any of these wrong and every roadmap slide gets 20% slower for the life of the product. These are the decisions where we insist on principal-level engagement.
Identity & access
Workforce, customer, and machine identities with tenant-aware authorisation. SSO, SCIM, and scoped API trust as defaults.
Data isolation
Row-level security, per-tenant KMS, BYOK for regulated tenants, and encryption boundaries that survive a compliance audit.
Noisy-neighbour defence
Quota enforcement, circuit breakers, bulkheads, and tenant-aware rate limiting. The largest customer can't starve the smallest.
Control plane
Onboarding, provisioning, entitlement, and billing as a first-class subsystem — not an ops tool bolted on later.
Observability by tenant
Metrics, logs, and traces carry tenant context end-to-end. SRE answers “is tenant X healthy?” in one query, not five.
Platform team topology
A clear split between product and platform — with shared language, accountable on-call, and the funding model that makes it stick.
§ 04 — The drawing
Six layers.
Read it in two minutes.
Adapted per engagement, but the skeleton is stable. The line between product services and platform services is where engineering leverage either compounds or stalls.
Customer experience
Edge & API
Product services
Platform services
Data plane
Foundation
Scale: 1 row ≈ 1 architectural layer
§ 05 — From the field
Four conversations
we keep having.
Names changed. Details blurred. The shape of the problem — and the shape of the answer — is real.
“Our data room just asked how the architecture scales past 10x. We don't have an honest answer.”
— our answer
Tenancy model audit, platform plan, and a hiring profile that fits the capital plan. Six weeks to a data-room-ready answer.
“A $1M ACV prospect needs BYOK, tenant isolation, and SOC 2 — without turning us into a services company.”
— our answer
We design the escape hatches: per-tier KMS, silo-on-demand, and a commercial model your sales team can actually quote.
“One product is becoming three. Every team is rebuilding auth, billing, and observability. We can feel the tax.”
— our answer
Platform layer design. Shared capability gets built once, carries tenant context, and frees product teams to build product.
“We just acquired a SaaS. Their stack is different, their tenancy is different, and both roadmaps can't freeze.”
— our answer
Integration spine: shared identity, entitlement, and data lineage designed so neither team has to stop shipping.
§ 06 — The numbers
// medians across live platforms
platforms architected
B-stage to public SaaS
availability delivered
tenant-scoped SLA
tenant-level p99
end-to-end, including auth
multi-tenant margin lift
median, post-engagement
§ 07 — Open a review
We'll stress-test
your platform in
two weeks.
An architecture review run by the people who've shipped 40+ multi-tenant platforms. You'll leave with a tenancy recommendation, a platform-team plan, and the first three things to change next quarter.
- Current tenancy model & shape
- ICP & compliance envelope
- Platform team context
- 30-min principal call
// scheduled within 48h
Next drawing:
Cloud Security