Pre-launch · Inviting design partners
Fenhive Radar
Know where GPS can't be trusted. Before it reaches your operation.
Fenhive Radar maps GPS jamming and spoofing from the signals aircraft and ships already broadcast. Every event comes with its evidence and its uncertainty, so your team can decide what to do with it.
The problem
GPS was built for a quiet radio environment. That environment is gone.
Interference from conflict zones now spills into civil airspace and shipping lanes. Most operators find out after the fact, one report at a time.
Weak by design
Satellite signals reach the ground extremely faint. A cheap transmitter can drown them out across a wide area.
Easy to fake
The civil signal is public and unauthenticated, so a receiver can be fed a false position and report it with confidence.
Seen in pieces
Aviation, shipping and drone operators each see their own slice. There is no neutral view across all of them.
What we do
Many signals in. One picture out.
An aircraft being jammed only knows its own fix went bad. Many of them in the same place and time are a pattern. That pattern is what Fenhive reads.
Detect
Interference from public aircraft (ADS-B) and ship (AIS) broadcasts today. Our own ground sensors are planned.
Verify
Rule out benign causes first. A receiver fault is not interference, and a bad alert costs you money and trust.
Distribute
A public map and email alerts. A dashboard and an API for teams that build it into their workflow.
Archive
Every event goes into a searchable history, so you can look back at a route, a region or a date.
Who it's for
For teams that make a decision when GPS goes wrong.
Drone and BVLOS operators
Check a corridor before you fly, and keep a record you can show a regulator after an incident.
Your question: was there interference on our route, and can we show it?
Business aviation and flight ops
Know which regions are affected today, for dispatch decisions and crew briefings.
Your question: should we brief the crew or plan around it?
Maritime and insurance
See where ships report positions no ship could reach, and look back at a route's history.
Your question: how exposed is this route, and what happened on this date?
Journalists, OSINT and research
An open, citable record with the uncertainty left in, and a documented method with stated limits.
Your question: can I cite this, and how sure is it?
How we work
A wrong "GPS is down" is worse than a late "GPS might be down."
Truth over optimism
We never overstate confidence. We keep evidence separate from conclusions and always show the uncertainty.
False positives cost trust
Before a detector ships, it has to show how it rules out benign causes such as receiver faults and signal reflections.
Neutral by design
We are not aligned to any government, carrier or vendor.
Detection only
We build detection, not attack tools. When data could help cause harm, we withhold or aggregate it.
Design partners
What working with us looks like.
We're working with a small number of teams before public launch. You tell us what decision you make; we shape the product around it.
- Step 1
A short call
20 minutes on your routes, your decisions and what interference has cost you.
- Step 2
Your region
We set up the view for the corridors, routes or regions you care about.
- Step 3
Weekly review
For about 30 days, we review what it showed and what it missed, together.
- Step 4
Decide together
If it helps, we agree how you'd keep using it. If it doesn't, you've lost nothing but a few calls.
Fenhive is pre-launch. Coverage, alerts and the API are being tested with design partners, and we'll tell you plainly what the data can and can't show for your region.
Work with us.
Design partners, press and researchers. One inbox, read by a person: [email protected]