<?xml version="1.0" encoding="UTF-8"?>
<!--
  Hand-maintained until cmd/marketing-blog generates it.

  Adding a post means editing this file, marketing/blog/index.html (both
  the visible list AND the `blogPost` JSON-LD array), and adding a <loc>
  to marketing/sitemap.xml. Keep <lastBuildDate> in step with the newest
  <pubDate>, and keep every <pubDate> in RFC 822 — feed readers reject
  ISO 8601 here, unlike everywhere else on this site.
-->
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Containarium Blog</title>
    <link>https://containarium.dev/blog/</link>
    <atom:link href="https://containarium.dev/blog/rss.xml" rel="self" type="application/rss+xml" />
    <description>Engineering notes on agent sandboxes, LXC internals, and container isolation from the team building Containarium.</description>
    <language>en</language>
    <copyright>© FootprintAI. Apache 2.0 for OSS components.</copyright>
    <lastBuildDate>Mon, 31 Aug 2026 12:00:00 +0000</lastBuildDate>
    <image>
      <url>https://containarium.dev/og.png</url>
      <title>Containarium Blog</title>
      <link>https://containarium.dev/blog/</link>
    </image>

    <item>
      <title>You should own everything. You don't have to run it.</title>
      <link>https://containarium.dev/blog/ownership-not-operations</link>
      <guid isPermaLink="true">https://containarium.dev/blog/ownership-not-operations</guid>
      <pubDate>Mon, 31 Aug 2026 12:00:00 +0000</pubDate>
      <description>Custody doesn't mean doing it all yourself. Owning something and running it are two different jobs, and only one has to be yours: hiring people to run your machines or scan your cloud is normal, and the teams caught by this leak had outsourced ownership along with the work. The four things you never hand over, the four tests of a healthy arrangement, and how a company with no IT staff moves onto its own cloud account. Also available in Traditional Chinese: https://containarium.dev/zh-tw/blog/ownership-not-operations</description>
    </item>

    <item>
      <title>Day two of the breach: custody, not trust</title>
      <link>https://containarium.dev/blog/custody-not-trust</link>
      <guid isPermaLink="true">https://containarium.dev/blog/custody-not-trust</guid>
      <pubDate>Sun, 30 Aug 2026 12:00:00 +0000</pubDate>
      <description>Day two of the PaaS credential leak: the official statement says only environment variables were exported; the rumors say far more. You can verify neither — and that verification gap is what you signed up for when you handed over custody. On trust vs. verify vs. custody, and the four rules of real BYOC. Also available in Traditional Chinese: https://containarium.dev/zh-tw/blog/custody-not-trust</description>
    </item>

    <item>
      <title>The day the secret store gets scraped: encryption boundaries, not firewalls</title>
      <link>https://containarium.dev/blog/secret-store-blast-radius</link>
      <guid isPermaLink="true">https://containarium.dev/blog/secret-store-blast-radius</guid>
      <pubDate>Sat, 29 Aug 2026 12:00:00 +0000</pubDate>
      <description>A PaaS platform leaked tenant environment variables — API keys in the open. The leak path in these incidents isn't lateral movement between clusters; it's one secret store scraped for every tenant at once. What to do in the first hour, why firewalls can't stop it, and the seven rules of a security boundary we build by. Also available in Traditional Chinese: https://containarium.dev/zh-tw/blog/secret-store-blast-radius</description>
    </item>

    <item>
      <title>Agent sandbox density: we lost by 2x, then found out why</title>
      <link>https://containarium.dev/blog/agent-sandbox-density-benchmark</link>
      <guid isPermaLink="true">https://containarium.dev/blog/agent-sandbox-density-benchmark</guid>
      <pubDate>Wed, 26 Aug 2026 12:00:00 +0000</pubDate>
      <description>Containarium scored half of upstream agent-sandbox's density on Kubernetes — 186 vs. 373. We root-caused it to a real CLI gap, shipped the fix, and re-ran: exact match, 373 vs. 373.</description>
    </item>

    <item>
      <title>Agent sandboxes on Kubernetes: gVisor breaks kubectl, not SSH</title>
      <link>https://containarium.dev/blog/gvisor-breaks-kubectl-not-ssh</link>
      <guid isPermaLink="true">https://containarium.dev/blog/gvisor-breaks-kubectl-not-ssh</guid>
      <pubDate>Sat, 22 Aug 2026 12:00:00 +0000</pubDate>
      <description>kubectl port-forward breaks under gVisor; kubectl exec doesn't. We hit the gap independently, then found our own SSH gateway was ALSO broken, for two unrelated reasons we found, root-caused, and fixed. What broke, what we got wrong the first time, and what's proven end to end now.</description>
    </item>

    <item>
      <title>Running untrusted agent code: the hole isn't escape, it's egress</title>
      <link>https://containarium.dev/blog/run-untrusted-agent-code</link>
      <guid isPermaLink="true">https://containarium.dev/blog/run-untrusted-agent-code</guid>
      <pubDate>Tue, 28 Jul 2026 12:00:00 +0000</pubDate>
      <description>"Untrusted" is three different threats, and most teams defend the wrong one — shopping for isolation technology while running with unrestricted outbound network access. What a container boundary actually buys you, what it doesn't, and when a box is the wrong tool.</description>
    </item>

    <item>
      <title>Scaling coding agents: five agents, five Linux boxes</title>
      <link>https://containarium.dev/blog/scaling-coding-agents</link>
      <guid isPermaLink="true">https://containarium.dev/blog/scaling-coding-agents</guid>
      <pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate>
      <description>Everyone uses a coding agent to write code; almost nobody talks about how to scale one up. Two things made it work for our team — a software quality process the agents actually follow, and one isolated Linux box per agent. Also available in Traditional Chinese: https://containarium.dev/zh-tw/blog/scaling-coding-agents</description>
    </item>

    <item>
      <title>The Best AI Agent Sandboxes in 2026 (Compared)</title>
      <link>https://containarium.dev/blog/best-ai-agent-sandboxes</link>
      <guid isPermaLink="true">https://containarium.dev/blog/best-ai-agent-sandboxes</guid>
      <pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
      <description>Containarium, E2B, Modal, and Daytona side by side on the things that actually decide the choice: self-hosting, persistence, isolation technology, license, MCP support, and cost. Written by a vendor in the space, so it says plainly where each competitor wins.</description>
    </item>

  </channel>
</rss>
