StratoSense000
STRATOSENSE Request platform access

Airspace Intelligence

Stratosense

Drone traffic control,
in real time.

Permission before flight. Live telemetry, verified identity and a flight record for every connected operation.

  • TelemetryLive position & altitude
  • IdentityAircraft & operator bound
  • AuthorizationPermission before flight
  • RecordsReplayable afterwards
Know•Monitor•Protect•The Skies

PERMISSION BEFORE FLIGHT

The aircraft waits
for permission.

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 feed
launch point WAITING FOR AUTHORIZATION
Flight request
Airspace check
Permission
Device verification
NPNT check
Flight enabled
—
Simulated · NPNT-oriented architecture, not a certification claim

Permission first. Flight second.

THE QUESTION

Why do we need
two different systems?

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 join
System A · airspace and authorization Flight plan Airspace Permission Authorization System B · aircraft and operation Aircraft Controller Telemetry Flight control GAP StratoSense the operational connection
—
Architectural fragmentation · not a claim that any existing system is broken or non-compliant

What if authorization and flight execution were part of one operational chain?

OPERATING REALITY

Every flight
creates data.

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

Enterprise

BVLOS / corridor

Agriculture

Spray / swath

Mapping

Grid / overlap

Inspection

Asset / orbit

Industrial

Payload / lift

Specialised

Mission / tasked

Illustrative operation geometries

The operational record of a flight should not end where the aircraft's own ecosystem ends.

THE ECOSYSTEM GAP

The chain stops
before the airspace.

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

DRONE CONTROLLER PILOT no shared link AIRSPACE / UTM
Proprietary linksClosed log formatsNo shared identityManual paperworkNo unified live pictureSiloed fleet dataDifficult historical verification

StratoSense — a common intelligence layer beneath every flight.

How it works

Five things happen
around every flight.

  1. 01

    Identify

    The aircraft and the operator are bound to a flight, so every later record has a known origin.

  2. 02

    Authorize

    A flight plan is checked and an authorization state returns before the aircraft leaves the ground.

  3. 03

    Connect

    StratoSense hardware joins the operation — on the aircraft, on the controller side, or both.

  4. 04

    Monitor

    Position, altitude, link quality and authorization state stay visible while the aircraft is airborne.

  5. 05

    Record

    The flight becomes a record that can be replayed afterwards and checked for tampering.

The units

Two units. Two places.

One sits on the aircraft. One sits with the controller on the ground. They are not interchangeable.

Drone Unit · drone-side

StratoSense Cap

GNSS MOUNT

Mounted on the airframe. Contributes aircraft-side position and flight data to the operation.

Location
On the drone
Role
Aircraft-side data

RC Unit · controller-side

StratoSense Tether

INTERFACE PORT TO CONTROLLER

Connects on the controller or ground-station side. It is not a flight controller, not an autopilot, and is never installed in the aircraft.

Location
With the controller
Role
Telemetry & authorization

The Cap belongs on the aircraft. The Tether belongs on the ground. A deployment may use either, or both.

CONTEXT

India's drone
ecosystem today.

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 layer
Government DGCA the aviation regulator Rules / regulation applicable requirements DigitalSky digital permission platform Service providers DigitalSky Service Providers Operators and UAS manufacturers Other stakeholders UTM participants Permissions permission artifacts Flights planned operations UAS / RPAS incl. flight module where applicable Remote pilot UTM traffic management and data exchange across stakeholders
—
StratoSense is not a regulator and does not replace DGCA or DigitalSky

StratoSense 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

No permission.
No takeoff.

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 feed
Permission applicable authorized pathway Signed artifact bound to flight, aircraft, area, window Device verify on the aircraft or control layer Valid arm enabled Invalid arm blocked
—
NPNT is an aircraft / system-level enforcement concept

Authorization / the permission artifact

Simulated
StratoSense flight authorization UNVERIFIED
Flight ID
SS-2291
Aircraft
UAS-014
Operator
OP-042
Area
Operation Zone A
Altitude
Authorized band
Time window
14:30 – 15:00
Status
—
Signature
—
Received
Verified
Matched
Device authorized
—
Simulated authorization data · no real permission artifact, token or signature is published here

The artifact shown above is simulated. No real permission artifact, token, key or signature appears anywhere on this website.

PRODUCT ARCHITECTURE

Not one device.
An ecosystem.

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.

