<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ota on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/ota/</link>
    <description>Recent content in Ota on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/ota/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Firmware OTA Update Management: Eclipse hawkBit vs RAUC vs SWUpdate</title>
      <link>https://www.pistack.xyz/posts/2026-05-07-self-hosted-firmware-ota-update-management-hawkbit-rauc-swupdate-guide/</link>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-07-self-hosted-firmware-ota-update-management-hawkbit-rauc-swupdate-guide/</guid>
      <description>&lt;p&gt;Managing firmware updates across hundreds or thousands of embedded devices is one of the most challenging aspects of IoT deployment. Over-the-Air (OTA) update systems allow you to push firmware images, configuration changes, and security patches to devices remotely, eliminating costly physical visits. While cloud-based OTA services exist, self-hosting your OTA infrastructure gives you full control over update rollouts, device enrollment, and data sovereignty.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
