DEV

True multi-tenant SaaS isolation goes far beyond choosing a data model — this episode breaks down every layer of the stack, from token validation at the edge to per-tenant encryption keys, that must align before you actually have security.

Show Notes

Picking between pooled schema, schema-per-tenant, and database-per-tenant is often treated as the defining architectural decision in multi-tenant SaaS — but it's really just the starting point. This episode of DEV.co digs into the full isolation stack that has to work in concert with whatever data model you've chosen, from the moment a request hits the edge all the way through encryption, background jobs, and audit logging. The discussion is grounded in the full isolation stack for multi-tenant SaaS — a deep-dive reference covering each layer in detail.

Here's what the episode covers:

  • Tenant resolution before the first query: Why isolation must be established cryptographically at the edge — via signed tokens and subdomain/hostname cross-checks — before any code touches the data layer, and why request-scoped, immutable context is non-negotiable.
  • Postgres row-level security done right: How to move from "we remember to filter" to "the database enforces it for us," including the critical difference between SET LOCAL and SET in connection-pooled environments, composite index design, and when to grant bypass permissions.
  • Silo vs. pool vs. bridge — mapped to deal size: A practical decision framework that ties architecture to customer tier and contract value, with a concrete rule for when to graduate tenants from pool to bridge to silo without a rewrite — made possible by abstracting the connection resolver behind a tenant router from day one. Teams building or scaling a SaaS platform will find this framing immediately applicable.
  • Envelope encryption and per-tenant key hierarchies: Why a single application-wide key is a single point of total exposure, how a three-layer KMS hierarchy eliminates cross-tenant key paths, and how BYOK falls naturally out of the same architecture — making it table stakes for healthcare and financial services buyers rather than a premium feature.
  • The layer most teams miss — jobs, caches, and queues: Background workers, cache entries, and message queues all carry implicit tenant context that's easy to leak; the episode addresses why these are often the last gap closed and the first place isolation breaks in production.
  • Security as a structural property, not a convention: The throughline across every layer is that conventions are forgotten under deadline pressure — each mechanism discussed replaces a remembered rule with an enforced one. Teams working on cybersecurity development for SaaS products will recognize this as the right frame.

For more on securing complex financial systems at the infrastructure layer, the episode Custom Banking Software in 2026: Core APIs, KYC, and Security Controls That Actually Matter covers adjacent ground on regulated workloads and compliance-grade controls worth pairing with this one.

DEV.co

RFP.co

What is DEV?

Software and web development from the side that has to ship it and then live with it. Architecture decisions with a cost attached, scoping, technical debt, hiring and vendor selection, and the AI tooling question every engineering team is now answering whether they planned to or not.

Each episode takes one decision — rewrite or refactor, framework choice, build versus buy, how to scope a fixed-bid project honestly — and works through the tradeoffs, including the ones that only show up in year two. Written for engineering leads, technical founders and the people who fund them. Five or six minutes, no hand-waving.

Topics include rewrite versus refactor, build versus buy, scoping fixed-bid work honestly, technical debt you should keep, framework and platform choices, hiring and vendor selection, code review culture, and where AI tooling actually helps.

Produced by DEV.co, web and software development. Full details, services and further reading at https://dev.co