<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Saas on Lorbic</title>
    <link>https://lorbic.com/tags/saas/</link>
    <description>Recent content in Saas on Lorbic</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 01 Jul 2026 00:00:00 +0530</lastBuildDate>
    <atom:link href="https://lorbic.com/tags/saas/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Multi-Tenant SaaS Actually Works</title>
      <link>https://lorbic.com/how-multi-tenant-saas-works/</link>
      <pubDate>Wed, 01 Jul 2026 00:00:00 +0530</pubDate>
      <guid>https://lorbic.com/how-multi-tenant-saas-works/</guid>
      <description>&lt;p&gt;For the past month I have been reading about multi-tenant SaaS architecture. Not as an academic exercise. I kept running into the same questions on every project I looked at: where exactly does tenant data go, how do you stop one customer&amp;rsquo;s bug from becoming every customer&amp;rsquo;s problem, how does billing actually work at the database level. The blog posts I found were either too abstract or skipped the hard parts entirely.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
