PRODUCT PORTFOLIO
Four roles.
One ecosystem.
StratoSense is not one device. Beacon, Tether and CAP have different physical interfaces and different responsibilities, and the Cloud / UTM platform is the common operational picture they all report into.
Three devices.
Three different jobs.
Beacon
EstablishedIndependent compliance detection & reporting
Observes flight activity, compares it against available flight-plan and authorization context, flags what is unexpected and reports it through implemented pathways.
Read the detailTether
In developmentController-connected authorization & flight intelligence
Sits with the remote controller. Carries authorization state, acquires telemetry, associates identity, logs operational events and uploads to the platform.
Read the detailCAP
EstablishedControlled airspace protection
Aircraft-side authorization and local airspace protection, between the RC receiver and the flight controller. Independent GNSS and IMU, local boundary evaluation, cellular reporting.
Read the detailThe chain, running.
Each hop below is a connection that actually exists in the system. Watch what moves along it, and what does not.
StratoSense / The operational chain
Simulated feedCLOUD / UTM
The common
operational picture
The StratoSense Cloud / UTM platform is where flight plans, identities, authorization state, live telemetry, events and historical records are associated into a single picture — one that a pilot, an operator and an authorized authority each see through their own role.
Established
StratoSense / System architecture
Select any nodeCAPABILITY MATRIX
The products are not
interchangeable.
Each row states what a given product does in its own right. A capability shown for one product should not be assumed for another.
| Capability | Beacon | Tether | CAP | Cloud / UTM |
|---|---|---|---|---|
| Independent detection | Yes | No | No | Yes, from available sources |
| Flight-plan context | Yes | Yes | Yes | Yes |
| Authorization context | Yes | Yes | Yes | Yes |
| Controller connection | No | Yes | No | No |
| Aircraft control-chain interface | None | Controller-side | RC receiver to flight controller | None |
| Arm blocking | No | Yes | Yes | No |
| Telemetry | Independent detection context | Yes | Aircraft-side status | Yes |
| Local airspace protection | No | No | Yes | Airspace intelligence |
| Historical records | Yes | Yes | Yes, where reported | Yes |
| Fleet operations | No | No | No | Yes |
| Authority operational view | Yes | Yes | Yes | Yes |
Beacon has no arm or control-chain interface, and therefore does not physically prevent an aircraft from arming.
Tether is not a flight-controller replacement, not an aircraft steering system, and does not autonomously fly the aircraft. It reads the operational data made available through the supported controller interface.
CAP does not fly or steer the aircraft. When it interrupts the RC path under protection conditions, the flight controller interprets the condition as normal RC loss and its existing failsafe or return-to-launch behaviour takes over.
Bring StratoSense into
your operation.
Tell us about the aircraft, the controllers and the airspace you work in, and we will tell you honestly what is available today and what is still in development.