From Data to Dirt: How We Develop Off-Road Autonomy

When people picture an autonomous vehicle, they usually imagine the finished product: a machine moving through rough terrain, no driver, no hesitation. What stays invisible is everything that happens long before that first autonomous drive across a field or forest track — the slow, deliberate work of teaching software to understand the world around it.

For us, that work begins with data.

Every capability begins with observation

Before the Autonomy Kit can make a single decision, it has to understand what it sees. Is this surface drivable? Does the path continue around the corner? Is that vegetation an obstacle — or just scenery?

Answering these questions takes real-world observation. So we start by recording sensor data in representative environments. Every route, every terrain type, every change in weather and light adds another piece to our understanding of the operational domain.

The principle is simple: collect real data first, instead of trying to solve every imaginable problem on paper.

Turning data into insight

Raw recordings are where the engineering really starts. We use them to test early versions of our perception software and to compare different approaches under identical conditions.

This is how theory becomes knowledge. Patterns become visible, challenges become concrete, and assumptions turn into hypotheses we can actually test. Step by step, a clearer picture emerges of how an autonomy function should behave in the field.

From insight to virtual validation

Once we've got those recordings, the real work begins. We use them to test early versions of the perception software and to put different approaches head-to-head under exactly the same conditions. That last part matters more than it sounds — when everything runs against the same data, you can actually tell which approach is better, instead of guessing.

This is the stage where raw recordings turn into genuine engineering knowledge. Patterns start to jump out. The tricky edge cases become visible. And vague ideas turn into concrete questions we can actually test. By the end of it, we have a much clearer sense of how a given function should behave out in the field.

Closing the loop with physical demonstrators

Of course, virtual validation alone is never enough. At the end of the day, the Autonomy Kit has to work in the dirt.

That's why we bring in physical demonstrators early and step by step, instead of all at once. Small platforms and prototypes let us validate integration, perception behaviour and system interactions before we move to the larger UGVs — our actual target platform. It's the best of both worlds: the speed of software development, grounded by the honesty only real hardware can provide.

Why this matters

The real value of this process isn't just efficiency — it's confidence. Every stage adds evidence. Every validation reduces uncertainty.

By the time a feature reaches the target platform, it has already passed through multiple learning loops: software development, data collection, virtual analysis and physical testing. So we don't treat UGV trials as the starting line. They're simply the next step in a process that's been running all along.

The path from data to dirt

Off-road autonomy comes down to one hard problem: operating reliably in a world that's messy and unpredictable. Pulling that off takes more than a clever vehicle. It takes data, analysis, understanding and testing — and, just as importantly, a way of working that ties all four together.

That's what "from data to dirt" really means for us. Not a single project, but a loop we keep running: start by observing, end up in real terrain, and let every step build toward autonomy you can actually trust.