From Zero to Ecosystem in 72 Hours

The Sprint

On February 21, 2026, The Void Grows existed as an idea and a collection of notes. By February 23, it was a fully operational ecosystem: a marketing website with 17+ pages, a companion app at v4.0, parametric CAD designs for three dome tiers, ESP32 firmware with climate control, and a public open-source repository with downloadable STL files.

This is not how products are supposed to get built. But we did it anyway.

Day One: Foundation

The first day was about decisions, not code. We wrote the brand bible. Researched cultivation requirements for six gourmet mushroom species. Defined the technical specifications for three product tiers. Mapped out a 9-phase development roadmap.

The critical insight from day one: mushroom cultivation hardware is not complicated, but it needs to be precise. Humidity control within a 10% window. Fresh air exchange without contamination. UV-C sterilization with hardware safety interlocks. Getting the specifications right before writing a single line of code saved us from rebuilding later.

We also made the decision to position The Void Grows around gourmet cultivation rather than general mycology. Lion's Mane, Oyster varieties, Shiitake, Reishi — species that people actually want to eat and use, not just grow as a novelty. This focus shaped everything that followed.

Day Two: Build Everything

Day two was the big push. We scaffolded the entire Next.js 15 website from scratch — homepage with species previews, product pages for all three dome tiers, individual species guides with cultivation parameters, a build documentation section with BOM and assembly steps, a species quiz, a blog, and a community page with timeline and contributor sections.

In parallel, we built the companion app. React 19 with TypeScript, a Zustand state management layer, a device communication abstraction that supports both local WiFi adapters and mock data, a full sensor dashboard with real-time readings, climate control interfaces, and PWA support for mobile. Capacitor integration for native iOS and Android builds. The app hit v4.0 by end of day.

On the hardware side, we designed the full dome in OpenSCAD — parametric models for the dome shell, vent caps, base housing, and substrate platform. The ESP32 firmware went from blank file to functional climate controller: BME280 sensor polling, PID-tuned humidity control, scheduled FAE cycling, LED ambient lighting, UV-C sterilization with hardware interlock, and a REST API for the companion app.

Day Three: Polish and Publish

Day three was about making everything real. The golden ratio cloche redesign replaced our initial dome geometry with proportions derived from the golden ratio — the same mathematical relationship found in natural mycelium branching patterns. The new design is not just more visually striking; the internal volume ratios between the growing chamber and air exchange plenum are optimized for airflow dynamics.

We built the brand identity system: Outfit typography, a UV-purple and bio-cyan color palette, and a custom mycelium network animation engine that uses bezier curves and golden ratio mathematics to generate organic branching patterns across the site.

The email subscriber system went live with species-specific welcome emails — take the quiz, get matched to a species, and receive a personalized welcome with cultivation tips for your recommended grow.

Most importantly, we published everything. The void-blueprints repository went public with all CAD files, firmware source code, build documentation, and a GitHub Action that automatically packages STL files on every release. v0.1.0 — the Golden Ratio Cloche — was the first tagged release.

What We Learned

Decisions before code. The brand bible and technical specifications from day one meant we never had to stop and debate direction during the build. Every page, every feature, every design choice flowed from decisions that were already made.

Parallel workstreams matter. Website, app, firmware, and CAD progressed simultaneously because they share interfaces, not implementations. The app talks to the firmware via a REST API contract defined on day one. The website references the same species data that the app uses. Decoupled systems build faster.

Open source from the start. We did not build first and open-source later. The public repository was part of the plan from day one. This forced clean documentation, clear file organization, and no shortcuts that would embarrass us later. When your code is public, you write it differently.

Ship the ecosystem, not just the product. A mushroom dome without a companion app is just a plastic shell. A companion app without species guides is just a dashboard. Species guides without build docs are just reading material. The value is in the complete ecosystem, and shipping it all together means every piece reinforces every other piece.

What Comes Next

The prototype build is underway. BOM components are being ordered, dome panels are queued for 3D printing, and the first physical Void Core unit will be assembled in March. After that: a full grow cycle test with real substrate blocks to validate the environmental controls under actual cultivation conditions.

The community is growing. Discord, Reddit, and GitHub are live. The virtual dome demo lets anyone experience the companion app without hardware. And every piece of the platform is open-source, ready for the first community contributors to fork, modify, and improve.

Three days from zero to ecosystem. Now the real work begins — growing mushrooms.

Follow the project on our community page or check the progress dashboard for real-time milestone tracking.