Keep watch
Small receivers continuously report satellite messages, signal reception and receiver health to the collector.
Ground Monitoring for Space Integrity.
On-site GPS monitoring with a network of receivers.
Install small GNSS monitoring receivers around your facility or across multiple locations. Each probe stays on watch and reports to a central collector. The collector compares satellite messages and local reception, helping your operators distinguish a local GPS problem from a wider satellite or signal event. We supply the hardware and software, installation assistance and continuing support.
Independent GNSS situational awareness for your facility.
Receivers → collector → operators
On-site receiver probesAuthenticated identity
Small receivers at the locations you need to monitor
- Probe 01On watch
- Probe 02On watch
- Probe 03On watch
Customer infrastructure
Central collectorCompare observations · record events
Your operatorsWarnings, receiver health and event history
Multiple receivers. One collector. Continuous monitoring.
01 / A network standing on watch
What’s local? What’s happening across the network?
Each probe observes the satellites it can see and the reception conditions at its own antenna. The central collector brings those reports together, so your team can investigate a problem at one location alongside satellite, clock and signal-health changes seen by other receivers.
Compare probes
Check whether a reception change is confined to one location or also appears in observations from other receivers.
Check the satellites
Examine orbit, clock and broadcast-health changes alongside the reception conditions reported on the ground.
Warn and investigate
Report configured events to your operators and retain the observations they need to investigate what happened.
Coverage follows your probe locations and supported signals. A missing receiver report is a monitoring gap, not evidence that conditions are healthy.
02 / Private and sovereign deployment
Sensors on your premises. Data in your infrastructure.
A sovereign GNSS monitoring network your team can inspect, operate and own. Place receiver probes around one facility or across multiple locations, all reporting to a central collector in your infrastructure. Your operators review reception, satellite events, receiver health and warnings together. We help install, configure and maintain the system.
A network you control
Inspect the hardware and software, operate the collector on your network and retain your operational data. For a sovereign deployment, you own the trust hierarchy and signing authority.
Receivers where you need them
Choose the probe count and antenna placement around your facilities and the systems you depend on. Add monitoring locations as your requirements grow; comparisons follow the measurements each receiver supports.
Support beyond installation
Provisioning, receiver configuration, software updates, alert review and incident interpretation are part of the continuing engineering and support we agree with your team.
Sovereign deployment boundary
- Observe continuouslyAuthenticated probes across your locations
- Compare centrallyA collector in your infrastructure
- Report and investigateLocal and satellite events, history and warnings
Optional public-network exchangeSeparately agreed by the customer
03 / Local and satellite-wide events
Investigate local problems and wider GNSS events.
If one probe loses signal strength or satellite tracking, compare the same signals at other locations. Are those receivers still receiving normally? Has the satellite’s broadcast health, orbit or clock changed too? The central collector brings these observations together to help your team distinguish local reception trouble from a wider satellite or signal event.
- Compare observations of the same satellites and signals across receiver probes.
- Review orbit, clock and broadcast-health changes alongside signal strength, tracking and receiver-reported interference indicators.
- Identify which locations report a change, which do not and where observations are missing.
- Keep the measurements behind warnings available for operational investigation and incident review.
Comparisons help investigate local and wider events; they do not guarantee interference or spoofing detection. Available indicators depend on the receiver configuration and conditions tested.
Investigation checklist
Evidence behind a network event
- Probes
- Reporting locations and authenticated receiver identities
- Configuration
- Receiver, firmware and signals monitored at each location
- Time
- Observation period and time source
- Change
- Reception, satellite messages, orbit, clock or broadcast health
- Condition
- Warning condition and supporting measurements
- Compare
- Other probes observing the same satellite or signal
- History
- Reception and event records, with known observation gaps
Monitoring where GNSS matters
Independent observations for your operations.
Airport facilities
Deploy GNSS interference-monitoring probes around your airport facilities. Give ground-system teams an independent view of GPS reception, local anomalies and satellite events.
Timing infrastructure
Keep watch around the receivers that supply precision time. Compare reception changes with satellite clock and broadcast-health events.
Ports & maritime facilities
Place probes around operational locations to record reception conditions and compare navigation problems with observations elsewhere in the network.
Flight test & autonomous systems
Maintain an independent observation network alongside your operational equipment, with reception history and event evidence for test and incident review.
04 / Deployment and continuing support
A monitoring network. Built to keep watching.
We supply and support a working monitoring network, not a three-month study. Your receivers keep reporting to a central collector, your operators follow local reception and satellite events, and we continue supporting the hardware and software. Start with the coverage you need and add probes as your requirements grow.
Installation and commissioning
Deploy your receivers
Place and configure small GNSS probes around your facility or across the locations that matter to you.
- Antenna and receiver placement
- Authenticated sensor provisioning
- Central collector setup and handover
Continuous operation
Keep the network on watch
Probes report throughout operation. The collector compares observations, records events and warns your operators.
- Local and satellite-wide event comparisons
- Receiver health and reception history
- Operator warnings and integrations
Continuing support
Maintain and expand
Installation is the beginning. We support the receivers, collector and monitoring workflow as your network and requirements change.
- Receiver configuration and software updates
- Alert review and incident interpretation
- Ongoing engineering and support
A pilot can be the first step into ongoing monitoring, not the product or an automatic end date. Your agreement defines probe count, supported indicators, retention, integrations, operating responsibilities and continuing support.
Before we talk
A few practical questions.
An operating network, with deployment and support built around your facilities.
Discuss your networkAre we buying a report or an operating monitoring system?
An operating GNSS monitoring network: small receiver probes, central collector software, observation history and event reporting, with installation assistance and continuing support. Reports help explain incidents; they are not a substitute for the receivers keeping watch.
How many receivers can we deploy?
We plan the number of receivers and collector capacity around your locations, coverage and supported signals. Start with the locations you need to watch and add probes as your monitoring needs grow.
How does Integrity Satellite relate to NavListen?
NavListen is the hardware, software and monitoring-network foundation we already operate. Integrity Satellite supplies supported customer deployments, provisioning, configuration and continuing engineering.
Can we inspect, operate and own our network?
Yes. The hardware and software are open for inspection, and your team can operate the receiver network and collector in your own infrastructure. We provide the agreed configuration, documentation, handover and continuing support. A sovereign deployment gives you ownership of the trust hierarchy and signing authority.
Who controls the sovereign trust hierarchy?
The customer owns the sovereign deployment’s trust hierarchy and signing authority. Public-network participation uses a separate arrangement.
Must we contribute observations to the public network?
Public-network contribution is a separate customer decision. The scope defines what data stays in the customer environment and any agreed exchange.
Does the system prevent GNSS interference?
The monitoring service observes and records conditions for investigation and alerting. Mitigation and the response of connected operational systems are separate requirements.
What does a spoofing indicator mean?
It is an observation or pattern evaluated against a defined condition. We state the supporting evidence, uncertainty and tested scope; an indicator is not a universal guarantee of spoofing detection.
Is a phone required?
The iPhone app is one way to demonstrate and inspect the public system. The enterprise scope defines the local operational interface and alert recipients. Local alerts and phone push notifications are different delivery paths.
Does monitoring end after three months?
The offer is ongoing monitoring, not a three-month report. A pilot is an optional way to establish the receiver layout, baseline and operational fit before continuing into production. We agree how the network will be operated and supported beyond that initial stage.
Let’s put your receivers on watch
Plan your monitoring network.
Tell us which facilities and GPS-dependent systems need an independent watch. We’ll work through probe placement, the central collector, operator warnings and the continuing support that keeps the network useful to your team.
Talk with Patrick TudorDeployment and continuing engineering support
Prefer a direct email?
patrick.tudor@intsat.space
Discuss your monitoring network
A few details help us plan your receivers, collector and ongoing support.
Email Patrick with your name, organization, facility locations, and the GPS-dependent systems your receiver network will monitor.
patrick.tudor@intsat.space