Live GPS-integrity evidence for drones, aviation & maritime.
An independent, signed indicator of probable GPS/GNSS interference over an area, measured from live aircraft navigation-quality (the GPSJam method) and delivered as one keyless MCP + REST call. Each reading is Ed25519-signed over its exact bytes, provenance-stamped, and written to an append-only signed archive, so a disrupted nav fix becomes a record you can put in front of a regulator, an insurer, or a safety case, not just an app screenshot. Evidence, not a safety guarantee, your stack and operator own the go decision.
A jammed fix is real, but it isn't evidence.
GNSS jamming and spoofing are rising across conflict edges, busy ports, and contested airspace, and they reach civilian drones, aircraft, and vessels operating nearby. When it happens, the operator sees a degraded or wandering position, but a screenshot of an app isn't evidence. It doesn't stand up in a CASA finding, it won't substantiate an insurance claim, and it's not enough to defend a BVLOS safety case after the fact.
What holds up is an independent record, a reading from a third-party source, signed and timestamped at the moment it existed, that anyone can re-check without trusting your word or ours. That's what this vertical provides: a live, region-level GPS-integrity indicator, captured as a tamper-evident, provenance-stamped record.
A signed GPS-integrity reading anyone can check.
A live indicator, delivered the same way every datapoint we publish is, signed, sourced, and archived.
- Live GPS-integrity readings by region. Our
gps_interferencetool returns the share of sampled aircraft showing degraded GPS navigation over an area, the GPSJam method, derived from live ADS-B navigation-integrity indicators (NIC / NACp). Region presets or any lat / lon. - A signed go / caution / no-go awareness verdict. Our
/v1/awarenessendpoint returns a per-class (ground / aerial / marine / orbital / humanoid) signed verdict for a launch point, with the grounded facts behind it. It never hangs, on a hard deadline it floors to caution, never go. - Per-datapoint provenance. Every reading carries its source, the source URL, and the exact measurement timestamp, the origin of each number is explicit.
- Ed25519 signatures over canonical bytes. Each datapoint is signed so any later edit is detectable, tamper-evidence by construction.
- An append-only signed archive. Readings are captured as they happen, so the record can't be backfilled or quietly rewritten after an incident.
- Verify it yourself. Drop a bundle on the in-browser verifier, or use the open Python / JS / Rust verifiers, anyone re-checks a record independently, in their own code, without trusting us.
The record a machine acts on is the record an insurer adjudicates.
Each reading is issued as a self-contained evidence bundle built on one identity, a single content hash carried through two phases:
- Live, on-device, microseconds. A drone, vessel, or agent checks the Ed25519 signature + freshness before it acts, no network. Authentic and current, so a stale "GPS was clean an hour ago" reading can't be replayed at it.
- Evidence, offline, verifiable. The same content hash is committed to an append-only transparency log and time-stamped by an independent RFC 3161 authority, instantly. An adjuster proves, after the fact, that this exact observation existed at that time, witnessed by an independent authority neither party controls.
- Verify four ways, trusting no one. The bundle checks out in a browser, a CLI, and independent Python, JavaScript, and Rust verifiers, against the bundle's own embedded key, with zero calls back to us. It still verifies even if Dynamic Feed no longer exists.
- Append-only, time-stamped. Each reading is written to an append-only archive and time-stamped by an RFC 3161 authority, so any change after it was time-stamped is detectable, tamper-evident in a way a bare signature alone isn't.
Right now, over a monitored region.
This is a live gps_interference reading, fetched in your browser from POST /v1/batch. degraded_fraction is the share of sampled aircraft below GPS-grade navigation over the area, a high share is the probable interference signal. Pick a region to re-fetch.
14.6%
Of 130 aircraft sampled in the region, 19 showed degraded GPS navigation, severity low. Derived by Dynamic Feed from live ADS-B (adsb.lol, open data), the GPSJam method.
The reading is a derived indicator, not a direct measurement of a jammer. A high degraded fraction over a region is consistent with GPS/GNSS interference; a low sample (few aircraft overhead) means lower confidence. It is evidence, not a safety guarantee, your stack and operator own the go decision.
Teams who need a record that holds up.
Substantiate a safety case
Capture an independent GPS-integrity record per launch point and per flight, so a degraded fix is documented evidence in your BVLOS or operational safety case, not a memory.
Document the airspace
A signed, timestamped indicator of GNSS conditions over a region, archived as it happened, useful when reconstructing what the navigation environment looked like.
An independent claims input
When a loss involves GPS disruption, an independent third-party reading signed at the time gives adjusters a record neither party controls, evidence, not a self-report.
Ground the go decision
Query a per-class signed awareness verdict for a launch point and log the signed indicator your system acted on, auditable after the fact.
One call → a signed record.
Call the feed
One keyless MCP or REST call: gps_interference with a region preset or lat / lon. No key to get started.
Or ask for a verdict
POST /v1/awareness with a class and location returns a signed go / caution / no-go verdict plus the facts behind it for that launch point.
Keep the signed record
Every response is Ed25519-signed and provenance-stamped, and written to the append-only archive, so you can produce it later.
Verify it independently
Drop the bundle on the in-browser verifier, or use the open Python / JS / Rust verifiers, to re-check the signature, log inclusion and RFC 3161 timestamp yourself. No need to trust us.
One price, the whole platform.
GPS integrity is part of Dynamic Feed, not a separate bill. Start free and keyless; paid tiers (Builder, Scale, Enterprise) are in early access — request access and tell us your workload. The same signed, sourced, archived records on every tier.
Every tier is self-serve, even Enterprise. Mint a key and you are live in seconds, no sales call and no waiting. Need GPS integrity alongside AIS, weather and tides at sea? See the maritime vertical. Want the whole verifiable-data layer, or your own source wrapped the same way? See done-for-you.
An indicator, not a certification.
GPS-integrity here is a derived signal computed from third-party ADS-B, aircraft navigation-quality indicators, not a direct sensor reading of a jammer. It is not a guarantee of the presence or absence of jamming, and not a safety certification. Signing and RFC 3161 timestamping prove that a datapoint existed, unchanged, at a specific time, they do not prove it is true or accurate; we make no accuracy guarantees about the upstream source. This is an independent, signed indicator, evidence, not a safety guarantee; your stack and operator own the go decision.
Fully automated. Run by AI, end to end.
No sales calls and no waiting. Mint a key and you are live in seconds, on any tier, with signed GPS-integrity readings.