<?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: Rajneesh Tiwari</title>
    <description>The latest articles on DEV Community by Rajneesh Tiwari (@rajneesh_tiwari_e0556afa6).</description>
    <link>https://dev.to/rajneesh_tiwari_e0556afa6</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2873263%2F279c3a4c-1b91-4a87-be66-bd2bc3bf2e47.png</url>
      <title>DEV Community: Rajneesh Tiwari</title>
      <link>https://dev.to/rajneesh_tiwari_e0556afa6</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rajneesh_tiwari_e0556afa6"/>
    <language>en</language>
    <item>
      <title>I built an open-source tool that shows your servers and databases as a living 3D city</title>
      <dc:creator>Rajneesh Tiwari</dc:creator>
      <pubDate>Fri, 13 Nov 2026 02:30:03 +0000</pubDate>
      <link>https://dev.to/rajneesh_tiwari_e0556afa6/i-built-an-open-source-tool-that-shows-your-servers-and-databases-as-a-living-3d-city-4p6d</link>
      <guid>https://dev.to/rajneesh_tiwari_e0556afa6/i-built-an-open-source-tool-that-shows-your-servers-and-databases-as-a-living-3d-city-4p6d</guid>
      <description>&lt;p&gt;Most infrastructure tools show you lists: servers, databases, alerts, all in rows. The problem with a list is that it re-sorts itself. When something goes wrong, you have to read it to find out what changed.&lt;/p&gt;

&lt;p&gt;So I built &lt;strong&gt;GRIDCITY&lt;/strong&gt;: an open-source (MIT), local-first console where every server, database, Redis instance and bucket is a building in a 3D city. A city stays put. You remember where things are, so a change of light is the first thing you notice.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffo42wqk6eh2yoecgb387.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffo42wqk6eh2yoecgb387.png" alt="GRIDCITY overview" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Try it in your browser (simulated data):&lt;/strong&gt; &lt;a href="https://chapeee.github.io/GRIDCITY/demo/" rel="noopener noreferrer"&gt;https://chapeee.github.io/GRIDCITY/demo/&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Code:&lt;/strong&gt; &lt;a href="https://github.com/chapeee/GRIDCITY" rel="noopener noreferrer"&gt;https://github.com/chapeee/GRIDCITY&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Rule one: every light means exactly one thing
&lt;/h2&gt;

&lt;p&gt;The thing I cared about most is that the picture never lies.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Edge pulse speed is CPU.&lt;/li&gt;
&lt;li&gt;Light strips filling upward are memory.&lt;/li&gt;
&lt;li&gt;A segmented ring at the base shows each disk; an amber arc means that disk is nearly full.&lt;/li&gt;
&lt;li&gt;Particles rising around a tower are network throughput.&lt;/li&gt;
&lt;li&gt;An &lt;strong&gt;offline&lt;/strong&gt; server is dark and motionless.&lt;/li&gt;
&lt;li&gt;A server whose data &lt;strong&gt;stopped arriving&lt;/strong&gt; freezes, greys out and shows "last seen".&lt;/li&gt;
&lt;li&gt;Replay is always labelled REPLAY.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Databases are drums, Redis is a hexagonal prism, buckets are low warehouses. A pretty view that shows a dead server as healthy is worse than no view at all, so "truth first" is the one principle I don't bend.&lt;/p&gt;
&lt;h2&gt;
  
  
  It's not just a picture
&lt;/h2&gt;

&lt;p&gt;Looking at the city is the starting point. From there:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Jack in:&lt;/strong&gt; press Enter on a building for a real SSH terminal.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Manage data:&lt;/strong&gt; press M on a database for a SQL manager (PostgreSQL, MySQL/MariaDB, SQL Server, SQLite), a key browser and console for Redis, documents for MongoDB, and a file browser for S3, Spaces, MinIO and R2. Everything opens &lt;strong&gt;read-only&lt;/strong&gt;, enforced by the database itself, until you click "Allow changes", and every change is audited.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Security:&lt;/strong&gt; SSH brute force, a login right after failed guesses, a new root account, a public bucket or a database open to the internet puts a red ring on the building. CrowdSec and Fail2ban findings show up too.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Alerts with the app closed:&lt;/strong&gt; browser push, email, Slack, Discord, Telegram, Teams, ntfy, Gotify, Pushover and Apprise.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Time travel:&lt;/strong&gt; press T and drag back to last night's incident, then press Play and watch it unfold.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzjev5m3issycgz1mjcqk.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzjev5m3issycgz1mjcqk.png" alt="Focusing a host" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  The Doctor: prove the fix before suggesting it
&lt;/h2&gt;

&lt;p&gt;"Could not connect" is the least helpful error in ops. When a connection fails, the Doctor climbs DNS → port → TLS → login, matches the real error against its rules, recognises managed providers, and then &lt;strong&gt;tries each candidate fix with a real read-only connection&lt;/strong&gt;. You get something like "Turn on TLS: proven, connected with this change" instead of a guess. It also runs headless: &lt;code&gt;gridcity doctor --json&lt;/code&gt; works in CI.&lt;/p&gt;
&lt;h2&gt;
  
  
  Letting an AI near your servers, safely
&lt;/h2&gt;

&lt;p&gt;GRIDCITY is also an MCP server, so Claude Code, Cursor or any MCP client can call tools like &lt;code&gt;incident_report&lt;/code&gt; (everything unhealthy, grouped by likely root cause), &lt;code&gt;diagnose&lt;/code&gt;, &lt;code&gt;get_topology&lt;/code&gt; and &lt;code&gt;security_findings&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The one tool that changes anything is &lt;code&gt;run_command&lt;/code&gt;, and it never runs on its own. Every command the AI wants to run shows up as an approval card in the city: the exact command, the server, and the AI's reason. You click Allow or Deny. If a command needs a sudo password, you type it into the card, and it goes to the command, never to the model.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx gridcity        &lt;span class="c"&gt;# start it&lt;/span&gt;
npx gridcity mcp    &lt;span class="c"&gt;# prints the command to connect Claude Code&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Private by design
&lt;/h2&gt;

&lt;p&gt;It runs on your machine and listens on 127.0.0.1 only. It connects outward over your existing SSH keys and installs nothing on your servers (one read-only script reads /proc and df). No cloud, no account, no telemetry. Credentials you paste are stored encrypted locally.&lt;/p&gt;

&lt;h2&gt;
  
  
  Honest limits
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;It's single-user and local by design.&lt;/li&gt;
&lt;li&gt;Remote servers must be Linux.&lt;/li&gt;
&lt;li&gt;It keeps days of history (7 by default, up to 90), so it is not a Prometheus or Grafana replacement.&lt;/li&gt;
&lt;li&gt;It catches known attack patterns, not every attack.&lt;/li&gt;
&lt;li&gt;It's v0.4, so expect rough edges.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx gridcity demo   &lt;span class="c"&gt;# a simulated city, no setup at all&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;or with Docker:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker run -d --name gridcity -p 127.0.0.1:4600:4600 \
  -v gridcity-config:/config -v gridcity-data:/data ghcr.io/chapeee/gridcity
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I'd love feedback, especially on one question: does the city view actually help you spot problems faster than a list? Issues and ideas are welcome on GitHub: &lt;a href="https://github.com/chapeee/GRIDCITY" rel="noopener noreferrer"&gt;https://github.com/chapeee/GRIDCITY&lt;/a&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>devops</category>
      <category>selfhosted</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
