About

Most lawn gadgets hand you a wall of numbers.

Then they leave the thinking to you. We think that gets it backwards. A sensor that reports 41.2% volumetric water content has told you nothing you can act on — the useful output is water for 22 minutes on Thursday morning, and not before. Getting from one to the other is the entire product.

Published modelsStated limits Your data leaves with you

FIG.01

The premise

The problem is not measurement. It is interpretation.

Soil moisture on its own is close to meaningless without context. Forty percent is soaking wet in sand and slightly dry in clay. The top inch of thatch dries out in hours while the root zone four inches down stays wet for days — which is exactly why a lawn can look thirsty on a hot afternoon and need no water at all. And demand is not a constant: a still, overcast 70°F day pulls a fraction of the water out of your turf that a windy, bright 95°F day does.

A sprinkler timer knows none of this. It knows what day it is. That is the whole reason people water their lawns twice as much as the grass actually wants.

FIG.02

The method

Grounded in published agronomy, not vibes

Every recommendation traces back to a model you can go and read. Watering demand comes from FAO-56 Hargreaves reference evapotranspiration, with the extraterrestrial radiation term computed from your latitude and the day of the year rather than assumed, then adjusted by a grass-specific crop coefficient. Soil moisture bands are matched to your soil type. Effective rainfall is subtracted from demand using what your own sensor recorded, not a regional forecast. Anomaly detection is statistical rather than a hand-tuned guess.

Caught in development
2.5×
Roughly — our ET₀ against the plausible value

This matters more than it sounds. During development we found our own ET₀ figure running at roughly two and a half times the physically plausible value because a radiation constant was being used in the wrong unit. Every watering runtime the system produced was inflated. Nobody would ever have noticed from the dashboard — it looked completely reasonable — which is precisely why the maths has to be checked against the literature rather than against whether the output feels about right.

Fig. 02 — The reason the models are named on this site at all. A number you cannot check against a published method is a number you have to take on trust, and this one would have passed every eyeball test in the building.

FIG.03

The limits we chose

What we deliberately do not do

  1. 01

    We do not sell your data.

    Not to advertisers, not to aggregators, not as an anonymised dataset. It exists so your dashboard works.

  2. 02

    We do not lock you into our hardware.

    Anything that speaks HTTPS, MQTT or LoRaWAN can report in. There is no proprietary hub, and there never will be — a hub is a way of making you buy a second thing.

  3. 03

    We do not hold features back for a higher tier.

    There is one price. The agronomy tools are the product; charging extra for them would be charging extra for the point.

  4. 04

    We do not control your sprinklers.

    Not yet, and not until we can do it without narrowing which irrigation systems you are allowed to own. Telling you the right answer works with a hose and a dial.

  5. 05

    We do not make cancelling difficult.

    One button, from the billing portal, no phone call, no retention script.

Fig. 03 — Five things this product will not grow into. Each one costs us something, which is the only reason writing them down means anything.

FIG.04

Where we actually are

The company is not new. The product is.

We have been at this since 2018. What is new is the product — so there is no install base to point at and no testimonials to quote, and we would rather say so than manufacture them.

What we can offer instead is specificity: the models are named, the thresholds are published in the FAQ, the limits are written down, and every reading you generate can be exported as CSV whenever you want it.

The practical upside of being early is access. Write to us and one of the two people who actually built the thing reads it, usually the same day. That does not scale forever, so enjoy it while it lasts — here is who you are writing to.

Questions before you buy?

The FAQ covers sensors, connectivity, accuracy, billing and privacy in detail. Anything it misses, just ask us.