<?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: GrowerZer0</title>
    <description>The latest articles on DEV Community by GrowerZer0 (@growerzer0).</description>
    <link>https://dev.to/growerzer0</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%2F4002730%2F3cbe968f-94a0-4eee-82e9-a193b5576386.png</url>
      <title>DEV Community: GrowerZer0</title>
      <link>https://dev.to/growerzer0</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/growerzer0"/>
    <language>en</language>
    <item>
      <title>Building a cultivation dashboard that stays on your hardware</title>
      <dc:creator>GrowerZer0</dc:creator>
      <pubDate>Tue, 30 Jun 2026 12:52:27 +0000</pubDate>
      <link>https://dev.to/growerzer0/building-a-cultivation-dashboard-that-stays-on-your-hardware-335o</link>
      <guid>https://dev.to/growerzer0/building-a-cultivation-dashboard-that-stays-on-your-hardware-335o</guid>
      <description>&lt;p&gt;&lt;em&gt;Early alpha dashboard — VPD tracking and dry-back cycle monitoring.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I've spent most of my career in logistics and maintenance. When I started growing, I looked for telemetry tools and found a lot of cloud subscriptions and data lock-in. So I'm building something different.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'm making:
&lt;/h2&gt;

&lt;p&gt;An open-source, local-first cultivation telemetry platform. VPD tracking, sensor ingestion, modern dashboard — all on your own hardware. No monthly fees. No data leaving your network unless you want it to.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why local-first:
&lt;/h2&gt;

&lt;p&gt;I've seen too many systems fail because they depended on someone else's servers. I want data safety, redundancy, and control. That means:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;PGMQ with read() + delete()&lt;/strong&gt; for bulletproof ingestion&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Next.js dashboard&lt;/strong&gt; that talks to your own PostgreSQL instance&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Full Docker Compose setup&lt;/strong&gt; for easy deployment&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where it's at right now:
&lt;/h2&gt;

&lt;p&gt;Early alpha. The dashboard is functional but rough. The architecture is solid but unproven. That's why I'm putting it on GitHub — to get feedback, find blind spots, and make it better with help from people who actually grow.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'm not building:
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A walled-garden ecosystem&lt;/li&gt;
&lt;li&gt;A product that forces your data into the cloud&lt;/li&gt;
&lt;li&gt;A black-box platform that phones home&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Get Involved
&lt;/h2&gt;

&lt;p&gt;The repo is completely open-source: &lt;a href="https://github.com/growerzer0/cultivatorsledger" rel="noopener noreferrer"&gt;github.com/growerzer0/cultivatorsledger&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I'm new to open-source. I'd highly appreciate:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Code reviews&lt;/li&gt;
&lt;li&gt;Architecture feedback&lt;/li&gt;
&lt;li&gt;Feature requests from real growers&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'll be posting architecture deep-dives next. Drop your thoughts or hardware setup in the comments below!&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>selfhosted</category>
      <category>nextjs</category>
      <category>postgres</category>
    </item>
  </channel>
</rss>
