Understand the ground. Design what grows on it. Build it with certainty. Keep it alive for decades — one connected system, not a pile of separate decisions.
Why TerraOS
Designers, contractors, suppliers, and owners each work from a different mental model of the same ground — different assumptions about light, soil, water, and what a plant actually needs to survive there.
Nothing connects what's known to what gets built, so knowledge gets recreated, lost, and disconnected from one stage to the next.
TerraOS is the shared intelligence layer that connects them — one system that carries a site's knowledge from the ground, through design, into what actually gets built and kept alive.
Where a site's conditions get understood — the point everything else in TerraOS moves from.
How sun and shade actually move through a site, and what that means for every plant on it.
What's under the surface, and how it decides what will thrive above it.
Drainage and retention — how much water a spot really holds onto.
Where a species actually wants to live, not just where it looks good in a render.
Every species we specify, with the conditions it needs to survive here.
Where that understanding becomes a plan — the same knowledge, applied to an actual site.
Species grouped the way they'd grow together in the wild — not just color-matched.
Enclosed, shaded, humid — built for the microclimate a courtyard actually has.
Wind, weight limits, and reflected heat — solved before you buy a single pot.
Low light, low maintenance, and still alive in year three.
Park zones, pathways, and planting logic, planned as one system.
One dataset, start to finish: TerraScope captures the site, TerraDesign turns it into a planting plan, TerraCost prices and structures it, TerraExec builds and maintains it.
Converts site intelligence into build intelligence — a structured, itemised BOQ that carries straight through to TerraExec, not a one-off PDF.
Creates the digital foundation every other module builds on — capture zones, plants, and dimensions on your phone, straight into estimation.
Turns site conditions into a planting plan — a zone's light, soil, and water logic, resolved into what actually gets planted.
The BOQ becomes a work order — execution schedules, material dispatch, and the maintenance calendar that keeps it alive for years, not months.
The connecting layer
Every soil mix, planter, and amendment lives here — named at the point in the knowledge above where it belongs. Not a shop. A reference for what exists and what it's for, growing as more makers are added to the index.
Where everything above comes from — most companies keep this hidden. We don't.
One set of terms so every zone, plant, and material relates to the others consistently, across every module.
How a site's conditions connect to the right plants, soil, and detailing — automatically, not by memory.
The shared specifications that ensure products, plans, and execution follow the same rules across every project.
How species, zones, and materials get classified — and why that classification matters for design.