<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel>
    <title>iSleep Labs Blog</title>
    <link>https://isleep.dev/blog</link>
    <description>Engineering perspectives on smart mattresses, sleep data platforms and agent integration.</description>
    <language>en</language>
    <item>
      <title>A smart mattress is a stack, not a feature</title>
      <link>https://isleep.dev/blog/smart-mattress-stack</link>
      <guid>https://isleep.dev/blog/smart-mattress-stack</guid>
      <pubDate>Fri, 09 Oct 2026 00:00:00 GMT</pubDate>
      <description>Why sensing hardware, apps, data infrastructure and agent interfaces have to be designed together.</description>
    </item>
    <item>
      <title>Why Self-Hosted sleep data matters to mattress brands</title>
      <link>https://isleep.dev/blog/self-hosted-sleep-data</link>
      <guid>https://isleep.dev/blog/self-hosted-sleep-data</guid>
      <pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate>
      <description>Data residency becomes simpler when the architecture separates a customer data plane from a narrow cloud control plane.</description>
    </item>
    <item>
      <title>MCP for sleep data: a practical architecture</title>
      <link>https://isleep.dev/blog/mcp-for-sleep-data</link>
      <guid>https://isleep.dev/blog/mcp-for-sleep-data</guid>
      <pubDate>Sat, 26 Sep 2026 00:00:00 GMT</pubDate>
      <description>How to expose useful sleep tools to agents without turning MCP into an authorization bypass.</description>
    </item>
    <item>
      <title>From reference app to a white-label sleep product</title>
      <link>https://isleep.dev/blog/white-label-sleep-app</link>
      <guid>https://isleep.dev/blog/white-label-sleep-app</guid>
      <pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate>
      <description>What mattress brands should preserve—and what they should customize—when launching a sleep app.</description>
    </item>
  </channel></rss>
