Drone Unit · drone-side
StratoSense Cap
Mounted on the airframe. Contributes aircraft-side position and flight data to the operation.
- Location
- On the drone
- Role
- Aircraft-side data
Airspace Intelligence
Drone traffic control,
in real time.
Permission before flight. Live telemetry, verified identity and a flight record for every connected operation.
PERMISSION BEFORE FLIGHT
A flight request is evaluated against the airspace. A permission is issued through the applicable authorized pathway. The device verifies it. Only then is the aircraft flight enabled. Watch the order — the aircraft does not move until the chain completes.
StratoSense / Permission before flight
Simulated feedPermission first. Flight second.
THE QUESTION
Airspace and authorization live in one place. The aircraft, the controller and the telemetry live in another. A permission can be perfectly valid in the first while the second knows nothing about it.
The gap / authorization and flight, apart
Watch them joinWhat if authorization and flight execution were part of one operational chain?
OPERATING REALITY
Every UAS operation produces position, state, health, events, a route, a mission context, an identity and an authorization context — whatever the category it is flown in.
Operating categories / every flight creates data
BVLOS / corridor
Spray / swath
Grid / overlap
Asset / orbit
Payload / lift
Mission / tasked
The operational record of a flight should not end where the aircraft's own ecosystem ends.
THE ECOSYSTEM GAP
The drone talks to the controller. The controller talks to the pilot. And then, for most operations, it ends — in proprietary links, closed log formats and paperwork that nobody can query afterwards.
Today / where the record stops
StratoSense — a common intelligence layer beneath every flight.
How it works
The aircraft and the operator are bound to a flight, so every later record has a known origin.
A flight plan is checked and an authorization state returns before the aircraft leaves the ground.
StratoSense hardware joins the operation — on the aircraft, on the controller side, or both.
Position, altitude, link quality and authorization state stay visible while the aircraft is airborne.
The flight becomes a record that can be replayed afterwards and checked for tampering.
The units
One sits on the aircraft. One sits with the controller on the ground. They are not interchangeable.
Drone Unit · drone-side
Mounted on the airframe. Contributes aircraft-side position and flight data to the operation.
RC Unit · controller-side
Connects on the controller or ground-station side. It is not a flight controller, not an autopilot, and is never installed in the aircraft.
The Cap belongs on the aircraft. The Tether belongs on the ground. A deployment may use either, or both.
CONTEXT
This is not one system. It is a framework of stakeholders: government and the regulator setting the rules, DigitalSky carrying digital permission, service providers and operators connecting to it, UAS manufacturers building the aircraft and flight modules, remote pilots conducting the operations, and a broader UTM layer exchanging information across all of them.
India / the UAS ecosystem today
Select any layerStratoSense is not a regulator. It does not replace DGCA, it does not replace DigitalSky, and it does not issue permission. It connects the operational layers to the framework that already exists, subject to applicable regulatory requirements and authorized integration arrangements.
NPNT
NPNT is not a pilot ticking a box. DigitalSky's RPAS guidance describes it as a system-level mechanism: the aircraft must hold a valid permission artifact and verify it before it can arm. The enforcement sits with the aircraft or its control layer, not with the person holding the controller.
NPNT / no permission, no takeoff
Simulated feedAuthorization / the permission artifact
SimulatedThe artifact shown above is simulated. No real permission artifact, token, key or signature appears anywhere on this website.
PRODUCT ARCHITECTURE
Beacon, Tether and CAP have different physical interfaces and different responsibilities. The Cloud / UTM platform is the common operational picture they all report into. They are not interchangeable, and this site does not present them as though they were.
Independent compliance detection & reporting
Observes flight activity, compares it against available flight-plan and authorization context, flags what is unexpected and reports it. No arm or control-chain interface.
Read the detailController-connected authorization & flight intelligence
Sits with the remote controller. Carries authorization state, acquires telemetry through the supported interface, associates identity and uploads to the platform.
Read the detailControlled airspace protection
Aircraft-side authorization between the RC receiver and the flight controller. Independent GNSS and IMU, local boundary evaluation, cellular reporting.
Read the detailStratoSense / The operational chain
Simulated feedStratoSense / System architecture
Select any nodeSTRATOSENSE BEACON
Where a compatible aircraft control interface is unavailable, Beacon still provides a view: it observes activity, identifies what context it can, compares that against the available flight-plan and authorization context, flags what does not fit and reports it.
Beacon / detection scenario
Simulated feedBeacon has no arm or control-chain interface, and therefore does not physically prevent an aircraft from arming. It does not detect every aircraft — coverage depends on deployed devices, what the observed aircraft makes available, communications and authorized external data sources.
STRATOSENSE CAP
CAP sits between the RC receiver and the flight controller with its own GNSS, its own IMU and a local airspace map. Watch what happens when the aircraft reaches a protected volume — and note what CAP does not do.
CAP / protection scenario
Simulated feedCAP does not fly or steer the aircraft. Interrupting the RC path makes the flight controller read a normal RC loss, so the aircraft's own existing failsafe or return-to-launch behaviour takes over — the behaviour already configured on that airframe.
ONE PRINCIPLE
Permission validation belongs at the layer that can actually act on it. Tether validates at the controller, where the supported control architecture permits. CAP validates at the aircraft, through its control-chain interface. Beacon does neither — and this site says so plainly.
One principle / enforcement at the right layer
Select any pathTether — controller-side permission and authorization validation, and operational enforcement where the supported control architecture permits it.
CAP — aircraft-side permission validation and protection through its aircraft / control-chain interface.
Beacon — independent observation, detection and compliance reporting. Beacon has no arm or control-chain interface and does not prevent an aircraft from arming. Where enforcement is not available at the aircraft or control-chain layer, Beacon provides an independent compliance visibility layer instead.
StratoSense provides an architecture for permission-aware and NPNT-oriented operation across connected systems, with enforcement implemented at the appropriate control or interface layer. No StratoSense product is claimed here as a certified or registered flight module.
Ecosystem
StratoSense brings the aircraft, the people operating it, the platform and the wider airspace ecosystem into a single operational picture.
Aircraft, ground and platform in one picture.
Flights bound to a known aircraft and operator.
Live status while the aircraft is airborne.
A durable record you can go back to.
TELEMETRY INTELLIGENCE
Four stages turn bytes on an interface into something that can be read, compared against a plan and audited a year later.
Telemetry / pipeline
Select any stageBytes on an interface, in the shape the source emits them.
Framing and fields resolved against the source protocol.
A common schema, a common time base and a device identity.
State, history, events and compliance context.
Telemetry / packet to dashboard
Simulated feedFrom aircraft to airspace
A single reading leaves the aircraft and ends up somewhere an operator and an authority can both act on it.
Illustrative values
Live airspace
A simulated operation running entirely in your browser. Nothing here is connected to a live aircraft.
ADVISORY — ZONE B BOUNDARY
Simulated · deterministic · no backend
Platform
Every flight in the operation, in the same place, with the same vocabulary — from the moment telemetry arrives to the moment the record is archived.
Authenticated telemetry arrives from the aircraft and controller side.
One current view of who is flying, where, and at what altitude.
Zone proximity and link conditions surface as advisories, not alarms.
Step back through any flight, second by second, after it has landed.
Records are retained and chained so later modification is detectable.
| Flight | Altitude | Status | State |
|---|---|---|---|
| SS-2291 | 118 m | AUTHORIZED | ACTIVE |
| SS-3384 | 95 m | AUTHORIZED | ACTIVE |
| SS-4410 | 62 m | AUTHORIZED | RECORDED |
| SS-5552 | 80 m | ADVISORY | ACTIVE |
Altitude · SS-2291
Illustrative interface · demonstration data
The flight record
Scrub the timeline. The map, the altitude and the event all move together.
Simulated · deterministic
Two points of view
Fly with confidence.
Know the flight is permitted before it leaves the ground.
Position, altitude and link quality while airborne.
A replayable record of what actually happened.
See the bigger picture.
Active flights and zones in one view.
Authorization state alongside each operation.
Records and events available after the fact.
THE DIFFERENCE
Authorization, flight control, telemetry, fleet and compliance each work. They simply do not reach each other. That is an architectural gap, not a failure of any one system.
Before / after
Toggle the viewCLOUD / UTM
Connected operations and independent detections arrive at the same platform. Pilots, operators and authorities are each served from the same underlying record, through their own role.
Cloud / many operations, one picture
Simulated feedWHO IT IS FOR
Flight-planning context, airspace awareness, authorization state, live telemetry, operational status, alerts and historical flight records.
Read moreFleet and operational visibility, telemetry, authorization context, alerts, flight history and audit records across the whole fleet.
Read moreAn operational view built from connected and authorized sources, flight-plan and authorization context, detected activity, historical investigation and audit information.
Read moreIncident review
Select an event to jump the replay to that moment.
Simulated demonstration
System architecture
Select any part to see what it connects to. High-level only — no implementation detail.
Select a node to see its role and what it connects to.
THE STRATOSENSE DIFFERENCE
Not a telemetry device. Not another drone tracker. Not another authorization application. The connection between those layers — carrying one flight identity from the moment it is created to the moment somebody audits it.
One flight / ten stages, one identity
Simulated feedTWO DIFFERENT QUESTIONS
These are not the same record, and neither one alone proves anything. Compliance is what happens when you can put them side by side.
Permission / versus telemetry
Simulated feedWhat are you allowed to do?
What are you actually doing?
FULL FLIGHT LIFECYCLE
Authenticate, plan, evaluate the airspace, obtain the applicable authorization, validate the device, fly, carry the telemetry and events, close the flight, retain the record, answer the query.
THE WHOLE PLATFORM
Position, state, health, events, a route, a mission context, an identity and an authorization context — produced by every operation, in every category.
Proprietary links, closed log formats, no shared identity and paperwork nobody can query. The chain stops before the airspace.
Aircraft, controller, Tether, cloud, airspace — plus CAP on the airframe and Beacon observing independently, each on the interface it actually has.
Raw packets are decoded, normalised to one schema and time base, and attributed to a device before anything reads them.
A plan is evaluated against authoritative airspace data, authorization is carried from the applicable authorized pathway, and the device validates it for that specific flight.
Airspace awareness before the flight, live state during it, and a record that can be returned to afterwards.
Every aircraft, every live and scheduled flight, every flagged event, with the authorization context attached to each.
Built from connected devices and authorized data sources — and honest about the fact that this is not every drone in the sky.
Plan versus actual, telemetry, events, device events and communication events, retained and protected so it reads later as it was written.
From the moment a pilot signs in to the moment an authorized auditor asks what happened.
Built for trust
Hardware participating in an operation is identified, so data has a known source.
Messages between devices and the platform are authenticated in transit.
Operators and authorities see what their role permits — not everything.
Records are chained so later modification is detectable on verification.
Each flight resolves to a durable record that can be replayed.
Events carry timestamps and origin, so a sequence can be reconstructed.
Described at a product level. StratoSense does not publish its security implementation.
Integration
Drone operations rarely run one make of aircraft or one controller. StratoSense is designed to work across heterogeneous equipment.
Interface concepts under development. Listing an interface is not a claim of certified or production support for a given airframe or controller.
AIRSPACE · PERMISSION · NPNT · TELEMETRY · COMPLIANCE
StratoSense / five questions, one chain
Simulated feedWhere can I fly?
Can I fly?
May I arm?
What am I doing?
Did I follow the plan?
WHY THIS MATTERS
The aircraft knows whether the required permission and authorization state is valid before the relevant operation proceeds.
The operational system knows what the connected aircraft is actually doing, while it is doing it.
Identity, authorization, telemetry and events can be associated with a single flight record.
The operation can be evaluated against applicable airspace information and restrictions.
THE FAIR QUESTION
Because the problem is not a shortage of systems. Identity, authorization, airspace, telemetry, control, compliance and history already exist — they simply exist across different technical layers, built at different times for different purposes.
So why not connect them?
StratoSense does not replace the ecosystem. It connects the operational layers.
PRODUCT STATUS
Engineering concepts are not presented here as released features. This is where each part of the ecosystem actually stands.
Portfolio / maturity
Interoperability
Digital Sky is where Indian drone registration and permission live. StratoSense is designed to sit alongside it, adding the live picture and the flight record that a registration alone does not provide.
Who should be flying.
A known operator, bound to a known airframe.
A plan that was granted before the flight.
What actually happened.
Position, altitude and link, while the aircraft is airborne.
The track compared against the permission that was granted.
StratoSense is an independent product. Nothing on this page represents an endorsement, approval, certification or partnership. digitalsky.dgca.gov.in is linked for reference only.
Airspace intelligence for the people who fly, and the people who oversee the flying.
THE WHOLE LIFECYCLE
Connect the authorization, the aircraft, the telemetry, the airspace and the operational record into one continuous flight lifecycle.
From permission / to proof
Simulated feedNo permission.
No takeoff.
StratoSense — the digital operational layer between drones and the airspace.
Telemetry · Authorization · Compliance · Connectivity