Grow-Dojo Stack (GrowDojo)
Summary
GrowDojo (github.com/Grow-Dojo/GrowDojo) is an open-source, modular, and scalable agricultural environment monitor and controller designed for "any crop, anywhere, using any cultivation method" — hydroponics, aquaponics, aeroponics, traditional farming, greenhouse, and closed-environment agriculture. The project is steered by an explicit ethos: decentralization, peer-based production, privacy and anonymity, trustless operation, apolitical stance, and right-to-repair. Its stated aims include being approachable to people new to devops or plant production, being replicable from easily accessible parts, letting each maker choose their own complexity level, and contributing a technical solution to food scarcity. Self-hosting is a first-class feature. The README notes that until repository management is fully delegated, the Rhizomatic Systems fork (github.com/Rhizomatic-Systems) carries more up-to-date management of the Grow-Dojo project, with forking welcome from either repo. License: GPL-3.0. Last push February 2026 — active, with discussions enabled on the management fork.
Guiding Principles
- Open Source — GPL-3.0, fork-friendly governance, right-to-repair as an explicit design value.
- Modularity — cultivation-method-agnostic controller architecture; complexity chosen by each maker.
- Food Sovereignty — positions decentralized crop production as a direct answer to politically exasperated food scarcity.
- Community Self-Sufficiency — peer-based production, self-hosting, and privacy/anonymity keep control with growers, not platforms.
Learning Outcomes & Transferable Skills
Builders develop Systems Thinking across whole growing environments, Coding and devops practice (containerized, self-hosted stacks), Electronics (sensors, actuators, accessible parts), and Project Management (choosing scope and complexity deliberately). The ethos documentation is itself a lesson in how values get encoded into technical architecture — useful for Sustainability Literacy discussions.
How to Replicate or Build On It
- Clone
https://github.com/Grow-Dojo/GrowDojo; check the README's pointer to the Rhizomatic-Systems organization for the freshest code and discussions. - Read the concept and ethos sections first to understand the intended deployment patterns (self-hosted, privacy-preserving).
- Start with a single cultivation module (e.g., one hydroponic loop) and add complexity incrementally, as the project intends.
- Contribute back via either repository — the project explicitly welcomes forks and delegation of management.
Considerations & Constraints
- Cost: Software free (GPL-3.0). Hardware cost scales with chosen complexity; the project emphasizes easily accessible parts.
- Skill Level: Advanced — devops/self-hosting literacy is assumed; the project aims to teach newcomers but the stack is non-trivial.
- Space/Climate: Cultivation-method-agnostic; indoor to greenhouse to open field.
- Tools Required: A host for the self-hosted stack (server/SBC), sensors and actuators per deployment, Git/GitHub fluency.
- Ongoing Maintenance: Self-hosted infrastructure requires upkeep; living systems require routine care.
- Access Barriers: Project is mid-governance-transition (main repo vs. Rhizomatic-Systems fork) — verify which repo is canonical before deep investment; English only.
Prerequisites
Basic Linux/self-hosting experience recommended.
