Skip to Content
Registrations Closed

Edge TLS and Tenant Isolation for Multi Tenant SaaS

A technical look at how the edge terminates TLS, routes tenant traffic, and keeps every customer domain isolated.

America/Chicago
Add to calendar:

If you run a multi-tenant platform, your customers want their product to live on their own domain, and every one of those domains has to be safe from every other tenant. This session is a technical deep dive for the people who own that problem. We will walk through how an edge terminates TLS, how it routes each request to the right tenant, and how certificate issuance and renewal happen on demand so a customer domain can go live in about thirty seconds.

What you will learn

  • How a control plane and an edge divide the work of connecting, securing, and routing customer domains.
  • How on demand certificate issuance and renewal keep TLS current without manual steps.
  • How strict multi-tenant isolation is enforced at the edge so one tenant cannot reach another tenant's traffic or certificates.
  • How domain ownership verification and DNS configuration are automated across 63 DNS and registrar providers.
  • How a customer moves from an unconnected domain to a live, secured domain in roughly thirty seconds.

Who this is for

This is built for platform and security engineers at multi-tenant SaaS companies who are responsible for custom domains, TLS, and the isolation guarantees they make to their customers. If you have weighed building this in house against adopting a fully managed service, you will get a clear technical basis for that decision.

What we will cover

  1. The shape of the system: control plane responsibilities and edge responsibilities, and where the boundary sits.
  2. Connecting a domain three ways: one click provider authorization, a provider API token, and a guided manual flow that verifies automatically.
  3. TLS at the edge: certificate issuance, renewal, and how termination and routing fit together.
  4. Tenant isolation: the guarantees that keep each customer domain and its traffic separate from the rest.
  5. Operating it at scale: what a fully managed service handles for you and what stays in your hands.

This was a live sixty minute session with time for questions from the audience at the end. Everyone who registered receives the recording, so you can revisit the architecture and the walkthrough at your own pace.