RAPTOR-OPERATED CONNECTIVITY
Beyond line of sight. Beyond one mesh.
We are developing our own Raptor-operated backhaul service to connect geographically separated nodes and networks.
In developmentOur own service layer
The planned Raptor service provides a managed VPN/backhaul layer for participating nodes. The direction is to offer hardware with an optional connectivity service; pricing, availability and service commitments are not yet announced.
The connection underneath
An available fibre, cellular or broadband satellite connection would carry traffic to the service. Raptor operating the backhaul does not mean Raptor owns those third-party carrier networks.
A gateway between locations
A local gateway is intended to carry supported traffic between a field mesh and remote networks. Routing, access control, provisioning, reconnection and monitoring are implementation and validation priorities.
Local operation still matters
The design keeps local mesh communication independent of external connectivity. Remote voice and data depend on the available uplink; this is not a promise of uninterrupted or universal coverage.
Satellite messaging research
RockBLOCK 9704 is being investigated as a separate satellite messaging option. It is not a broadband voice/video backhaul. The manufacturer describes message-based IoT connectivity, including messages up to 100 KB.
What comes next
Establish repeatable node onboarding, verify isolation and access controls, test realistic loss and reconnection scenarios, and validate supported traffic before offering a production service.
CUSTOMER OPERATIONS
Manage BLOS service in one place.
Technology reference: Ground Control — RockBLOCK 9704
THE COMPLETE PICTURE