OpenFarm: Open-Source Vertical Farming Cooperative

OpenFarm was conceived as a response to the growing demand for local, sustainable food in cities. Unlike proprietary vertical farming systems that are black boxes requiring expensive service contracts, OpenFarm releases all designs, BOMs, firmware, and software under open-source licenses. The business model is a cooperative: members pay a subscription for the hardware kit, ongoing upgrades, and access to a shared knowledge base. The core product is a modular, stackable growing unit with LED lighting, hydroponic or aeroponic delivery, and sensors for pH, EC, temperature, humidity, and CO2. All firmware runs on Arduino/Raspberry Pi; the software stack includes a monitoring dashboard and a recipe-sharing platform. The co-op organizes local 'build parties' to assemble units, creating community engagement and reducing costs. Ultimately, OpenFarm aimed to franchise the model: each city chapter would have a shared workshop, tool library, and training program.

Most vertical farming systems are proprietary, expensive, and require constant vendor lock-in. Individuals or small co-ops cannot easily build or modify their own systems, and the technology is not accessible to underserved communities. OpenFarm addresses the itch for real food sovereignty and democratized technology.

• Design and release version 1.0 of the open-source vertical farm unit under CERN OHL or similar.
• Recruit 100 founding members to form the initial cooperative.
• Set up a shared workshop space with CNC routing, 3D printing, and electronics assembly.
• Build a user-friendly web dashboard for monitoring and control.
• Create a GitHub repository with full documentation, assembly guides, and a contribution guide.
• Establish partnerships with local universities for testing and validation.
• Achieve cost parity with equivalent proprietary systems within 18 months.
• Launch a 'farm-in-a-box' subscription model at $49/month (including seeds, nutrients, and replacement parts).
• Develop a recipe-sharing platform where users can share plant growing schedules.

• We are not building a proprietary cloud platform—data will be stored locally with opt-in sharing.
• Not targeting large-scale commercial farms (at least initially); focus on home and community gardening.
• Not designing for maximum yield per square foot; prioritizing simplicity, repairability, and cost.
• Not planning to raise traditional VC funding; we will use a co-op equity model and crowdfunding.
• Not selling data or advertising; the co-op exists to serve members.

• Materials: extruded aluminum T-slot framing, acrylic panels, waterproof LED strips (red/blue/white), PVC or repurposed plumbing for hydroponics, peristaltic pumps, nebulizers for aeroponics, environmental sensors (BME280, pH probe, EC probe, soil moisture), Raspberry Pi 4, Arduino Mega, power supply (12V/24V DC bus).
• Tools: 3D printers (for brackets), CNC router for custom parts, soldering stations, multimeters, oscilloscope, woodworking tools for optional cabinets.
• Software: Node-RED for dashboard, MQTT for sensor communication, InfluxDB for time-series data, Grafana for visualization, GitHub for version control, KiCad for electronics design, OpenSCAD for 3D modeling.
• Method: Iterative prototyping with community feedback; all testing documented in public logs.

The system is modular. Each 'tower' consists of a base unit with reservoir and pump, a vertical column with plant sites, and a top cap with LED array. The controller is a Raspberry Pi Zero 2W running Node-RED, connected to an Arduino that reads sensors via I2C and controls pumps/LEDs via relays. The Pi runs a local web server with the dashboard. Data flows: sensors -> Arduino -> serial -> Pi -> MQTT broker -> InfluxDB -> Grafana. The Pi can also connect to a local network for remote access, but the system is completely offline-capable. The recipe format is a JSON file that defines light schedule, nutrient mix, water cycles, and environment targets. These can be shared via a public git repo. The physical structure is designed to be assembled with common tools; all fasteners are metric and readily available. The system is stackable: multiple towers can be connected to a single reservoir.

• High upfront hardware cost for prototyping and tooling.
• Community may not self-organize to contribute effectively.
• Reliability of open-source designs for critical food production.
• Competition from low-cost Chinese hydroponic kits that are 'open-washed.'
• Difficulty in sourcing certified components consistently.
• Co-op governance could become contentious.

• What license to use? CERN OHL v2 strongly reciprocal vs. Apache 2 with patent grant.
• How to handle liability if a unit fails and plants die? Disclaimer or warranty from co-op?
• Should we offer a pre-assembled option even though that contradicts the build-party ethos?
• What is the optimal unit size for a standard apartment vs. a community center?
• How to standardize the recipe format so it can be shared across different hardware versions?

The founder shifted careers after a family emergency and the window for a co-op launch missed a key crowdfunding momentum. The plans and BOM are still on GitHub, but the project never secured enough active contributors to build the first 10 units. Sometimes a good idea just stays an idea.

This plan was developed over 2 years of weekend research and one 3-day hackathon prototype. The repo has 47 stars and a few issues. It's still open to anyone to pick up.