BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//PYVOBJECT//NONSGML Version 1//EN
BEGIN:VTIMEZONE
TZID:America/Chicago
BEGIN:STANDARD
DTSTART:20001029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T070000Z
TZNAME:CST
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:CST
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T080000Z
TZNAME:CDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:CDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:20260711T094257Z - 86933@25e1d5f22592
DTSTART;TZID=America/Chicago:20251209T110000
DTEND;TZID=America/Chicago:20251209T120000
CREATED:20260711T094257Z
DESCRIPTION:<a href="https://customdomain.ai/event/edge-tls-and-tenant-isol
 ation-for-multi-tenant-saas-19">Edge TLS and Tenant Isolation for Multi Te
 nant SaaS</a>\nIf you run a multi-tenant platform\, your customers want th
 eir product to live on their own domain\, and every one of those domains h
 as to be safe from every other tenant. This session is a technical deep di
 ve for the people who own that problem. We will walk through how an edge t
 erminates TLS\, how it routes each request to the right tenant\, and how c
 ertificate 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 a
 nd 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 acr
 oss 63 DNS and registrar providers. How a customer moves from an unconnect
 ed domain to a live\, secured domain in roughly thirty seconds. Who this i
 s for This is built for platform and security engineers at multi-tenant Sa
 aS companies who are responsible for custom domains\, TLS\, and the isolat
 ion guarantees they make to their customers. If you have weighed building 
 this in house against adopting a fully managed service\, you will get a cl
 ear technical basis for that decision. What we will cover The shape of the
  system: control plane responsibilities and edge responsibilities\, and wh
 ere the boundary sits. Connecting a domain three ways: one click provider 
 authorization\, a provider API token\, and a guided manual flow that verif
 ies automatically. TLS at the edge: certificate issuance\, renewal\, and h
 ow termination and routing fit together. Tenant isolation: the guarantees 
 that keep each customer domain and its traffic separate from the rest. Ope
 rating it at scale: what a fully managed service handles for you and what 
 [...]
DTSTAMP:20260711T094257Z
LOCATION:Custom Domain
SUMMARY:Edge TLS and Tenant Isolation for Multi Tenant SaaS
X-ALT-DESC;FMTTYPE=text/html:<a href="https://customdomain.ai/event/edge-tl
 s-and-tenant-isolation-for-multi-tenant-saas-19">Edge TLS and Tenant Isola
 tion for Multi Tenant SaaS</a>\nIf you run a multi-tenant platform\, your 
 customers want their product to live on their own domain\, and every one o
 f 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 thro
 ugh how an edge terminates TLS\, how it routes each request to the right t
 enant\, and how certificate issuance and renewal happen on demand so a cus
 tomer 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 i
 s 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 se
 conds. Who this is for This is built for platform and security engineers a
 t 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
  The shape of the system: control plane responsibilities and edge responsi
 bilities\, and where the boundary sits. Connecting a domain three ways: on
 e click provider authorization\, a provider API token\, and a guided manua
 l flow that verifies automatically. TLS at the edge: certificate issuance\
 , renewal\, and how termination and routing fit together. Tenant isolation
 : the guarantees that keep each customer domain and its traffic separate f
 rom the rest. Operating it at scale: what a fully managed service handles 
 for you and what [...]
END:VEVENT
END:VCALENDAR