<?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: RIPUN BASUMATARY</title>
    <description>The latest articles on DEV Community by RIPUN BASUMATARY (@ripun).</description>
    <link>https://dev.to/ripun</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%2F3807997%2Fbf869616-2171-4091-9d70-79bff9d604d2.png</url>
      <title>DEV Community: RIPUN BASUMATARY</title>
      <link>https://dev.to/ripun</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ripun"/>
    <language>en</language>
    <item>
      <title>Why I Built Cockpit.run: A Visual Operating Surface for VPS Infrastructure</title>
      <dc:creator>RIPUN BASUMATARY</dc:creator>
      <pubDate>Thu, 05 Mar 2026 13:07:36 +0000</pubDate>
      <link>https://dev.to/ripun/why-i-built-cockpitrun-a-visual-operating-surface-for-vps-infrastructure-3gpe</link>
      <guid>https://dev.to/ripun/why-i-built-cockpitrun-a-visual-operating-surface-for-vps-infrastructure-3gpe</guid>
      <description>&lt;p&gt;If you run servers or deploy applications on VPS infrastructure, you probably know the workflow:&lt;/p&gt;

&lt;p&gt;SSH into a server → run commands → check logs → open monitoring dashboard → deploy again.&lt;/p&gt;

&lt;p&gt;It works, but it also creates a fragmented experience.&lt;/p&gt;

&lt;p&gt;Over time, managing servers becomes a mix of terminals, dashboards, scripts, and monitoring tools.&lt;/p&gt;

&lt;p&gt;I wanted something simpler - a unified surface where infrastructure can be observed and controlled visually.&lt;/p&gt;

&lt;p&gt;That’s why I started building &lt;strong&gt;Cockpit.run&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The goal of Cockpit.run is to provide an operating surface for VPS infrastructure where you can:&lt;/p&gt;

&lt;p&gt;• monitor server resources&lt;br&gt;
• manage multiple VPS instances&lt;br&gt;
• deploy applications&lt;br&gt;
• control infrastructure from a single interface&lt;/p&gt;

&lt;p&gt;Instead of juggling multiple tools, the interface acts more like a control layer for your servers.&lt;/p&gt;

&lt;p&gt;This project is still early, but I’m sharing it to get feedback from developers who run their own infrastructure.&lt;/p&gt;

&lt;p&gt;Showcase:&lt;br&gt;
&lt;strong&gt;&lt;a href="https://www.ripun.site/showcase/cockpit-operating-surface" rel="noopener noreferrer"&gt;https://www.ripun.site/showcase/cockpit-operating-surface&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Questions for the community:&lt;br&gt;
What tools do you currently use to manage servers?&lt;br&gt;
What features would make VPS management easier for you?&lt;/p&gt;

</description>
      <category>devops</category>
      <category>vps</category>
      <category>selfhosted</category>
      <category>serverless</category>
    </item>
  </channel>
</rss>
