How it works.

Game engines democratized game development. We are doing it for drones and robots.

What you bring, what happens to it inside the environment, and what you get back.

Who builds in it

Bring what you build. Get back what it does.

The environment and the interfaces are the same, whichever layer is yours.

A fixed-wing drone over open sea, a second drone in the distance, and vessels low on the horizon.

Drone, robot and component makers

You bring

Your airframe, robot, flight controller, sensor or radio.

You get back

How it behaves in a real place, in the weather and traffic it will meet, before you have a permit.

A container port with each crane marked as an obstacle volume, under cloud.

Autonomy and AI teams

You bring

Your autonomy stack, as the controller in a driving, helm, dive or flight station.

You get back

Hours of decisions in a real place, with a person able to take over mid-run.

A city interchange and the streets around it, as a 3D map.

Fleet, ground control and route planning

You bring

Your planning or command software.

You get back

A whole fleet running under it, and where coordination breaks.

Getting your system in

Give it the operating information and it becomes a vehicle.

Bring your own 3D model, or have an AI draft one from photos. The library grows without a modeling contract for each one.

Sourced
Every figure can record where its number came from.
Rated
And how much to trust it.
Labeled
Each aerodynamic figure says whether it is sourced, fitted, default or extrapolated.
A cargo ship model on the vehicle editor grid, with its axes drawn through it.
The loop

Run, see, change, run again.

The aim is a short distance between a change and the evidence that it worked, before anything is cut, welded or flown.

The Coldrange ring as a loop, running clockwise from Run to See to Change. The ring is open at Change, where your change plugs in.

A trial runs unattended from one command, and a script scores it. Change a setting, a condition or the whole scenario, run it again, and compare.

From the twin to test day

Arrive at test day with a system that already works.

From digital twin to software in the loop, hardware in the loop and the real device, each step cuts the technical and design errors that reach the next. ArduPilot SITL is one of the ways in.

Four steps: digital twin, software in the loop, hardware in the loop, the real device. A band of marks for technical and design errors thins at each step, and only a few reach test day.
Where it runs

Built to keep your code and data in Europe.

In our environment, in a dedicated one for you, or offline on your own premises. European models, or your own.

  • Our environment
  • A dedicated one
  • Offline, on your premises
A container port with cranes and stacked containers.
Interfaces

Open, and the ones you already use.

MAVLink

Missions stored as MAVLink mission items, the format ArduPilot and QGroundControl use.

ArduPilot SITL

Your autopilot firmware flies the vehicle through ArduPilot’s own simulation interface.

MISB ST 0601

Camera and sensor metadata as KLV, streamed over SRT.

JSON Schema

Scenarios defined in a published schema, checked by a live validator.

Scenarios, runs and results are designed to be reached through the same open interface, by your software or your agents.

Tell us what you need to prove.

We are building Coldrange in the open, with partners. If you build drones, robots, sensors, autonomy or ground control software, or you are responsible for the places where they operate, write to us.

Write to us hello@coldrange.ai

Coldrange is new. The experience is not. The team has more than a decade of building hardware-in-the-loop systems, software that talks to real hardware from drones to tanks, including projects for NATO and the British military. It also brings decades of international business experience, and a track record of successfully building and scaling ecosystem products.