We build the tools robotics teams keep rebuilding.

01 — WHY WE STARTED

Eight years of fielding robots taught us where the time goes.

Jack Morrison and Davis Foster previously founded Scythe Robotics, where they spent eight years taking an autonomous commercial mower from concept to hundreds of machines working daily across the country. Generation after generation went out to the field, first to sites near the shop, then later to customers thousands of miles away.

And for most of those years, the fleet ran on a rollout tool cobbled together for the first few robots. It worked when the fleet was small. Later, a routine update could leave engineers awake until 2 a.m. fighting failed transfers and special-snowflake machines. Some customers had to pull robots out of sheds at an agreed time so we could push new software.

We knew we needed something better. We also had models to train, blades to test, machines to build, and customers to serve. Nobody buys a robot because of how the deployment sausage gets made — so the rollout system fell to the bottom of the list, again and again.

That story plays out across robotics. Nearly every team has stitched together web, cloud, and IoT tools and made them kind of work. Engineers know which scripts to run and which errors to ignore. Fleet managers learn to call the one person who understands the whole thing. Everyone knows it needs work. Everyone has a robot to build.