Sentinel SkyWatch
A drone fleet workspace for camera feeds, surveillance review, site alerts and flight practice.
Drone operators, surveillance teams and training leads
Organised aircraft, camera observations and mission records.
Sentinel SkyWatch gives drone teams a local workspace for aircraft, sites, camera observations and recorded missions. The operator flies with the aircraft’s own controller while the team reviews supported video inputs. A separate practice lab provides a simulated place to train.
Review registered aircraft, site context and recent workspace activity.
Register aircraft, assign operators and link camera inputs to sites. Ready, On mission and Maintenance reflect recorded operational status.
Review supported video inputs or recorded flight video, select viewing modes and capture snapshots or recordings.
Review several feeds and configure the supported detection categories, confidence, counts and site alert behavior.
The station offers enhanced modes and thermal palettes for suitable camera inputs.
Recorded mission status, alerts and detection activity support incident and mission reports. Operators can save reviewed snapshots and recordings.
A separate procedural 3D city supports keyboard, on-screen sticks and compatible controllers, with a tactical map and sensor view.
Application screenshots show fictional aircraft and a training workspace. The practice city is simulated. Registered aircraft status is an operational record, rather than live flight telemetry.
Review registered aircraft, site context and recent workspace activity.
Keep aircraft identity, readiness and operator assignment organised.
Practise in the simulated city using the supported training controls.
The administrator registers the aircraft, associates it with a site and assigns the responsible operator. Ready, On mission and Maintenance describe the team’s recorded operational status and help colleagues understand which aircraft is available.
The register does not replace the aircraft manufacturer’s pre-flight checklist, controller or flight recorder. The operator remains responsible for the physical aircraft, the operating environment and the permissions required for the mission. Site records provide context for the observation workflow.
Application preview with demonstration data.
A supported capture device or receiver can expose the aircraft’s camera as a video input. The team reviews that input through the camera workspace, uses configured detection tools and keeps relevant captures and observations for reporting.
Input quality, practical latency, browser permissions and processing capacity affect the result. Thermal interpretation needs suitable hardware and calibration; a coloured image palette alone does not measure heat. Aircraft flight control remains with the operator’s own equipment.
Application preview with demonstration data.
The practice lab provides a procedural city, a tactical map and supported keyboard, on-screen and compatible controller inputs. Training exercises give the operator a place to practise movement, landing and surveillance tasks within a simulated environment.
Treat practice as familiarisation. It is separate from live aircraft control and does not establish flight certification or manufacturer-specific proficiency. Validate controller mappings before an exercise and review the experience with the training lead afterwards.
Application preview with demonstration data.
Manage accounts, sites, registered aircraft and application security policy.
Maintain mission status and review the camera input while flying with the aircraft controller.
Examine authorised feeds, alerts and captured observations.
Use simulated practice missions to develop operator familiarity.
An operator surveys an authorised site.
Practical value: Aircraft responsibility and camera events remain organised.
Requirements: The operator flies independently using the aircraft controller.
The aircraft provides genuine thermal video.
Practical value: Viewing tools retain the limits of the input.
Requirements: Visible-light pseudo-thermal cannot establish measured temperature.
A team reviews multiple authorised inputs.
Practical value: The team can follow responsibility across the inputs.
Requirements: Capture channels, browser support and computer capacity must be tested.
A training lead selects the separate practice lab.
Practical value: Operators can practise the application workflow without a real aircraft.
Requirements: Practice does not certify the operator for live flight.
These scenarios explain workflows using fictional examples.
The operator flies using the manufacturer’s own equipment.
A supported capture device or receiver exposes the feed as a camera input.
The local browser/application organise cameras, aircraft, rules and observations.
Configured local storage holds records/media; the separate practice lab simulates flying.
Compatible receiver or capture device exposing a supported input.
This is video review, not aircraft command/control integration.
Appropriate hardware and camera type selection.
Thermal interpretation requires real thermal input and calibration.
Configured categories, thresholds and notification permissions.
Test sound and desktop notification delivery.
Configured external imagery and search providers.
These need their network services; the practice city is procedural.
Compatible browser gamepad, on-screen sticks or keyboard.
Test mappings, dead zones and disconnect behavior.
Review the selected scope, source records and intended audience. Confirm which staff may export or retain the output and protect downloaded files under your organisation’s policy.
Explore information handling and access →Confirm users, workflows, inputs and the outcome your team needs.
Set up accounts, sources, devices and the agreed integration scope.
Exercise normal and failure cases with representative inputs.
Train the responsible staff and agree recovery, maintenance and support.
No. The operator uses the aircraft’s own controller; Sentinel SkyWatch reviews video and organises observations.
No. The city, flight telemetry and detection sensor are simulated.
No. Heat interpretation requires thermal hardware and calibration.
The supported deployment count depends on capture hardware, browser support and measured computer capacity.
Local features can run locally; maps, search and initial provisioning may need network services.
The agreed software deployment, capture arrangements, training and support. Aircraft and specialist hardware need an explicit commercial scope.
Sentinel SkyWatch does not fly a real aircraft. Operators use the aircraft’s own controller. The practice lab is a simulation; its detections and flight telemetry are training data.
Tell us who will use the product, which inputs or devices you need to connect and how you want to deploy it. We can then define a demonstration and a separate product-specific quotation.
Capabilities, practical examples and deployment requirements for this product.
Review the implemented capabilities and their operating conditions.
Explore features →Follow illustrative workflows and the records needed for review.
Explore use cases →Understand supported connections and the work needed to commission them.
Explore integrations →Review access boundaries and operational responsibilities.
Explore security →Plan a pilot, acceptance tests, training and support.
Explore deployment →Read the full proposal and use the editable presentation.
Explore proposal & slides →