Government and defence engagement
PNTMAP™ is operated as a UK-sovereign source of evidence about GNSS interference affecting aviation. This page states precisely what the operator is, what the platform does today, and what is planned.
PNTMAP is an intelligence and situational-awareness service. It is not an authorised navigation source and must not be used as the sole basis for flight planning, navigation or aviation safety decisions.
Operator and entity scope
PNTMAP™ is operated by Decent Cybersecurity Ltd, a company registered in England and Wales (company number 15364616), London. Group credentials belong to the entities that hold them and are not transferred to the platform: Decent Cybersecurity s.r.o., a Decent Cybersecurity group company, was selected for NATO DIANA's 2026 Decision Superiority for NATO Warfighters Challenge. That selection belongs to s.r.o.; it is not a NATO endorsement of PNTMAP™ and is not held by Decent Cybersecurity Ltd. Personnel security clearances are held by named individuals, not by the platform. Full detail is on the sovereign page.
UK data flow and hosting
Nodes are UK-sited and owned by the operator. Telemetry is authenticated per node with server-side validated keys, ingested over TLS, and stored in UK/EU-hosted managed infrastructure. There is no dependency on third-party or community-sourced aggregated ADS-B feeds for the evidence record.
Deployment options
Three routes are supported architecturally: participation in the public national network; dedicated nodes at customer-nominated sites reporting into a customer-scoped view; and a wholly separate instance under customer control. Availability and terms per route: [DECISION NEEDED].
Classification handling
The public platform processes only publicly broadcast ADS-B telemetry and operator-owned sensor measurements, and is operated at OFFICIAL. It does not currently hold, process or store classified material, and no capability on this site should be read as accredited for classified handling. Requirements above OFFICIAL are handled as a separate engagement: [DECISION NEEDED].
Evidence-chain architecture
Records are designed as an append-only, tamper-evident evidence log, with post-quantum (ML-DSA-65) node signing live and verified at ingest on all UK nodes, and external anchoring not yet implemented. The trust model, planned record format and current honest status are published on Verify Evidence.
Custom reporting and sensor options
Bespoke reporting periods, region-scoped analysis, retrospective incident reconstruction within the retained record, and additional RF sensing payloads at nominated sites can be scoped. RF L1/L5 monitoring is planned network-wide and is not live on any node today.
Engagement route and procurement
Named engagement contact: [DECISION NEEDED]. Procurement identifiers (framework listings, DUNS, supplier registrations): [DECISION NEEDED]. Until those are published, use the contact route and state the requirement.