<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>SaaSLayer</title>
    <link>https://saaslayer.com</link>
    <description>Sign-in, organizations, and application permissions in your AWS account. SaaSLayer is a controlled user-service and Permissions beta with assisted setup.</description>
    <item>
      <title>Why we build SaaSLayer on top of AWS instead of hiding AWS</title>
      <link>https://saaslayer.com/blog/on-top-of-aws-not-hiding-it/</link>
      <guid>https://saaslayer.com/blog/on-top-of-aws-not-hiding-it/</guid>
      <description>Abstractions that hide your cloud eventually fight you. SaaSLayer is an experience layer over AWS primitives you can still see and audit.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>One-read permission checks for multi-tenant SaaS</title>
      <link>https://saaslayer.com/blog/one-read-permission-checks/</link>
      <guid>https://saaslayer.com/blog/one-read-permission-checks/</guid>
      <description>Why SaaSLayer materializes effective permissions into DynamoDB documents so the authorization hot path stays cheap and boring.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why the SaaS layer becomes its own product</title>
      <link>https://saaslayer.com/blog/why-the-saas-layer-becomes-its-own-product/</link>
      <guid>https://saaslayer.com/blog/why-the-saas-layer-becomes-its-own-product/</guid>
      <description>Every multi-tenant product eventually rebuilds the same platform layer. It deserves to be treated as a product, not a side quest.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
