<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Freedombox on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/freedombox/</link>
    <description>Recent content in Freedombox on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 15 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/freedombox/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Application Sandboxing Platforms: Sandstorm vs FreedomBox vs Cloudron Compared</title>
      <link>https://www.pistack.xyz/posts/2026-06-15-self-hosted-application-sandboxing-sandstorm-freedombox-cloudron/</link>
      <pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-15-self-hosted-application-sandboxing-sandstorm-freedombox-cloudron/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Running self-hosted web applications typically means managing multiple Docker containers, configuring reverse proxies, handling SSL certificates, setting up authentication, and maintaining separate databases for each app. Self-hosted application platforms aim to collapse this complexity into a unified management experience — an &amp;ldquo;app store&amp;rdquo; for your own server. But different platforms take fundamentally different approaches to security, isolation, and application packaging.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
