Mission software and onboard AI for unmanned systems
No signal. Still works.
No Signal is a team of specialists who build software for unmanned aircraft, so your platform keeps flying where the signal drops. Mission planning on the ground, autonomy and target recognition on board: built for your airframe, tested in real conditions and handed over with the code.
01What we build
Software for the whole mission, from the planning table to the airframe.
01 · Mission planning
Checked before every launch
One system to plan a mission, fly it and review it afterwards. We adapt what we have already built to your platform, extend the software your operators run today, or write it from scratch. What we have built into it so far:
- Weather at every waypoint, forecast for the time the aircraft will actually be there: wind, gusts, visibility, cloud.
- Range and fuel from the airframe's own figures and the forecast wind, with the point of no return and the reserve drawn on the map.
- Terrain check along the route and on the landing approach.
- One pre-flight checklist, grouped by take-off, route and landing: airframe settings, launch conditions, weather, fuel, terrain.
- Several aircraft in one session, with planned and actual arrival times updated in flight.
- Roles and access: who plans, who flies, who only watches. Licences per operator, station and airframe, issued and revoked centrally.
- Every flight recorded: position, telemetry and video. Replay the mission and compare the plan with what happened, months later if needed.
- On your servers or fully offline, on the operating system you use, with encrypted local data.
02 · Autonomous flight
Flight that holds when the link weakens
An onboard module we build around your existing flight controller, so the aircraft holds its route when satellite navigation and video fade and control goes back to the operator with one switch. What we bring to the integration:
- Works beside your existing flight controller. No autopilot replacement, no new sensors.
- Navigates on the flight controller's own signals, so it is designed to keep flying when satellite navigation and video are degraded.
- One switch hands control between operator and module, in either direction.
- Safety rules built in: altitude and tilt limits, mission timeout, soft landing on telemetry loss.
- Connects over common RC and serial interfaces, with an airframe profile tuned per platform.
- The same core runs in the simulator and on the aircraft, so behaviour is checked before a flight.
Next step
Talk to an engineer
See it hold the route on your airframe.
We start in the simulator with your flight controller and airframe profile, then move to test flights.
03 · Target recognition
Models trained for your task
Detection, classification and tracking from the onboard camera, trained for your task and sized for the compute and power budget of your aircraft.
- Object classes for your mission: aircraft, vehicles, vessels or infrastructure.
- Runs on the onboard computer you already fly, Raspberry Pi, NVIDIA Jetson or similar.
- A new class needs new training data, not new code.
- Training on your data, on your infrastructure: intake, labelling, evaluation against a metric agreed in advance, versioned deployment to the aircraft.
- The operator confirms every detection. The model proposes; a person decides.
Also in the toolbox
Work that often comes with the three areas, or on its own.
- Operator interfaces
Dashboards and control screens for people who use them under pressure, built by a frontend team with 14 years in complex live interfaces.
- Telemetry and data pipelines
Real-time ingest, storage and replay of position, telemetry and video, on your infrastructure.
- Integrations with proprietary hardware and legacy protocols
Radios, payload controllers, external detection systems and the formats your customer already uses.
- On-prem model pipelines
Training, evaluation and versioned release of models on your own GPU hardware, with no data leaving your site.
- Stack
Rust, Go, Python and TypeScript on the ground; C and Python on the aircraft; Kubernetes and bare metal underneath.
Platforms
UAV · Air01
UGV · Ground02
USV · Maritime03
02How we work
Small first step. Code you own.
Three formats
Format
Terms
Scope
01
Build for your platform
TermsFixed price
Scope
Development of one of the three areas for your airframe. Typical first project: mission planning connected to your autopilot and your platform's range and fuel figures, 6–8 weeks.
02
Extend your team
TermsYour rules, your repositories
Scope
Our engineers join your software team for a defined scope. Starts with a 2–3 week audit of your current ground or onboard software and a written plan.
03
One target class
TermsAgreed metric
Scope
A detection model trained on your data for one class of object, evaluated against a metric agreed before training.
How a project runs
- Step 01
Scope
We pick one existing platform, one mission and one acceptance test together. You name the problem owner on your side.
- Step 02
Build
Under a development contract. Progress is shown on the simulator and on test flights.
- Step 03
Test
Flight tests in Ukraine under real jamming and weather. Terms, including export requirements, are agreed for each project.
- Step 04
Hand over
The code and the rights to it are yours. We can keep supporting and extending the software afterwards.
First call
One 20-minute call is enough to say whether we can help.
Bring the platform and its flight controller, the interfaces it exposes, the mission you want it to fly, and a sample of the data you already have.
03Team
Engineers for the places where the link fails.
Overview
No Signal is a team of more than 50 engineers across computer vision, embedded systems, ground software and infrastructure. We have built secure, high-load software since 2013: trading systems, telemetry pipelines, on-prem GPU infrastructure. The same engineers now build mission software for unmanned systems.
The team holds current industry certifications in machine learning, Kubernetes and infrastructure security, renewed as they expire rather than collected.
Track record
Results from the systems this team has built and run.
Mission operations
Mission operations software for unmanned aircraft. In use with an operator running a fleet: planning, flight and debrief in one system, on the operator's own infrastructure.
Infrastructure cost
$70k → $400
Unmanaged server sprawl that peaked at about $70,000 a month was rebuilt and now runs at about $400 a month for the same performance.
Uptime
3 years
Infrastructure we tuned and still run has gone three years without an interruption and produces 15% more on the same hardware.
Scale
20 MW
Data centre programmes up to 20 MW: GPU procurement, contractors and schedule through to commissioning.
04Principles
How we work with defence customers.
01
Operator
The operator confirms every decision that matters. The software plans, flies and recognises; a person decides.
02
Confidentiality
Customer names, test results and configurations are shared under NDA only.
03
Honesty
We say what we have built and what we are building, and keep the two apart.
05FAQ
Questions we get asked first.
We make the software that runs on them. We work with manufacturers who already have a platform and need mission planning, onboard autonomy or target recognition built or adapted for it. The platform, the autopilot and the hardware stay yours.
No. Everything we do is built for your platform. We adapt what we have already built, extend the software your operators run today, or write a new piece from scratch, and hand over the code either way.
The onboard module navigates on the flight controller's own signals and is designed to hold the route when satellite navigation and video are degraded. Mission planning runs on the operator's side with no connection to our servers. Which conditions a given configuration handles is agreed and tested per project.
Fixed-wing and multirotor aircraft first. Ground and maritime platforms with a camera, an onboard computer and a link to the operator can be covered on the same terms. We connect through the platform's existing interfaces and flight controller, so no autopilot replacement is needed.
No. Mission planning runs on your servers or fully offline, and onboard modules run on the platform's own computer. Data stays on your infrastructure and is encrypted.
With one platform, one mission and one acceptance test agreed in advance. The first step is a scoped, paid piece of work: an integration, a software audit or a model for one target class. The next step follows from the results.
You do. We work under development contracts, so the code and the rights to it are yours. We can keep supporting and extending the software after handover.
Yes. We have access to test ranges in Ukraine and can arrange flight tests under real jamming and weather, with terms agreed per project.