Resources
Frequently asked questions
Common questions from operations, safety and IT teams about coverage, devices and how SatSentinel delivers events over satellite.
Coverage & networks
Where SatSentinel works and which networks it uses.
Which satellite networks does SatSentinel use?
SatSentinel operates over Iridium, Thuraya and other approved networks. Future LEO pathways form part of the roadmap. The network used for a specific deployment is selected during scoping.
Do we still need cellular coverage?
No. The platform is designed for locations where GSM and fibre are unavailable or unreliable. Where cellular is available, supported devices and mobile apps can use it, with satellite carrying events when it is not.
Is coverage guaranteed everywhere?
Coverage depends on the chosen network, the device and the operating environment — terrain, structures and vehicle installation all matter. Coverage for a specific operating area is confirmed with Fluxcon before deployment.
What happens during a satellite outage?
Where the device supports it, events buffer on the device and are delivered once a link becomes available. Device and service health, including delivery latency, is visible in the platform.
Does SatSentinel provide the emergency response?
No. SatSentinel routes alerts to the control rooms, security providers, emergency contacts or response partners you nominate. Response services are provided by those parties.
Can we keep our current security company?
Yes. Alarm and safety events are delivered over satellite to the security company or control room you already use, or to another nominated responder.
Which countries and regions are supported?
Availability follows the chosen satellite network and applicable regulatory approvals. Fluxcon confirms supported regions for your operation during scoping.
Devices & compatibility
Supported hardware, alarm panels, vehicles and mobile applications.
Which satellite devices are supported for Personnel?
Personnel operates with supported satellite-capable devices and services, including TYTO and Thuraya One, together with paired mobile applications. Specific device compatibility is confirmed with Fluxcon.
Which alarm panels work with SatSentinel Alarm?
The alarm hub supports common panel outputs and contact-style inputs, covering intrusion, panic, power failure, compatible fire inputs and environmental sensors. Panel compatibility is confirmed during scoping.
What is installed in a vehicle for ACN?
ACN uses in-vehicle hardware that detects crash, rollover and G-force events, captures GNSS position and transmits over satellite. A dual-antenna architecture is used to improve event-delivery survivability after a severe incident.
Can ACN replace our telematics platform?
No, and it is not intended to. ACN focuses on satellite-delivered incident notification and integrates with fleet and telematics platforms via APIs.
Are there mobile applications?
Yes. Field teams use mobile applications for SOS, check-ins, messaging and job workflows, while supervisors and operations use the web portal.
Can we monitor device health?
Yes. Battery, signal, delivery latency and service health are reported at device and site level.
What about the roadmap devices?
Beacon, Fire Monitoring, Energiser Monitoring, Weather Station, Fuel Monitoring and Fuel Audit are future releases subject to technical validation, field trials and commercial approval. No release dates are published.
Data, delivery & latency
How events are transported, how quickly they arrive and how records are retained.
How quickly are alerts delivered?
Delivery is near-real-time and event-driven. Actual latency depends on the satellite network, device, site conditions and the configured reporting profile, so no fixed delivery time is guaranteed.
Why is the platform event-based rather than continuous?
Satellite links are not broadband. Event-led workflows, payload optimisation and message compression keep critical information moving while controlling data usage and operating cost.
Can we see how long delivery actually took?
Yes. Delivery-latency reporting is available per device and per event, alongside device and system health views.
How often do devices report position?
Reporting uses scheduled updates and threshold-based rules, configured per deployment to balance operational visibility against satellite data cost.
What happens to events raised while a device is out of contact?
Where the device supports store-and-forward, events are buffered and delivered once a link is available.
How are false alarms handled?
Events are validated before transmission where applicable, and cloud rules apply classification, filtering and escalation so that nuisance activations do not overwhelm responders.
What record is kept?
SatSentinel maintains an immutable event history and an operator audit trail covering acknowledgements and actions, available for compliance and post-incident review.
Who can see our data?
Access follows the users, teams and response partners you configure. Data handling and retention terms are agreed with Fluxcon as part of your service arrangement.
Answers reflect current product behaviour. Roadmap items are labelled as future releases and have no published release dates. Specifications, coverage, device compatibility and integration options are confirmed during scoping. Talk to Fluxcon.