Build with us.

Game engines democratized game development. We are doing it for defense.

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.

Same environment, same interfaces, whichever layer is yours.

Drone and component makers
You bring

Your airframe, flight controller, sensor or radio.

You get back

How it behaves against a live opponent in a real place, before you have a permit or a range.

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 against a hostile force, with a person able to take over mid-mission.

Command, control and mission planning
You bring

Your planning or command software.

You get back

A whole unit running under it in a contested scenario, and where coordination breaks.

A vessel model on the vehicle editor grid, with its axes drawn through it.
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, and it becomes a vehicle in the environment. 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
Every unguided round says whether its drag is sourced, fitted, default or extrapolated.
The loop

The loop is the product.

The point is not the single run. It is how short the distance gets 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 from one command with nobody at the keyboard, and a script scores it. Change something, run it again, and compare.

From the twin to test day

Arrive at test day with a system that already works.

Digital twin. Software in the loop. Hardware in the loop. 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 for European defense.

In our environment, in a dedicated one for you, or offline on your own premises. European models, or your own. Your code and data stay in Europe.

Interfaces

Open, and the ones you already use.

Connecting your system is integration, not invention.

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

Sensor metadata as KLV, streamed over SRT.

JSON Schema

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

Meet tomorrow’s threats before they arrive.

Build with us. We are building Coldrange in the open, with partners. If you build drones, autonomy, command software or the components inside them, or defend what they threaten, tell us what you need to prove.

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.