<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Includeos on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/includeos/</link>
    <description>Recent content in Includeos on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 04 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/includeos/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Unikernel Platforms: Unikraft vs Nanos vs IncludeOS vs MirageOS</title>
      <link>https://www.pistack.xyz/posts/2026-06-04-self-hosted-unikernel-platforms-unikraft-nanos-includeos-mirageos-guide/</link>
      <pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-04-self-hosted-unikernel-platforms-unikraft-nanos-includeos-mirageos-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Traditional virtualization runs a full operating system for every application, duplicating kernel services and wasting resources. Unikernels take the opposite approach: compile your application directly into a minimal, single-purpose kernel image that runs directly on the hypervisor. The result is boot times measured in milliseconds, memory footprints under 10 MB, and attack surfaces orders of magnitude smaller than a full VM.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
