{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/c08196e3a28543e29872938afd7296f7\" frameborder=\"0\" width=\"1214\" height=\"910\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":910,"width":1214,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":910,"thumbnail_width":1214,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/c08196e3a28543e29872938afd7296f7-b956bf8d6618fbfd.gif","duration":458.62,"title":"Multi Tenant Routing in BreedLedger Explained 🚀","description":"Hey, I am Dusty, and in this Loom I show the multi tenant routing I implemented in BreedLedger. Every request goes through one resolve function that handles localhost, root domain for the marketing site, custom domains, and then subdomains, trying tenants first for backward compatibility and then falling back to organizations. I explain the discriminated union resolve entity, the dev tenant switch via a DevTenant slug, and how cookie domain and Superbase session token propagation work across subdomains. I also cover rewrite logic for single collection clean URLs, plus platform route gatekeeping with canonical 301 redirects. I do not request any action from viewers."}