One operating model. Configured around your sites, policies, and operations.
The software doesn’t change. The operation does.
24 example missions across 5 segments, each written the way it
actually runs. What changes between them is which capabilities the operation leans on — not
the platform.
01 · Trigger
What starts it — a schedule, a saved template, or a call.
02 · Plan
How the mission is built, before any aircraft is named.
03 · Fly
What happens in the air, and what keeps being checked.
04 · Deliver
How results leave the platform and reach your systems.
Common examples, not a catalog — the 27 capabilities behind them recombine into far
more missions than the 24 here.
Nothing matches that wording. Clear the filter, or pick a capability instead of typing a phrase.
Segment
Oil & Gas
One fleet over a live plant: security, safety and inspection in one workflow, scans returned as models.
An area scan over the process units, returned as a stitched 2D map and 3D model inside the platform.
01 · Trigger
A polygon drawn over the tank farm, jetty or unit is filed as an area-scan mission and saved for reuse.
02 · Plan
The platform lays route points across the polygon from scan angle, altitude with terrain following, and heading and side overlap.
03 · Fly
A photo is taken at each route point, with the route re-validated continuously against no-fly volumes, the terrain model and energy.
04 · Deliver
Internal photogrammetry stitches the frames into a 2D map and a 3D model, held on the platform with the flight record.
You end up withA dated 2D map and 3D model of the site, on the platform.
An operator flies the shot manually around a flare or stack, and the flight is recorded as a repeatable mission.
01 · Trigger
An inspector takes manual control (MC2) and flies the standoff and angles the shot actually needs, with live video.
02 · Plan
The flown path, camera and gimbal instructions are captured as a mission template rather than drawn as waypoints beforehand.
03 · Fly
Replayed later, the platform flies the recorded geometry itself, re-validating it against no-fly volumes, terrain and energy.
04 · Deliver
Each replay files against the same template, so this quarter's frames line up with the last from the same positions.
You end up withA hand-flown inspection turned into a mission anyone can repeat.
Captured imagery is routed from the processing hub to the third-party processing and asset-management tools your engineering team already runs.
01 · Trigger
The same scan or inspection mission runs; its imagery lands in the processing hub with its flight and telemetry data.
02 · Plan
The hub is set to the engine that handles this job: built-in photogrammetry, a VLM, or your third-party engine.
03 · Fly
Frames are captured at each route point with their position and gimbal angle, so imagery reaches the engine ready to process.
04 · Deliver
Results and imagery move on through APIs, the AI results datalake, or an RTSPS stream into your asset-management system.
You end up withImagery and results inside the processing and asset systems you already run.
Perimeter security, safety oversight and asset inspection run as missions on one fleet, under one set of restrictions.
01 · Trigger
A gate alarm, a hot-work permit or an inspection request each open as a mission in the same refinery work area.
02 · Plan
Each is a mission type: patrol for the fenceline, target tracking on the work party, area scan or patrol for assets.
03 · Fly
Allocation draws from one fleet; a drone in Ready On Air is re-tasked from a patrol to the alarm without landing.
04 · Deliver
All three file into the same log: 3D debrief with synced video, PDF report, JSON export, one record per site.
You end up withOne fleet, one log, covering the perimeter, the work party and the assets.
Ground robots run indoors and inside confined process areas under the same mission model as the aircraft.
01 · Trigger
An indoor round — compressor house, pump room, culvert — opens as a mission and is allocated to a ground robot.
02 · Plan
The same template applies: a patrol route with a scan or static view at each point, each carrying one AI action.
03 · Fly
The robot works through the route while the operator watches low-latency video and can take manual control (MC2) at any point.
04 · Deliver
Indoor passes store beside the flights above: same debrief playback, same PDF report, same JSON export, one asset history.
You end up withIndoor and confined-space inspection recorded in the same asset history.
Segment
Homeland Security
Autonomy turns a cue or a schedule into a drone overhead, with detection running as it flies.
Patrol templates you keep and reuse, plus missions built on the spot from a cue, dispatched the same way.
01 · Trigger
A shift starts on a saved patrol template, or a cue arrives and an operator opens a mission on those coordinates.
02 · Plan
Either way the mission carries destination or route, camera and gimbal instructions, AI instructions and altitude behaviour before any drone is named.
03 · Fly
Allocation takes the first enabled drone, or you dispatch one by hand; the route is generated from its status, restrictions and energy.
04 · Deliver
Both kinds of mission close the same way: stored flight data, 3D debrief playback with synced video, PDF report, JSON export.
You end up withA drone over the point, whether the mission was saved or new.
Detection engines run on the camera actions inside the mission, so results arrive during the flight, not after.
01 · Trigger
You attach one AI action to a camera action — scan, static view or flying view — when you build the mission.
02 · Plan
The processing hub holds built-in engines, VLM engines and third-party engines; prompt-based detection lets you describe the object in words.
03 · Fly
At each route point the camera performs its action and the attached engine runs on that imagery; results reach the operator panel.
04 · Deliver
Results land in the AI results API and datalake, and stream to your C2, alerting or VMS through the pre-integrations.
You end up withNamed detections tied to the route point and frame that produced them.
The same polygon flown as an area scan on a schedule, each composite compared against the passes before it.
01 · Trigger
A polygon over the ground you care about is saved as an area-scan mission, then run again from the same template.
02 · Plan
Altitude behaviour and overlap set the route points across the polygon; reusing the template keeps every later pass on the same grid.
03 · Fly
The drone photographs at each route point; internal photogrammetry stitches the frames into a 2D composite and a 3D model.
04 · Deliver
Each pass is stored against the same mission, so this week's composite sits beside last month's for comparison and export.
You end up withDated maps and 3D models of the same ground, pass by pass.
3D no-fly and restricted volumes the platform holds to in flight, with detection reporting what enters them.
01 · Trigger
Perimeter, work areas and 3D no-fly volumes are defined once; the platform evaluates them continuously against every active mission.
02 · Plan
Routes are validated against those volumes, the terrain model and the altitude matrix before a drone is allocated to the mission.
03 · Fly
A restriction added mid-flight triggers automatic re-validation and re-routing, while a camera action's AI flags people or vehicles inside the zone.
04 · Deliver
Zone entries and re-routes are logged with time and reason, replayable in the 3D debrief and exportable as PDF or JSON.
You end up withFlights that stay inside the volumes, and a record of every incursion.
Rounds placed on the mission calendar, whose detections and imagery close out as a report per flight.
01 · Trigger
The mission calendar starts the round at its set time — hourly, nightly, shift change — with no operator at the console.
02 · Plan
The saved template supplies route, camera actions and AI actions; allocation generates the flyable mission from drone status, restrictions and energy.
03 · Fly
Each scheduled flight runs the same actions at the same points, so detections and imagery arrive in the same structure every round.
04 · Deliver
The flight closes into a PDF report and JSON export, with detections in the results API — assembled by the platform.
You end up withA report per scheduled round, ready without an analyst assembling it.
Segment
Public Safety
A call, an alert or a dispatch record becomes a mission the platform plans, flies and records.
The agency's dispatch or C2 system requests a mission over the API, and the platform files and runs it.
01 · Trigger
A dispatch record or C2 task arrives over the API as an objective, and the platform opens the matching mission.
02 · Plan
Pre-integrations map the incident coordinates and type onto a saved mission template: route, camera actions, AI instructions, altitude behaviour.
03 · Fly
Allocation assigns a drone and the platform flies the mission; mission phase and video return to the C2 operator's screen.
04 · Deliver
Flight and mission data return through the API, with the PDF report and JSON export filed against that call.
You end up withA mission flown and recorded from the dispatch record that started it.
One flight's video reaching units on the ground and the command room at the same time, over encrypted streams.
01 · Trigger
A mission goes airborne and the platform opens its video stream out over RTSPS, encrypted, with no cap on simultaneous viewers.
02 · Plan
Each recipient — command room, vehicle laptop, a handheld in the field — is subscribed to the same stream from the platform.
03 · Fly
Video runs at low latency while the operator can take manual control (MC2) of the drone from the same picture.
04 · Deliver
The same feed lands in the VMS through the pre-integration and in the flight record for debrief playback.
You end up withThe same live picture in the command room and in every unit's hands.
A situation such as violence or a collision is typed as a description and bound to a camera action.
01 · Trigger
An operator writes the situation to look for in words, and attaches it to a camera action as its AI action.
02 · Plan
Each route point carries one camera action — scan, static view or flying view — and one AI action with that description.
03 · Fly
The processing hub runs the VLM engine on the frames in flight and returns matches with time and location.
04 · Deliver
Results reach the operator panel, the AI results API and the datalake; orchestration can chain an alert or another action.
You end up withSituations found by description, timestamped, located and available over the API.
An alert from an alerting system or VMS becomes an active mission and launches a drone, with no pilot planning.
01 · Trigger
An alert arrives through the alerting or VMS pre-integration and activates the mission template saved for that alert type and location.
02 · Plan
Allocation takes the first enabled drone and generates a tailored mission from its status, the restrictions matrix and available energy.
03 · Fly
Takeoff, on mission, observing — the phases run unattended; a drone already in Ready On Air is re-tasked without landing.
04 · Deliver
Video and mission phase reach the command room as the drone climbs, and the whole run stores for 3D debrief.
You end up withAn aircraft over the alert location, launched and recorded without a pilot.
A venue and its approaches flown as scheduled patrols and area scans for the hours the event runs.
01 · Trigger
The event area is drawn as a work area, and the calendar schedules patrol and area-scan missions across the event window.
02 · Plan
Route points get scan sweeps over the crowd and static views on the gates, each with one prompt-based detection.
03 · Fly
A closure added mid-event re-validates the missions and re-routes remaining legs; command can re-task any drone onto a target.
04 · Deliver
Every lap is stored, so the event replays in 3D with synced video, and exports as PDF or JSON.
You end up withContinuous coverage for the whole event, and a replayable record of it.
Segment
Municipal & CI
Autonomy turns scattered public assets, roads and open space into scheduled rounds the platform plans, flies and documents.
Scheduled rounds over scattered public assets — pumping stations, reservoirs, depots — returned as stitched maps and 3D models.
01 · Trigger
The mission calendar opens the stored round for that site group on its due date, as a patrol with area scans.
02 · Plan
Each site's polygon carries scan angle, altitude with terrain following, and heading and side overlap; the platform lays route points across it.
03 · Fly
Allocation generates a tailored mission from the drone's status, restrictions matrix and energy; a photo is captured at every route point.
04 · Deliver
Internal photogrammetry stitches the frames into a 2D composite and 3D model, stored with the flight for PDF report or JSON export.
You end up withA dated map and 3D model per site, with the flight record.
Plate recognition runs as the AI action on the mission's video, over car parks, gates and traffic corridors.
01 · Trigger
An operator or an API call activates the mission over the car park, depot gate or corridor to be read.
02 · Plan
A static view or scan action at each route point carries plate recognition as its one AI action, at a set altitude.
03 · Fly
The processing hub runs the plate engine on the live video; reads reach the operator panel and the AI results API.
04 · Deliver
Each read is stored with its frame, time and location in the datalake, and exports as PDF or JSON to your systems.
You end up withTime and location-stamped plate reads, with the frame each came from.
Vehicle counts and flow read from a held aerial view over a junction, roundabout or arterial corridor.
01 · Trigger
The scheduler runs the stored traffic mission at the hours you want counted — peak, off-peak, event day — over the same junction.
02 · Plan
A static view holds the junction in frame at a fixed altitude and gimbal angle, with vehicle counting as its AI action.
03 · Fly
Counts accumulate while the platform recalculates energy against the route home; a replacement drone takes the same mission to extend the window.
04 · Deliver
Counts land in the AI results API and datalake; because the geometry is fixed, each session compares to the last.
You end up withVehicle counts per session from a repeatable viewpoint, with video and JSON.
Repeat passes over public space, with dumping, restricted-area entry and crowding described in words as the AI action.
01 · Trigger
The calendar runs the saved patrol over the park, beachfront or lay-by list on its schedule, or a complaint activates it early.
02 · Plan
Each route point carries a scan or static view with one prompt-based detection: dumped waste, people in a closed area, crowd density.
03 · Fly
The drone flies the round while 3D no-fly zones over the crowd and the altitude matrix hold it inside its permitted volume.
04 · Deliver
Hits reach the alerting and VMS integrations as they happen; the round replays in 3D and exports as PDF or JSON.
You end up withA dated pass per location, with flagged sites and crowding levels.
Segment
General Drone Ops
Autonomy turns the everyday jobs — patrol, monitoring, counting, inspection, video out — into saved missions any drone can fly.
The same route, camera actions and altitude behaviour flown again on every pass, at any site in the fleet.
01 · Trigger
The platform activates the saved patrol mission on its scheduled slot, on operator start, or on an API call.
02 · Plan
Route points, camera actions and altitude behaviour come from the template, re-validated against no-fly volumes, the terrain model and the altitude matrix.
03 · Fly
The first enabled drone is allocated and flown through each point's camera action; a new restriction triggers re-validation and re-routing mid-pass.
04 · Deliver
Every pass files under the same template, so debrief playback, PDF report and JSON export line up run against run.
You end up withA dated pass-by-pass record of each site, comparable against every earlier patrol.
Continuous watch over a fixed point or sector, carried on the low-latency stream with one detection bound to the action.
01 · Trigger
An alarm from the C2 or VMS integration, or an operator, opens a monitoring mission over the point that needs watching.
02 · Plan
A static view fixes the point of observation, or a scan sweeps the sector over a set time; one AI action attaches.
03 · Fly
The drone holds the Observing phase over the scene; low-latency video runs live while detection results post to the AI results API.
04 · Deliver
Detections reach your alerting and C2 systems as they land; video and results stay in the flight log and datalake.
You end up withA watched scene with detections in your alerting stack, and the video retained.
Counting what is in a scene, then keeping one moving object in frame as it leaves the count area.
01 · Trigger
The operator types what to count — vehicles in a yard, pallets on a pad — as the mission's detection prompt.
02 · Plan
A static view frames the scene for the count; a target-tracking mission waits, gimbal locked to a point the operator moves.
03 · Fly
The AI action returns the count from the framed scene; on target tracking the route recomputes dynamically to keep the object centred.
04 · Deliver
Counts post to the AI results API and datalake; the tracked run replays in 3D debrief with synced video.
You end up withA number for the scene, and video of the object held in frame.
Detailed capture of a structure or machine from a standoff distance and angle saved for every repeat visit.
01 · Trigger
A maintenance objective — this asset, this angle — arrives from the operator or the work system and becomes an inspection mission.
02 · Plan
Route points sit at the standoff geometry you set, each carrying a static view or a scan across the asset face.
03 · Fly
The drone works each point in order; the operator can take manual control (MC2) on the live video for a closer angle.
04 · Deliver
Frames land against the same asset record, with 3D debrief playback, a PDF report, JSON export, and photogrammetry on request.
You end up withClose-range imagery of the asset from the same geometry each visit.
Flight video captured and stored, then streamed out over RTSP to the systems and people who need it.
01 · Trigger
Any mission that flies produces video; the platform starts recording and opens the stream as the drone leaves the ground.
02 · Plan
Camera actions set what the frame holds: a sector sweep, a fixed point of observation, or an angle carried along a leg.
03 · Fly
Secure RTSP or RTSPS carries the live feed to your VMS, C2 and any viewer, with no cap on simultaneous streams.
04 · Deliver
The recording stays with its flight and mission data, replayable in 3D debrief with synced video, exportable as PDF or JSON.
You end up withLive feeds where they are needed, and stored video tied to the flight.
Start with the mission.
Tell us which missions your operation needs — a person replies by email with how they would run on the platform.
Cookies: this site uses only the session cookies it needs to work. No advertising,
no cross-site tracking, no profiling. Details in our privacy notice.
