Yardstick records what your machine actually did — where it lost its position, where it stopped, which corner of the garden it never finishes — and shows it to you on a map of your own yard. It runs on your computer, on your own network.
A robotic mower publishes far more about itself than any app displays: satellite quality, heading confidence, correction age, blade currents, every cell temperature in the battery. All of it arrives on your network and then disappears, because nothing is listening.
Yardstick listens, keeps it, and turns it into sentences you can act on.
Not "coverage was 94%". A place, a size, a direction from the dock, and how often it has gone wrong — so you know whether to move the route or cut a branch.
A map of your yard coloured by how well the machine was positioned there, across every session — not one run, all of them.
Places that keep going wrong, grouped by what you would do about them: sky view, or the correction stream from your Data Center.
Recorded area beside the job's real size, so a patch is never mistaken for the whole yard.
All six cell temperatures and both blade currents over time, so a cell drifting hot shows up months before it strands you.
Stuck, stopped in the yard, left the map, cannot get home. Every threshold set by replaying real recordings — roughly one alert every three hours, and each one a real event.
A full-screen summary for a television: progress, battery, speed, signal. Alerts take over the screen in red.
Yardstick talks to your Data Center directly over your own network. It does not depend on anybody's cloud being up — which matters, because that is the part that goes down. When the app loses your machine, Yardstick usually carries on recording.
The recordings live in a single database file on your computer. Nothing is kept anywhere else.