<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>os-alt blog</title>
  <subtitle>Monthly data on which self-hostable open-source SaaS alternatives are alive, stale, or dead.</subtitle>
  <link href="https://code-rho-dun.vercel.app/blog/" />
  <link rel="self" href="https://code-rho-dun.vercel.app/atom.xml" />
  <id>https://code-rho-dun.vercel.app/blog/</id>
  <updated>2026-05-10T00:00:00.000Z</updated>
  <author>
    <name>os-alt</name>
    <uri>https://code-rho-dun.vercel.app/</uri>
  </author>
  <entry>
    <title>When the OSS is alive but the license isn&apos;t: Sentry, MongoDB, Elasticsearch, Redis (May 2026)</title>
    <link href="https://code-rho-dun.vercel.app/blog/self-host-license-drama-2026-05/" />
    <id>https://code-rho-dun.vercel.app/blog/self-host-license-drama-2026-05/</id>
    <published>2026-05-10T00:00:00.000Z</published>
    <updated>2026-05-10T00:00:00.000Z</updated>
    <summary type="text">A fourth failure mode for our self-host directory — the code keeps shipping, the license stops being open. Four case studies (MongoDB 2018, Sentry 2019, Elasticsearch 2021, Redis 2024) and what the structural-explainer spine got wrong about half of them.</summary>
  </entry>
  <entry>
    <title>The Datadog escape hatch is real: observability is the OSS vertical that&apos;s actually winning (May 2026)</title>
    <link href="https://code-rho-dun.vercel.app/blog/self-host-datadog-alternatives-2026-05/" />
    <id>https://code-rho-dun.vercel.app/blog/self-host-datadog-alternatives-2026-05/</id>
    <published>2026-05-10T00:00:00.000Z</published>
    <updated>2026-05-10T00:00:00.000Z</updated>
    <summary type="text">Three of three self-host Datadog alternatives we list are alive and shipped this week. After two posts on OSS dying, observability is the vertical where it&apos;s actually winning — and the reason is OpenTelemetry, not the projects themselves.</summary>
  </entry>
  <entry>
    <title>The link-in-bio OSS market never had a Grafana — and it&apos;s quietly dying anyway (May 2026)</title>
    <link href="https://code-rho-dun.vercel.app/blog/self-host-link-in-bio-alternatives-2026-05/" />
    <id>https://code-rho-dun.vercel.app/blog/self-host-link-in-bio-alternatives-2026-05/</id>
    <published>2026-05-10T00:00:00.000Z</published>
    <updated>2026-05-10T00:00:00.000Z</updated>
    <summary type="text">Two of the three self-host Linktree alternatives we list aren&apos;t alive. The third hasn&apos;t shipped in 82 days. And unlike on-call OSS, there&apos;s no well-funded successor coming — link-in-bio is the OSS failure mode that happens when nobody is fighting to kill you.</summary>
  </entry>
  <entry>
    <title>We list 3 self-host PagerDuty alternatives. None of them are alive. (May 2026)</title>
    <link href="https://code-rho-dun.vercel.app/blog/self-host-pagerduty-alternatives-2026-05/" />
    <id>https://code-rho-dun.vercel.app/blog/self-host-pagerduty-alternatives-2026-05/</id>
    <published>2026-05-10T00:00:00.000Z</published>
    <updated>2026-05-10T00:00:00.000Z</updated>
    <summary type="text">The OSS on-call market is in trouble. Grafana archived their OnCall project. LinkedIn&apos;s Oncall hasn&apos;t shipped in 9 months. Cabot&apos;s GitHub repo is gone. Here&apos;s what we found, and what to self-host instead.</summary>
  </entry>
  <entry>
    <title>Most self-host SaaS alternatives are alive — but 13 of 118 aren&apos;t (May 2026)</title>
    <link href="https://code-rho-dun.vercel.app/blog/most-self-host-alternatives-are-still-alive-but-some-arent-2026-05/" />
    <id>https://code-rho-dun.vercel.app/blog/most-self-host-alternatives-are-still-alive-but-some-arent-2026-05/</id>
    <published>2026-05-10T00:00:00.000Z</published>
    <updated>2026-05-10T00:00:00.000Z</updated>
    <summary type="text">We scanned every GitHub repo recommended on os-alt as a self-hostable alternative to a paid SaaS. 6 are dead, 4 are stale, 3 we couldn&apos;t classify. Here&apos;s the full list with last-commit dates, and why a freshness signal matters more than star count when you&apos;re picking a self-host target.</summary>
  </entry>
</feed>
