<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Павел Веткин</title>
    <description>The latest articles on DEV Community by Павел Веткин (@__95bd8e69142b).</description>
    <link>https://dev.to/__95bd8e69142b</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2010574%2F60376911-6bdf-4280-8967-61aba8c97a07.png</url>
      <title>DEV Community: Павел Веткин</title>
      <link>https://dev.to/__95bd8e69142b</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/__95bd8e69142b"/>
    <language>en</language>
    <item>
      <title>I was tired of Backstage eating 16GB RAM, so I built a lightweight alternative in Python</title>
      <dc:creator>Павел Веткин</dc:creator>
      <pubDate>Mon, 23 Mar 2026 18:01:11 +0000</pubDate>
      <link>https://dev.to/__95bd8e69142b/i-was-tired-of-backstage-eating-16gb-ram-so-i-built-a-lightweight-alternative-in-python-3jof</link>
      <guid>https://dev.to/__95bd8e69142b/i-was-tired-of-backstage-eating-16gb-ram-so-i-built-a-lightweight-alternative-in-python-3jof</guid>
      <description>&lt;p&gt;Our team needed a developer portal — a single place to track services, APIs, teams, and ownership. Backstage was the obvious choice, but the reality was painful: Node.js + React + TypeScript plugins, complex deploy, and 16GB RAM just to run it.&lt;/p&gt;

&lt;p&gt;So I built &lt;strong&gt;FrontStage&lt;/strong&gt; — an open-source alternative that does the same job without the complexity.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Stack:&lt;/strong&gt; Python/FastAPI, Alpine.js, Tailwind, Redis, YAML configs, Docker Compose&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key differences vs Backstage:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;1GB RAM vs 16GB&lt;/li&gt;
&lt;li&gt;0.8 CPU vs 4 CPU&lt;/li&gt;
&lt;li&gt;No React, no TypeScript plugins — just Python and simple templates&lt;/li&gt;
&lt;li&gt;Your DevOps team already knows the stack&lt;/li&gt;
&lt;li&gt;One repo, readable code — easy to customize yourself or with AI assistants&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;What it does today:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Software Catalog: services, APIs, databases, libraries, teams&lt;/li&gt;
&lt;li&gt;Ownership tracking ("who owns this microservice?")&lt;/li&gt;
&lt;li&gt;Swagger docs out of the box&lt;/li&gt;
&lt;li&gt;Works great as a RAG data source (structured YAML = easy to index)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Quick start is just &lt;code&gt;docker compose up&lt;/code&gt;. YAML configs, no database migrations.&lt;/p&gt;

&lt;p&gt;MIT license. Would love feedback from anyone who's dealt with Backstage pain.&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/denisxab/frontstage/tree/master" rel="noopener noreferrer"&gt;https://github.com/denisxab/frontstage/tree/master&lt;/a&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>performance</category>
      <category>python</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
