Skip to content
Free public beta until December 4, 2026: every course is open, no card needed. After that, the first chapter of each course stays free and full access is a one-time $39 ($19 for up to 100 founding members chosen for helpful feedback). Your progress is kept. How the beta works

monorepo

One repository holding every part of a system.

A monorepo keeps all parts of a system (firmware, back end, dashboard, contracts, hardware, documents) in one version-controlled repository, so a cross-part change is reviewed as one; releases may still be separate.

Examples

  • The greenhouse monorepo puts the climate v2 schema in contracts/climate.v2.json, the runbook in docs/runbook.md and the soil probe's KiCad project in hardware/soil_probe/.

  • One repository makes adding batt_mv to contract, firmware and ingester one reviewable change, but the back end must still deploy before any node sends it.

See also

formatter linter interface contract
Read the full section →