StratoSense / The operational chain

Simulated feed
Airspace / UTM authoritative airspace data Authorization applicable authorized pathway StratoSense Cloud the common operational picture Pilot this flight Operator this fleet Authority connected + authorized StratoSense Tether controller-connected Remote controller Aircraft CAP aircraft-side protection Beacon independent detection reports reports
—
Simulated packet flow · Beacon observes independently and has no control-chain interface

StratoSense / System architecture

Select any node
AIRSPACE / UTM Authorization context STRATOSENSE CLOUD Common operational picture STRATOSENSE TETHER Controller-connected CONTROLLER Ground station AIRCRAFT Unmanned aircraft BEACON Independent detection CAP Aircraft-side protection
Architecture overview · implementation detail intentionally not published

STRATOSENSE BEACON

Independent
compliance visibility.

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 feed
Monitored area Beacon observing
Observe
Identify
Compare
Flag
Report
—
Beacon reports · it does not prevent arming

Beacon 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.

Read the Beacon detail

STRATOSENSE CAP

Aircraft-side
airspace protection.

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 feed
Authorized volume Protected volume
Remote control RC receiver CAP GNSS · IMU · local map Flight controller its own failsafe / RTL
—
CAP does not fly or steer the aircraft

CAP 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.

Read the CAP detail

ONE PRINCIPLE

One NPNT principle.
Several StratoSense systems.

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 path
Authorization applicable authorized pathway StratoSense Cloud Tether controller-side validation CAP aircraft-side validation Beacon observation only Controller Aircraft control chain Flight enabled reports — no control path
—
Enforcement is implemented at the appropriate connected aircraft or control interface, subject to applicable regulatory requirements and authorized integration arrangements

Tether — 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

One connected
airspace network.

StratoSense brings the aircraft, the people operating it, the platform and the wider airspace ecosystem into a single operational picture.

STRATOSENSE Airspace intelligence DRONEwith Cap CONTROLLERwith Tether CLOUDSecure ingest PLATFORMOne view OPERATORS AUTHORITIES UTMAirspace RECORDSReplayable
  • Connected

    Aircraft, ground and platform in one picture.

  • Verified

    Flights bound to a known aircraft and operator.

  • Visible

    Live status while the aircraft is airborne.

  • Recorded

    A durable record you can go back to.

TELEMETRY INTELLIGENCE

Raw packets become
a flight record.

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 stage
01

Raw packets

Bytes on an interface, in the shape the source emits them.

02

Decode

Framing and fields resolved against the source protocol.

03

Normalise

A common schema, a common time base and a device identity.

04

Flight intelligence

State, history, events and compliance context.

Architecture overview · decoder implementation is not published

Telemetry / packet to dashboard

Simulated feed
Raw Decode Normalise Time align Identity Intelligence bytes on an interface a readable flight record
Altitude
—m AGL
Ground speed
—m/s
Heading
—deg
Battery
—%
GNSS
—
—
The dashboard updates only after normalisation · simulated values

AUTHORIZATION ENGINE

From a plan to
permission to operate.

The authorization state is not a label an operator sets. It is carried from the applicable authorized pathway, bound to the specific flight, validated on the device, and recorded.

Authorization / state machine

Select any stage

Flight plan

Who, what, when, where, purpose and parameters are defined.

Plan

Airspace evaluation

Evaluated against applicable rules and authoritative airspace data.

Evaluate

Applicable authorization

Sought through the applicable authorized pathway.

Request

Flight-specific authorization

Bound to this flight, not to the account in general.

Bind

Device validation

The device validates the authorization it holds for this flight.

Validate

Arm / operate

The operation proceeds with a recorded authorization state.

Operate
Simulated state sequence · illustrative only

StratoSense does not itself grant regulatory authorization. It integrates with, carries, validates and records authorization state issued through the applicable authorized pathway. Integration with DigitalSky is a target integration, subject to the appropriate authorized-service-provider and regulatory arrangements.

From aircraft to airspace

Follow one telemetry update.

A single reading leaves the aircraft and ends up somewhere an operator and an authority can both act on it.

Drone + Capaircraft side Controller + Tetherground side Connectivity StratoSense cloud Platformoperators · authorities · UTM

What the platform shows

Position
28.61°N 77.21°E
Altitude
118 m
Status
ACTIVE
Link
14 sats
Authorization
AUTHORIZED

