{"podcast":{"title":"No Compromises","slug":"no-compromises-1309932","podcast_index_feed_id":1309932,"rss_url":"https://feeds.transistor.fm/no-compromises","website_url":"https://show.nocompromises.io","image_url":"https://img.transistorcdn.com/z6cTh6hcjDJiOBZWkONVdabUkSvSMha6ir6ZU7zqiNs/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzIzMDM3LzE2Mjc1/MjExMTAtYXJ0d29y/ay5qcGc.jpg","author":"Joel Clermont and Aaron Saray","episode_count":157,"summary":"Two seasoned salty programming veterans talk best practices based on years of working with Laravel SaaS teams.","last_synced_at":"2026-07-19T04:20:23.931944+00:00","page_url":"https://stenobird.com/podcast/no-compromises-1309932"},"episode":{"title":"Do you actually need a multi-tenancy package?","slug":"do-you-actually-need-a-multi-tenancy-package","published_at":"2026-04-25T05:00:00+00:00","page_url":"https://stenobird.com/podcast/no-compromises-1309932/do-you-actually-need-a-multi-tenancy-package","show_page_url":"https://stenobird.com/podcast/no-compromises-1309932","url":"https://share.transistor.fm/s/9ea352fe","audio_url":"https://media.transistor.fm/9ea352fe/7b83beef.mp3","summary":"Ever feel like a project requirement says \"we need multi-tenancy,\" and you're not even sure what that means in your specific context? In the latest episode of the No Compromises podcast, we discuss how to evaluate multi-tenancy needs before committing to an architectural approach. We break down what multi-tenancy actually means, from separate databases to custom domains and per-tenant configuration, and why the real question isn't which package to use, but whether you need one at all. We also explore when hand-rolling a simple solution beats adopting a full package, what legal and compliance requirements can force your hand, and why this is one of those decisions that's genuinely hard to undo later. 00:00 Defining what multi-tenancy actually means 02:11 Different ways to structure multi-tenant systems 03:44 When separate databases are truly necessary 04:57 Questions to ask before choosing an approach 08:25 Package vs. rolling your own trade-offs 11:30 Silly bit If you want guidance on decisions like these, check out our code review service to get expert eyes on your architecture.","meta_description":"Ever feel like a project requirement says \"we need multi-tenancy,\" and you're not even sure what that means in your specific context? In the latest episod…","key_points":[],"chapters":[],"topics":[],"duration_seconds":846,"processing_state":"not_requested","actions":[{"name":"request_transcript","method":"POST","url":"https://stenobird.com/v1/public/podcasts/no-compromises-1309932/episodes/do-you-actually-need-a-multi-tenancy-package/transcription-requests","description":"Idempotently request low-priority transcript generation for this episode."},{"name":"read_markdown","method":"GET","url":"https://stenobird.com/podcast/no-compromises-1309932/do-you-actually-need-a-multi-tenancy-package.md","description":"Read the agent-friendly Markdown representation of this episode resource."}]}}