Illustrative values

Live airspace

Watch a flight, start to finish.

A simulated operation running entirely in your browser. Nothing here is connected to a live aircraft.

ZONE B · CONTROLLED ZONE A · ADVISORY
READYSS-2291
Altitude
0m
Satellites
14sats
Ground speed
0.0m/s
Link
Standby

    Simulated · deterministic · no backend

    Platform

    The authority console.

    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.

    1. 01

      Ingest

      Authenticated telemetry arrives from the aircraft and controller side.

    2. 02

      Live picture

      One current view of who is flying, where, and at what altitude.

    3. 03

      Alerts

      Zone proximity and link conditions surface as advisories, not alarms.

    4. 04

      Replay

      Step back through any flight, second by second, after it has landed.

    5. 05

      Archive

      Records are retained and chained so later modification is detectable.

    The flight record

    Afterwards, go back to any moment.

    Scrub the timeline. The map, the altitude and the event all move together.

    EventTakeoff
    Time00:00
    Altitude0 m
    StatusCONNECTED

      Simulated · deterministic

      Two points of view

      The same flight, seen two ways.

      For operators

      Fly with confidence.

      1. BeforeAuthorization

        Know the flight is permitted before it leaves the ground.

      2. DuringMonitoring

        Position, altitude and link quality while airborne.

      3. AfterFlight record

        A replayable record of what actually happened.

      For regulators

      See the bigger picture.

      1. AirspaceWhat is happening

        Active flights and zones in one view.

      2. StatusWho is authorized

        Authorization state alongside each operation.

      3. HistoryWhat happened

        Records and events available after the fact.

      THE DIFFERENCE

      The information exists.
      The chain is fragmented.

      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 view
      Authorization Flight control Telemetry Fleet Compliance ✕ ✕ ✕ ✕ Airspace Authorization StratoSense Tether controller CAP aircraft Beacon detection Cloud Pilot Operator Authority
      —
      StratoSense connects the operational layers · it does not replace the ecosystem

      CLOUD / UTM

      Many operations.
      One picture.

      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 feed
      A-014 Tether + CAP A-007 Tether A-021 Tether + CAP A-052 Beacon detection Cloud associate + record Pilots this flight Operators this fleet Authorities connected + authorized connected sources role-based access
      —
      Coverage depends on deployed devices, connected aircraft and authorized data sources

      Explore the platform

      Incident review

      When something needs explaining.

      Select an event to jump the replay to that moment.

      FLIGHT SS-2291ZONE PROXIMITY

        Simulated demonstration

        System architecture

        How the pieces relate.

        Select any part to see what it connects to. High-level only — no implementation detail.

        StratoSense architecture

        Select a node to see its role and what it connects to.

        THE STRATOSENSE DIFFERENCE

        What if permission, airspace
        and flight were one chain?

        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 feed
        Identity Plan Airspace Authorize Device Arm Flight Telemetry Events Record SS-2291 the same flight, end to end
        —
        Simulated flight identity · illustrative only

        TWO DIFFERENT QUESTIONS

        What you were allowed to do.
        What you actually did.

        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 feed

        Permission

        What are you allowed to do?

        • Who — operator and remote pilot
        • What aircraft
        • Where — area and limits
        • When — the operating window
        • Operational conditions
        • Authorization state

        Telemetry

        What are you actually doing?

        • Position
        • Altitude
        • Speed
        • Heading
        • Battery
        • Route, flight state and events
        Plan versus actual Compliance
        —
        The comparison is the point · a permission alone proves nothing about the flight that followed

        FULL FLIGHT LIFECYCLE

        Plan to audit,
        in one chain.

        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.

        PLAN EVALUATE AUTHORIZE VALIDATE FLY RECORD AUDIT
        Lifecycle overview

        See the full architecture

        THE WHOLE PLATFORM

        Ten beats,
        one operational chain.

        01

        Every flight creates data.

        Position, state, health, events, a route, a mission context, an identity and an authorization context — produced by every operation, in every category.

        02

        The drone ecosystem is fragmented.

        Proprietary links, closed log formats, no shared identity and paperwork nobody can query. The chain stops before the airspace.

        03

        StratoSense connects the operational chain.

        Aircraft, controller, Tether, cloud, airspace — plus CAP on the airframe and Beacon observing independently, each on the interface it actually has.

        04

        Telemetry becomes structured intelligence.

        Raw packets are decoded, normalised to one schema and time base, and attributed to a device before anything reads them.

        05

        Flight plans become authorization context.

        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.

        06

        The pilot sees the operation.

        Airspace awareness before the flight, live state during it, and a record that can be returned to afterwards.

        07

        The operator sees the fleet.

        Every aircraft, every live and scheduled flight, every flagged event, with the authorization context attached to each.

        08

        The authority sees the operational picture.

        Built from connected devices and authorized data sources — and honest about the fact that this is not every drone in the sky.

        09

        The flight becomes a historical record.

        Plan versus actual, telemetry, events, device events and communication events, retained and protected so it reads later as it was written.

        10

        StratoSense connects the entire lifecycle.

        From the moment a pilot signs in to the moment an authorized auditor asks what happened.

        Built for trust

        A record is only useful
        if it can be trusted.

        • Device identity

          Hardware participating in an operation is identified, so data has a known source.

        • Authenticated comms

          Messages between devices and the platform are authenticated in transit.

        • Controlled access

          Operators and authorities see what their role permits — not everything.

        • Tamper awareness

          Records are chained so later modification is detectable on verification.

        • Flight records

          Each flight resolves to a durable record that can be replayed.

        • Auditability

          Events carry timestamps and origin, so a sequence can be reconstructed.

        Described at a product level. StratoSense does not publish its security implementation.

        Integration

        Built for a mixed fleet.

        Drone operations rarely run one make of aircraft or one controller. StratoSense is designed to work across heterogeneous equipment.

        • MAVLink
        • CRSF
        • SBUS
        • iBus
        • MSP
        • S.Port
        • LTM
        • NMEA

        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

        Five questions
        every flight has to answer.

        StratoSense / five questions, one chain

        Simulated feed
        01

        Airspace

        Where can I fly?

        02

        Permission

        Can I fly?

        03

        NPNT

        May I arm?

        04

        Telemetry

        What am I doing?

        05

        Compliance

        Did I follow the plan?

        —
        StratoSense sits across all five · simulated demonstration

        WHY THIS MATTERS

        Four things change
        when the chain connects.

        01

        Permission

        The aircraft knows whether the required permission and authorization state is valid before the relevant operation proceeds.

        02

        Visibility

        The operational system knows what the connected aircraft is actually doing, while it is doing it.

        03

        Accountability

        Identity, authorization, telemetry and events can be associated with a single flight record.

        04

        Airspace awareness

        The operation can be evaluated against applicable airspace information and restrictions.

        Subject to applicable regulatory requirements and authorized integration arrangements

        THE FAIR QUESTION

        Why build
        another system?

        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

        What is built,
        and what is not.

        Engineering concepts are not presented here as released features. This is where each part of the ecosystem actually stands.

        Portfolio / maturity

        StratoSense BeaconIndependent compliance detection and reporting.Established
        StratoSense CAPAircraft-side controlled airspace protection.Established
        StratoSense Cloud / UTMThe common operational picture.Established
        StratoSense TetherUnits built and bench-validated. Field validation in progress.In development
        DigitalSky integrationSubject to the appropriate authorized-service-provider and regulatory integration arrangements.Target integration
        No regulatory certification, government approval or partnership is claimed anywhere on this website

        Interoperability

        Beside Digital Sky,
        not instead of it.

        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.

        What registration gives you

        Who should be flying.

        1. IdentityRegistered aircraft and pilot

          A known operator, bound to a known airframe.

        2. PermissionAn approved intent

          A plan that was granted before the flight.

        What StratoSense adds

        What actually happened.

        1. LiveThe flight as it runs

          Position, altitude and link, while the aircraft is airborne.

        2. RecordA replayable account

          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.

        Know. Monitor. Protect.
        The skies.

        Airspace intelligence for the people who fly, and the people who oversee the flying.

        THE WHOLE LIFECYCLE

        From permission
        to proof.

        Connect the authorization, the aircraft, the telemetry, the airspace and the operational record into one continuous flight lifecycle.

        From permission / to proof

        Simulated feed
        Request Airspace Permission Verify NPNT Flight Telemetry Record
        —
        Simulated lifecycle · illustrative only

        No permission.
        No takeoff.

        StratoSense — the digital operational layer between drones and the airspace.

        Telemetry · Authorization · Compliance · Connectivity

        Request platform access