AI Engineer World's Fair 2026

One Operator, Many Drones: Inside Skydio's Autonomy Stack — Suchet Bargoti, Skydio

Read the talk

One Operator, Many Drones: Inside Skydio's Autonomy Stack

A live fleet demonstration leads into the engineering behind drones as infrastructure: immediate control on the aircraft, heavier reasoning in the cloud, maps refreshed by flight observations, and agents that use tools without replacing the systems responsible for safe flight.

From a talk by Suchet Bargoti

At a glance

Ideas worth remembering

  • Fleet operation requires drones to continue executing safely while the operator attends to another task; assigning a pilot to every aircraft preserves a staffing bottleneck.

  • Immediate actions run on the drone, while cloud inference supports heavier reasoning and longer-term planning. Useful video under limited bandwidth helps make that split work.

  • A shared map supports global navigation, and fleet observations can refresh it when construction changes the environment.

  • The white Jeep example connects a language request to trajectory and tracking tools. The agent chooses how to use capabilities already exposed by the drone system.

  • End-to-end learning can reduce manually written behavior, but difficult failure diagnosis and reliability guarantees still shape where it belongs in physical systems.

Launching a second drone while the first keeps flying

Suchet Bargoti of Skydio begins by flying. From a laptop, he launches a docked drone in San Mateo and uses his keyboard to look around. The important change comes when he switches away from that aircraft: he starts a second drone in Colorado while the first remains airborne. The Colorado dock opens and runs its prelaunch safety checks. One interface now coordinates work in two distant places.

Source frame: Launching a second drone while the first keeps flying
Source frame: Launching a second drone while the first keeps flying

The imagined Colorado task is an inspection after an incident on power lines. The actual engineering requirement is broader: neither aircraft can depend on the operator continuously attending to it. Everything runs over conference Wi-Fi, and Bargoti says safe operation must continue even if he closes the laptop. That requirement moves responsibility into the vehicle and the services behind the interface.

Back at the first drone, Bargoti selects a passing car to track and takes his hands off the controls. The autonomous system takes over following the vehicle, leaving him free to start a third drone at headquarters. This is the opening example of the stack's division of labor: a person chooses a task, the aircraft executes the ongoing movement, and the fleet interface allows attention to move elsewhere.

0:290:52
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:12 · section reference included

From a tool in a truck to infrastructure on call

The dock changes how a drone becomes available. Bargoti describes a progression from hobby aircraft roughly 15 years earlier, to industrial tools roughly 10 years earlier, to installed infrastructure. A tool travels with someone in a truck; an installed drone can launch where the work is needed. He reports thousands of docked systems deployed with utilities, public safety organizations, and construction companies.

Source frame: From a tool in a truck to infrastructure on call
Source frame: From a tool in a truck to infrastructure on call

The interface could eventually become a high-level request from a Slack bot: an incident happens, and a drone responds without someone managing every flight action. That is a future direction, distinct from the certified pilot operating this demonstration. For now, Bargoti tells the fleet to pause and return to dock, then begins the presentation while the aircraft handle the return.

Two customer examples explain why availability matters:

  • Utility patrols: A system installed near a power station on the northeastern US coast found a pole burning from the inside during a normal patrol. The concern was that it could fall and create a fire risk. A nearby drone makes inspection possible without first sending people to the site.
  • Following a stolen car: In the SFPD example, a drone maintains observation while a person changes the vehicle's license plate and later prepares to tint its windows. Continued aerial observation gives police time to position themselves for an intervention. Bargoti presents this as a safer alternative to a high-speed chase; the example does not establish a measured reduction in pursuit risk.

Installed infrastructure also has to work across weather and geography. Bargoti names docks in Alaska's cold and Texas's extreme heat, and reports about 16 million people living within a two-mile radius of this infrastructure. He states a reliability requirement of 99.9999%, supported by simulation and testing work. The recording does not define the event or denominator for that percentage, so it should be read as a stated engineering requirement rather than a demonstrated fleet-wide success rate.

0:581:02
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

3:38 · section reference included

The scaling limit is the operator's attention

A skilled pilot assigned to each drone creates a staffing problem as calls and alerts increase. Fleet control aims to let an operator specify an objective without continuously worrying about flight. Yet the opening demonstration still required Bargoti to choose and launch each aircraft individually. Even for an experienced operator, that introduces cognitive load. The longer-term ambition is to issue objectives such as searching an area for a missing person or finding a particular type of car.

Source frame: The scaling limit is the operator's attention
Source frame: The scaling limit is the operator's attention

Before moving deeper into the architecture, Bargoti checks the fleet: all the drones have landed. He is still pleased when that works, even though it is supposed to happen every time. The moment connects the ambition to its prerequisite. Delegating more tasks only helps if launch, flight, tracking, and recovery remain dependable while attention moves away.

Skydio controls the hardware, software, cloud services, user interface, and autonomy together. That allows decisions about perception and flight behavior to account for altitude, speed, cloud, rain, unreliable urban GPS, and objects hidden by buildings. These conditions affect one another: a tracking task still needs navigation, and navigation still needs a usable understanding of the environment.

Flights also produce the evidence for improving those systems. Logs capture the difference between an instruction and what the drone did, or between an expected outcome and what happened. Those discrepancies feed retraining and evaluation, including reinforcement learning, before updated systems return to the field. Bargoti puts data handling inside this learning cycle: private information needs to be removed, and customers need to understand what they share.

8:068:08
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

7:45 · section reference included

Immediate action on the drone, heavier reasoning in the cloud

Autonomy runs in two places. Immediate autonomous actions happen on the drone. Video and telemetry also pass through cloud servers, where GPUs and inference engines can support heavier computation and longer-term planning. The split lets the system use cloud resources without making every immediate action wait for a remote answer.

Source frame: Immediate action on the drone, heavier reasoning in the cloud
Source frame: Immediate action on the drone, heavier reasoning in the cloud

That division makes the uplink part of the intelligence system. Cloud reasoning depends on what information reaches the server, so Skydio invests in encoding video into smaller sizes and decoding it into clearer images under limited bandwidth. Bargoti describes better video quality under the same network conditions, without specifying a codec or compression method. The causal point is straightforward: more useful visual information gives remote inference a better view of the scene.

11:2911:33
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

11:25 · section reference included

A map is a world model the fleet can refresh

The first kind of model is a map. Local perception helps an aircraft respond to nearby obstacles, but a trip from one part of a city to another also needs global planning. Repeatedly discovering buildings along the way is a poor substitute for choosing a route with prior knowledge. Skydio combines prior information, building data, and vector data such as roads and power lines into a map the drone can use for planning and navigation. Those layers can also support different behavior in different areas.

Source frame: A map is a world model the fleet can refresh
Source frame: A map is a world model the fleet can refresh

A construction site provides a concrete example of how that model changes. Points representing the system's knowledge are rendered over a video feed, but some do not line up with the current scene: new construction has appeared that the map did not contain. Flying drones observe the changed area. After returning and supplying their data, those observations feed map synchronization. In the next iteration, the fleet can plan with the updated map.

How does one drone's observation become useful to other aircraft? The flow below follows the construction-site example from a stale map to a shared update. The important relationship is the return path: fleet operations consume the map, but also produce observations that improve the map for subsequent operations.

How it fits togetherFlight observations refresh the fleet's map

Building, road, and power-line information supports navigation.

New construction creates a mismatch between prior map knowledge and the observed scene. Returned flight data feeds synchronization, and the updated map supports the next round of planning.

12:5312:56
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

12:41 · section reference included

Tracking continues when the target disappears

The next model understands and tracks objects. A target moving behind a building requires more than recognizing it in each visible frame. The system needs a representation of the hidden object and an expectation of where it might emerge. That expectation informs the drone's own movement: it can reposition to regain a view on the other side. Tracking therefore joins perception to action.

Source frame: Tracking continues when the target disappears
Source frame: Tracking continues when the target disappears

Learned approaches, including reinforcement learning, can help choose these movements without explicitly engineering every occlusion case. The operational challenge remains vision-based tracking across rain, snow, day, and night. Here too, computation divides between locations:

  • On-device tracking: A minimal tracking capability runs on the aircraft.
  • Cloud tracking and reasoning: Heavier models, including vision-language models, can consider the broader map and return guidance for larger movement decisions. Bargoti describes one-to-two-second feedback latency as usable for those broad decisions, rather than for the immediate response expected from faster tracking.

Infrastructure inspection adds semantic understanding: the drone must identify what is in the scene before deciding what action fits an instruction such as inspecting a faulty line. Skydio builds primitives and tools for understanding utility poles and acting around them. Those capabilities can be called from conventional code today and made available to an agent that needs to understand what the drone sees and what it can do next.

14:4414:49
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

14:44 · section reference included

Finding a white Jeep by composing drone tools

The agent example begins with a user asking the system to look for a white Jeep. A vision-language model (VLM) accesses a drone API to command a search trajectory. As the aircraft moves, visual inference examines the scene for the requested vehicle. Once it finds a candidate, the agent calls tools that let the drone track and follow it. The visible task changes from searching an area to following an identified target.

Source frame: Finding a white Jeep by composing drone tools
Source frame: Finding a white Jeep by composing drone tools

What connects a language request to physical following? The flow below separates the agent's choices from the tools that carry them out. Search movement produces new visual context; recognizing the requested vehicle leads to a different tool call. The agent composes existing capabilities rather than requiring a custom rule sequence for this particular request. This is an illustrated capability in the talk; its production deployment scope is not specified.

How it fits togetherFrom vehicle description to tracking

The user supplies the target description.

The VLM uses a trajectory API to search, evaluates the resulting scene, and invokes tracking tools after finding the requested vehicle.

16:5416:57
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

16:54 · section reference included

Where end-to-end learning still needs structure

The longer-term learning ambition is to feed raw sensor data into a system that directly produces the right action: where to point, where to fly, or how to actuate the aircraft. Skydio is testing and training with reinforcement learning toward such behavior. The obstacle is the reliability required of a physical system. When a completely end-to-end system fails, diagnosing what went wrong and establishing reliability guarantees remain difficult.

Source frame: Where end-to-end learning still needs structure
Source frame: Where end-to-end learning still needs structure

That leaves a practical design decision: which parts should become learned behavior, and which parts benefit from an explicit representation of the world? Search and rescue illustrates the pressure to change. A manually written strategy can accumulate branches: inspect trees, look underneath, turn on thermal sensing, then search somewhere else if nothing appears. High-level tools give an agent ways to choose among those actions using the current context, reducing the need to encode every branching strategy in advance.

The closing direction extends beyond the demonstrated quadcopter. Skydio is applying similar thinking to a smaller quadcopter and beginning to explore fixed-wing aircraft within the infrastructure model. Basic interaction APIs would let cloud agents orchestrate these vehicles and make higher-level decisions. The aspiration to launch and recover from anywhere remains a direction of travel; the reusable mechanism is the same one shown in the Jeep example: expose useful vehicle capabilities, then let the cloud compose them into a task.

17:4517:47
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

17:45 · section reference included

Read the complete timestamped transcript
  1. 0:12

    Thanks everyone for coming. So we'll be

  2. 0:14

    talking about how um to use Agentic sort

  3. 0:18

    of orchestration to command many many

  4. 0:20

    different drones to achieve the

  5. 0:21

    different tasks that we have ahead of

  6. 0:23

    us. and just going to rethink this

  7. 0:26

    presentation a bit and not just jump

  8. 0:27

    straight into slides, but instead we're

  9. 0:29

    going to fly. Um, so what we have here

  10. 0:33

    on the left hand side is a real time

  11. 0:35

    view. What we're going to be doing right

  12. 0:37

    now, am I showing anything?

  13. 0:41

    >> Well, I'm flying. There you go. Sweet.

  14. 0:44

    Okay. Um, we are somewhere here in the

  15. 0:47

    city down south, which where where our

  16. 0:49

    headquarters is. Uh we have a few drones

  17. 0:52

    up and I'm going to hit launch. Uh and

  18. 0:56

    these are drones that are in docked

  19. 0:58

    stations. So we calling this drones as

  20. 1:00

    infrastructure uh where we actually have

  21. 1:02

    thousands of these drones now planted

  22. 1:04

    around the country with power utilities

  23. 1:07

    with uh public safety uh with

  24. 1:09

    construction companies. And what I'm

  25. 1:12

    doing right now is using my keyboard to

  26. 1:14

    simply fly here. Uh for those of you

  27. 1:17

    that know the area, this is San Mateo.

  28. 1:19

    And perhaps if I kind of zoom in here,

  29. 1:22

    we may see a very faint render of the uh

  30. 1:24

    SF skyline. Although the uh the fog city

  31. 1:28

    is always there. So we might just say

  32. 1:29

    hello to um the uh SFO airport here.

  33. 1:33

    Some planes are launching. If anyone has

  34. 1:35

    a plane tracker app, they can sort of

  35. 1:36

    see this is uh realtime stuff there. So

  36. 1:40

    what we have been building is the full

  37. 1:42

    autonomy stack behind like how does a

  38. 1:44

    vehicle operate autonomously? How does

  39. 1:45

    the cloud system operate here? How do

  40. 1:47

    the cloud servers work? uh and where

  41. 1:49

    does the uh different levels of

  42. 1:51

    intelligence and automation needs to

  43. 1:53

    happen for us to make this happen

  44. 1:54

    robustly such that when I'm here and

  45. 1:57

    saying hey oh there's an incident

  46. 1:58

    happening here I need to go respond I

  47. 2:01

    could at the same time go back here and

  48. 2:03

    say hey what about that other thing

  49. 2:04

    that's happening on the other side of

  50. 2:06

    the country what if we launch that

  51. 2:08

    instead so while that's happening I'm

  52. 2:11

    now going to launch something in

  53. 2:13

    Colorado

  54. 2:14

    so this is a imagine some sort of fire

  55. 2:17

    incident has happen on your on the power

  56. 2:19

    lines and we wanted to go out and

  57. 2:21

    inspect those things. So, a dock is now

  58. 2:24

    opening up in Colorado while the first

  59. 2:26

    drone is still flying safely. Um, and

  60. 2:29

    I'm just going to uh let it do all the

  61. 2:30

    safety checks that it needs to do before

  62. 2:32

    the launch. And this is all happening in

  63. 2:34

    sort of conference Wi-Fi traffic. So,

  64. 2:36

    you can imagine I can shut down my

  65. 2:38

    laptop right now and everything needs to

  66. 2:39

    safely happen behind the scenes.

  67. 2:42

    Um, so I'm going to do this while the

  68. 2:45

    first part is still happening.

  69. 2:47

    Let me let's go back to the first drone.

  70. 2:52

    Might give it another set of

  71. 2:53

    instruction. Let's have a look around

  72. 2:55

    here on the first drone. The second

  73. 2:57

    drone has sort of kick started off and

  74. 2:59

    maybe there's some cars sort of going

  75. 3:01

    around there um that we can perhaps

  76. 3:03

    track. So, let's track and what's this

  77. 3:08

    car doing here? All right. So, we're now

  78. 3:10

    tracking this car. Maybe this is a

  79. 3:11

    runaway car that we needed to follow.

  80. 3:13

    And I'm hands off right now. This is uh

  81. 3:15

    the autonomous system kind of taking

  82. 3:17

    over um through the various interactions

  83. 3:19

    that I've given uh for it to do. And at

  84. 3:22

    the same time while this is happening we

  85. 3:24

    can do the final thing which is yet

  86. 3:27

    another sort of drone in the system uh

  87. 3:31

    back at our HQ

  88. 3:34

    and we can say hey let's why don't we

  89. 3:36

    run a third drone.

  90. 3:38

    So what we're building towards is how do

  91. 3:40

    we enable autonomy at scale where

  92. 3:44

    traditionally how it started off

  93. 3:46

    historically 15 years ago that you might

  94. 3:48

    have a drone at home. It's a hobbyist

  95. 3:51

    drone and you might play around with it.

  96. 3:52

    You will tinker with it. You will work

  97. 3:53

    with the controlling software. And then

  98. 3:56

    about 10 years ago drones started to

  99. 3:58

    become a lot more available and they

  100. 4:00

    started to become a tool. A lot of

  101. 4:02

    industries out there started to use

  102. 4:03

    them. They will carry them with them in

  103. 4:04

    the truck, go out there, deploy it. And

  104. 4:07

    the next era that we're working towards

  105. 4:09

    is drones as infrastructure. Imagine

  106. 4:11

    these systems. And for the sake of this

  107. 4:13

    conference, I'm going to call them

  108. 4:14

    agents. These are physical emboded

  109. 4:16

    agents that are kind of available at all

  110. 4:18

    times at anywhere for the different sort

  111. 4:20

    of use cases that we're interested in

  112. 4:22

    that can automatically uh uh launch,

  113. 4:25

    execute, and do their tasks. And what is

  114. 4:27

    the minimum amount of autonomy that

  115. 4:29

    needs to be begged in? And what does the

  116. 4:30

    future interface look like today?

  117. 4:32

    Everyone needs to be a dedicated pilot.

  118. 4:35

    I go went through a certification

  119. 4:36

    exercise. I need to think about the

  120. 4:37

    safety standards here. But you can

  121. 4:39

    imagine in a few years time the safety

  122. 4:42

    is going to be determined by the

  123. 4:43

    autonomous system and the interface

  124. 4:46

    becomes really high level. It could be a

  125. 4:48

    little slack bot that says, "Hey,

  126. 4:49

    something's happened here. Why don't we

  127. 4:51

    go send a drone?" And you might not even

  128. 4:52

    know that the drone launched.

  129. 4:55

    So, while this is happening, I'm going

  130. 4:57

    to tell all the drones to pause and

  131. 4:59

    return to doc.

  132. 5:03

    So, we'll write this. They're all going

  133. 5:05

    to start returning to doc. And while

  134. 5:07

    that's happening, I'm going to start on

  135. 5:08

    the presentation.

  136. 5:14

    So, what I've shown you here is not just

  137. 5:16

    concept. These are literally systems

  138. 5:18

    that are being used in production. Uh as

  139. 5:20

    was mentioned we are the largest

  140. 5:22

    manufacturer of drones in the US and we

  141. 5:24

    want to give people superpowers uh

  142. 5:25

    through this technology.

  143. 5:28

    Let's take a quick look at what some of

  144. 5:30

    the people are doing here. This is um in

  145. 5:32

    the northeast coast of the US uh where

  146. 5:34

    our client has set up uh the system next

  147. 5:37

    to a power station and they kind of used

  148. 5:39

    this to do normal patrols and as they

  149. 5:40

    flew around they found that some of the

  150. 5:43

    there was a the pole was burning from

  151. 5:45

    the inside and it was really starting to

  152. 5:47

    show up here and this could have fallen

  153. 5:48

    at any time and created a fire risk that

  154. 5:50

    they would have otherwise not caught

  155. 5:52

    without having to send people there

  156. 5:54

    which itself is quite uh expensive.

  157. 5:59

    Moving on to the sort of next use case

  158. 6:01

    is on the public safety side. This is

  159. 6:03

    San Francisco. Uh we work very closely

  160. 6:06

    with SFPD. Um normally when a car gets

  161. 6:08

    stolen, you'll see a high-speed chase

  162. 6:10

    happening in the city. Quite dangerous.

  163. 6:12

    But what if you could deploy a drone

  164. 6:13

    instead where the uh people in the car

  165. 6:16

    don't even know that there's a drone

  166. 6:18

    following them. Here's a person who has

  167. 6:20

    stolen the car on the right hand side

  168. 6:22

    and they're about to change their

  169. 6:23

    license plates uh on that. So they go

  170. 6:27

    here, get out their tools. They come

  171. 6:29

    back, luckily they point the license

  172. 6:31

    plate up so the drone can see it and we

  173. 6:32

    know exactly what they're doing. But

  174. 6:34

    they're now replacing the plate uh in

  175. 6:36

    the car uh with a new one. And all this

  176. 6:39

    time they don't know that there's

  177. 6:40

    they're being chased. The the the how

  178. 6:42

    they behave in the uh public, how they

  179. 6:45

    behave out there is very different and

  180. 6:46

    it's a lot safer uh in how the

  181. 6:48

    operations are done. They're now going

  182. 6:50

    to go ahead and tint the windows. uh but

  183. 6:52

    this allows the police to like

  184. 6:54

    strategically position themselves in the

  185. 6:56

    most safest way form to intervene at the

  186. 6:59

    right time rather than doing a

  187. 7:00

    high-speed chase outside.

  188. 7:04

    So these are being used across many

  189. 7:06

    different industries

  190. 7:08

    and we are really starting to treat this

  191. 7:11

    as infrastructure that can operate day

  192. 7:13

    in day out nighttime rain sunshine.

  193. 7:16

    We've got a few of these docs deployed

  194. 7:17

    in Alaska, so very cold weathers. Few of

  195. 7:19

    these docks deployed in uh Texas, so

  196. 7:21

    extreme heat. And these need to be

  197. 7:23

    reliable down to 99.9999%

  198. 7:26

    uh where we do our sort of simulation

  199. 7:28

    and testing to be able to prove that.

  200. 7:29

    And today, uh we have about 16 million

  201. 7:33

    people living within 2 mi radius of this

  202. 7:35

    infrastructure that the uh um public

  203. 7:38

    safety, the power companies can kind of

  204. 7:40

    use this technology to be able to

  205. 7:41

    respond to such incidents without having

  206. 7:43

    to travel there.

  207. 7:45

    So, what really happens when this

  208. 7:47

    happens at scale? Can I get a hands up

  209. 7:49

    of people that have flown a drone

  210. 7:50

    before? A couple of hands up. When I

  211. 7:53

    started to fly it, it was like kind It

  212. 7:55

    took me a few hours to like really

  213. 7:56

    figure it out. Then I put on the FPV,

  214. 7:58

    that was even more tricky, but it felt

  215. 8:00

    good to get get that expertise up, but

  216. 8:02

    it's kind of like a skill that you

  217. 8:03

    develop and you develop that skill over

  218. 8:06

    time and you say, "Okay, for each

  219. 8:08

    skilled person, we're going to put them

  220. 8:09

    next to a drone and they're going to

  221. 8:11

    start working." But now you want more of

  222. 8:13

    these. So, uh, police companies,

  223. 8:16

    infrastructure companies need to start

  224. 8:17

    hiring these people more. And at some

  225. 8:19

    stage, this really starts to break down.

  226. 8:20

    The more 911 calls come that come in,

  227. 8:22

    the more alerts that can come in, it

  228. 8:24

    doesn't really scale. So, we kind of

  229. 8:26

    rethinking as to what this means in

  230. 8:28

    terms of this like initial firsterson

  231. 8:30

    view engagement with these systems to

  232. 8:32

    how do we convert this to a more

  233. 8:34

    strategic uh, multi- aent view that you

  234. 8:37

    can kind of command the entire fleet

  235. 8:38

    with an objective in mind without having

  236. 8:40

    to worry about the flight. Let me just

  237. 8:43

    go back and see if that was all working

  238. 8:44

    well. Great. They all landed. I am still

  239. 8:46

    pleased when that happens successfully.

  240. 8:48

    Although it's meant to happen all the

  241. 8:50

    time.

  242. 8:51

    All right, let's go back to this.

  243. 8:55

    Oh,

  244. 8:58

    all right. We're just going to carry on.

  245. 9:02

    So, what does that mean when we start to

  246. 9:04

    launch different things? You saw me

  247. 9:05

    launch them. I was still kind of

  248. 9:07

    thinking about it. Okay, I need to

  249. 9:08

    launch this one, that one, that one. And

  250. 9:11

    even myself in this like uh who's used

  251. 9:14

    to this, I'm going to have some

  252. 9:15

    cognitive challenges where our vision is

  253. 9:16

    to be able to launch uh many many of

  254. 9:18

    them uh in a potentially unsupervised

  255. 9:21

    way. So what sort of commands these

  256. 9:22

    things? How do we get it to like just

  257. 9:24

    hey get out there, launch, search in

  258. 9:26

    this area, find a missing person or look

  259. 9:28

    out for this type of car and hold your

  260. 9:30

    position there.

  261. 9:32

    And in order to do that, we really need

  262. 9:34

    to think about how do we get like really

  263. 9:36

    like the many nines of reliability that

  264. 9:39

    we need in autonomous flight. And that's

  265. 9:42

    where we get an edge in the industry

  266. 9:44

    because at Sky we're sort of controlling

  267. 9:46

    the hardware, the software, the cloud,

  268. 9:48

    the user interface to be able to manage

  269. 9:50

    all that and specifically the autonomy.

  270. 9:52

    uh allowing us to think about how our

  271. 9:54

    underlying vision system should work to

  272. 9:57

    see the environment to behave in the

  273. 9:59

    environment correctly whether it's at

  274. 10:00

    high altitudes whether it's cloudy

  275. 10:02

    whether it's at high speeds how do we

  276. 10:04

    deal in the rain on the bottom left

  277. 10:06

    we're showing how do we navigate in

  278. 10:07

    cities how do we plan large scale and be

  279. 10:10

    able to do that and for anyone that has

  280. 10:12

    worked with any sort of GPS device in

  281. 10:14

    the city even our phones they kind of

  282. 10:16

    suck uh so how do we robustly do that

  283. 10:18

    and how do we also like do tracking when

  284. 10:20

    there's a lot of occlusion

  285. 10:22

    These are the all the different places

  286. 10:24

    where we're thinking about how to train

  287. 10:25

    AI systems quote unquote models. The

  288. 10:28

    word model itself is uh has different

  289. 10:30

    meanings in different places and I'll

  290. 10:32

    discuss a little bit on what that means

  291. 10:33

    for us.

  292. 10:37

    But in order for us to you like really

  293. 10:39

    harness this is we are learning on the

  294. 10:41

    go. This is a learning flywheel that

  295. 10:43

    we're getting out there, we're

  296. 10:44

    collecting data, we're operating, and

  297. 10:46

    we're coming back and doing that so that

  298. 10:48

    each flight we can log the data. Uh kind

  299. 10:50

    of like Google Street View where we need

  300. 10:52

    to think about sanitizing that data,

  301. 10:54

    make sure there's no private information

  302. 10:55

    left there. Uh and make sure we don't

  303. 10:57

    sort of like uh uh the customers know

  304. 11:00

    exactly what they're sharing with us.

  305. 11:01

    But if we can once we do that, we have

  306. 11:03

    access to a huge amounts of data that we

  307. 11:05

    can kind of learn from every single time

  308. 11:07

    we instructed this but the drone did

  309. 11:08

    this. every single time. We thought this

  310. 11:10

    was going to happen, but this happened.

  311. 11:11

    That can come back to our uh learning

  312. 11:14

    agents, our reinforcement learning

  313. 11:15

    ecosystems to be able to retrain,

  314. 11:17

    evaluate, and send it back out there and

  315. 11:19

    kind of continue that flywheel that

  316. 11:21

    allows us to uh have that robust

  317. 11:23

    framework.

  318. 11:25

    And the other added advantage that we

  319. 11:27

    have is it's not just about having

  320. 11:29

    autonomy on the drone. As I mentioned

  321. 11:30

    earlier, we have the luxury now to have

  322. 11:33

    autonomy on the edge device, but also

  323. 11:36

    have autonomy on the cloud. what I was

  324. 11:37

    showing you earlier, all that video

  325. 11:39

    feed, all the telemetry that's going

  326. 11:40

    through a cloud server. We could set up

  327. 11:42

    GPUs and we could set up inference

  328. 11:44

    engines there to be able to have that

  329. 11:46

    heavier lifting, maybe that longerterm

  330. 11:48

    planning there, whereas the immediate

  331. 11:50

    autonomous actions happen on the drone

  332. 11:52

    and kind of always thinking about the

  333. 11:53

    trade-off that we need to make uh to

  334. 11:55

    make that successful.

  335. 11:57

    One thing is true, however, that uh once

  336. 11:59

    you do start thinking about having your

  337. 12:01

    agents from the cloud, this the amount

  338. 12:04

    of data coming to the cloud really

  339. 12:05

    matters. Uh here's us sort of investing

  340. 12:08

    in how we think about enabling the best

  341. 12:11

    um uh video quality coming up through to

  342. 12:14

    the servers uh in uh low lower low sort

  343. 12:17

    of bandwidth areas. Uh being able to

  344. 12:19

    sort of optimize that being able to un

  345. 12:22

    uh um encode that information into

  346. 12:24

    smaller sizes and be able to decode into

  347. 12:26

    something clear that allows us to have

  348. 12:29

    much higher quality exact same sort of

  349. 12:31

    network conditions here. uh and it's the

  350. 12:33

    some of the areas of investments that we

  351. 12:35

    make so that we can have this more

  352. 12:36

    cloud-based infrastructure uh to be able

  353. 12:39

    to manage this at scale.

  354. 12:41

    So once we do that I want to sort of

  355. 12:43

    explore at a high level some of the uh

  356. 12:46

    models that we um uh have in our system

  357. 12:49

    uh that allows us to orchestrate all of

  358. 12:51

    this.

  359. 12:53

    Firstly a model this is a section about

  360. 12:56

    world models. I want to sort of talk

  361. 12:57

    about world models from a context of

  362. 12:59

    maps. Not too dissimilar to how uh Whimo

  363. 13:02

    works. They have a map of the world and

  364. 13:04

    they kind of navigate in that world.

  365. 13:05

    They do local perception, but also think

  366. 13:07

    about global planning. If I want to go

  367. 13:09

    from part A of the city to part B, I

  368. 13:12

    can't just like keep hitting every

  369. 13:13

    building and kind of navigating around

  370. 13:14

    them. I need to think about what's the

  371. 13:15

    optimal path uh along the way. So, we

  372. 13:18

    start off with a lot of prior

  373. 13:19

    information. uh um and we merge that

  374. 13:22

    with uh not just sort of building data,

  375. 13:25

    but maybe there's uh vector data such as

  376. 13:28

    where the power lines are, where the

  377. 13:30

    roads are, if you want different

  378. 13:31

    behavior in these areas. And we think

  379. 13:33

    about how to combine these resources to

  380. 13:36

    ultimately build a map that we can plan

  381. 13:38

    and navigate around. And the drone has

  382. 13:40

    knowledge of this map uh at all times to

  383. 13:42

    be able to go around that.

  384. 13:45

    But like any map, maps can go out of

  385. 13:47

    date. Uh luckily we have so many eyes in

  386. 13:51

    the sky to think about how to maintain

  387. 13:54

    and update these maps along the way. On

  388. 13:56

    the left hand side uh we are rendering

  389. 13:59

    our knowledge of the world in the points

  390. 14:03

    onto our video feed. However, that

  391. 14:06

    doesn't line up perfectly everywhere. Uh

  392. 14:08

    there's some sections here that um if I

  393. 14:11

    sort of zoom out here, there's some

  394. 14:12

    sections here that a new construction

  395. 14:15

    site had set up uh that we did not know

  396. 14:18

    about. Uh however as a drone now starts

  397. 14:20

    to fly and not this is not just one

  398. 14:22

    drone but your fleet of drone they're

  399. 14:24

    now observing these things that we can

  400. 14:25

    feed back into our uh map syncing

  401. 14:28

    process that can come back land give the

  402. 14:30

    data and now once uh in the next

  403. 14:32

    iteration all the drones in the fleet

  404. 14:34

    have this most updated map of the world

  405. 14:36

    that they can uh do all the planning in.

  406. 14:44

    A second type of model is uh perhaps

  407. 14:47

    today a more conventional sort of uh

  408. 14:49

    machine learning uh inference model uh

  409. 14:52

    which is the ability to uh be able to

  410. 14:56

    track understand objects in the scene

  411. 14:58

    but be able to track them be able to

  412. 15:00

    track them behind occlusions. So the uh

  413. 15:03

    this implicit representation behind the

  414. 15:05

    scene is some sort of world

  415. 15:06

    representation of the object that hey

  416. 15:08

    it's gone behind this building and it

  417. 15:09

    might come out on the other side. So I

  418. 15:11

    should navigate myself so I can kind of

  419. 15:13

    follow it there or I should move myself

  420. 15:15

    in a different direction to be able to

  421. 15:17

    do that. Maybe 5 years ago this would be

  422. 15:19

    more done uh in a more conventional way.

  423. 15:21

    You have to like manually think about

  424. 15:23

    how to move. But now you can think about

  425. 15:25

    uh more reinforcement learning style

  426. 15:26

    techniques or more learned end to-end

  427. 15:28

    approaches that can really help out here

  428. 15:30

    without you having to engineer all the

  429. 15:32

    edge cases uh that can go in. And then

  430. 15:35

    obviously like how do we do this

  431. 15:36

    robustly rain, snow, day, night um uh

  432. 15:40

    using um vision only.

  433. 15:44

    One other thing that we're sort of doing

  434. 15:46

    here on the tracking side is we have

  435. 15:47

    some minimal set of tracking that's

  436. 15:49

    happened on device on the edge but we

  437. 15:51

    can do some higher level tracking that

  438. 15:53

    happens on the cloud. So perhaps it can

  439. 15:54

    reason more about your entire map.

  440. 15:56

    Perhaps you can reason more about use

  441. 15:58

    heavier models. Use VLMs uh uh with

  442. 16:01

    lower which have u which don't respond

  443. 16:03

    as quickly uh at a rate of like let's

  444. 16:05

    say 7 to 10 hertz but can give you

  445. 16:08

    feedback at a 1 to two second uh latency

  446. 16:10

    but that's good enough for us to make uh

  447. 16:12

    broad decisions about um where to move.

  448. 16:16

    For a lot of our um infrastructure

  449. 16:19

    customers uh we're doing a lot of

  450. 16:21

    semantic reasoning. So what is there in

  451. 16:23

    the scene? Uh here is an illustration of

  452. 16:25

    us thinking about um uh utility poles

  453. 16:28

    and we want to uh when a instruction

  454. 16:31

    comes in hey go look at this line

  455. 16:33

    there's something gone wrong the drone

  456. 16:34

    needs to go there it needs to understand

  457. 16:36

    the scene then it needs to take actions

  458. 16:37

    within that scene and we're constantly

  459. 16:39

    looking at how to build these primitives

  460. 16:41

    these tools ultimately uh that uh we

  461. 16:44

    today code but uh at any time an agent

  462. 16:47

    can access these tools to better

  463. 16:49

    understand uh what the drone is seeing

  464. 16:50

    and what it could do about

  465. 16:54

    So an example of uh the agentic sort of

  466. 16:57

    system in action is a visual language

  467. 16:59

    model on the top left side. The user

  468. 17:01

    here is typing in look for a white jeep

  469. 17:05

    uh and it's doing a sort of find and

  470. 17:07

    follow. It in it uh accesses a drone API

  471. 17:10

    to command a certain sort of trajectory

  472. 17:12

    that it should take. While that is

  473. 17:14

    happening the detection head is kind of

  474. 17:15

    uh the V uh the VLM is kind of running

  475. 17:18

    here to say hey what's what in the scene

  476. 17:20

    am I looking for? it finds something,

  477. 17:22

    then it has access to the tools that

  478. 17:24

    allow the drone to track and follow. And

  479. 17:26

    that's without any specific coding of

  480. 17:29

    that law rules, but instead uh having a

  481. 17:31

    more sort of agentic uh giving the

  482. 17:33

    agents the all the tools that it needs

  483. 17:35

    to be able to um understand the drone

  484. 17:37

    state and make decisions given the uh

  485. 17:40

    information and the context that's

  486. 17:41

    available there.

  487. 17:45

    And then there's uh always the sort of

  488. 17:47

    long-term vision uh that's often there

  489. 17:49

    in the self-driving community here right

  490. 17:51

    now or any sort of robotic system. What

  491. 17:53

    if uh we could just give it raw sensor

  492. 17:56

    data and out comes uh the perfect uh

  493. 18:00

    results. Uh perhaps that's the actuation

  494. 18:03

    that happens. Perhaps it's where the

  495. 18:04

    drone is pointing. Perhaps it's where

  496. 18:05

    the drone goes. And we're definitely

  497. 18:07

    sort of doing a lot of testing and

  498. 18:08

    triing with reinforcement learning on

  499. 18:10

    what that looks like if we have multiple

  500. 18:13

    uh instantiations of uh this um

  501. 18:15

    behavior. Does it get to the right um

  502. 18:18

    end spectrum? The main consideration

  503. 18:20

    whenever we work with a physical system

  504. 18:23

    is that you're often looking at really

  505. 18:26

    high volumes of reliability as I was

  506. 18:28

    saying many nines of reliability. uh and

  507. 18:31

    the um doing a completely end to-end

  508. 18:34

    system uh does have its challenges in

  509. 18:36

    the sense that the observability of

  510. 18:38

    what's going wrong and the guarantees on

  511. 18:40

    reliability is very difficult today. So

  512. 18:42

    while it's a direction that we're

  513. 18:43

    continuously taking and exploring, it's

  514. 18:44

    kind of figuring out which segments of

  515. 18:46

    your end to-end chunk need to move to a

  516. 18:48

    more uh um like sort of world model

  517. 18:52

    representation of it. Uh, and it's

  518. 18:55

    specifically the things where we always

  519. 18:56

    find ourselves, okay, I need to

  520. 18:58

    handgineer this. I need to code this in

  521. 19:00

    specifically. I need to look at these

  522. 19:01

    rules. Like search and rescue is one of

  523. 19:03

    those things like, oh, go look for these

  524. 19:04

    trees, but if you don't find the trees,

  525. 19:06

    look under here or then turn on thermal

  526. 19:08

    or but then if you didn't find it here,

  527. 19:10

    look there. We're trying to get away

  528. 19:11

    from having to have all these if

  529. 19:13

    statements and the code and these

  530. 19:14

    branching strategies and kind of let the

  531. 19:17

    agent have some highle tools uh to be

  532. 19:19

    able to instruct these very high level

  533. 19:21

    commands uh for the drone.

  534. 19:26

    So um I talked about a quadcopter today,

  535. 19:28

    but we're kind of doing this similar

  536. 19:29

    with a much smaller from form factor

  537. 19:32

    quadcopter and we're now starting to

  538. 19:34

    look at this what this looks like from a

  539. 19:35

    fixed wing as well. all in the world of

  540. 19:37

    infrastructure. Uh so they can be

  541. 19:39

    launched from anywhere, recovered from

  542. 19:40

    anywhere and ultimately the sweet spot

  543. 19:43

    where we can kind of start to very

  544. 19:44

    quickly build on the cloud uh to

  545. 19:46

    orchestrate these things. And the way we

  546. 19:48

    thinking about it is allowing these

  547. 19:50

    systems to have basic APIs of

  548. 19:52

    interactivity that the cloud agents can

  549. 19:54

    come in and uh tap into and make

  550. 19:56

    decisions on and ultimately allow for

  551. 19:59

    very high level thinking when we uh uh

  552. 20:02

    work with these drones.

  553. 20:04

    So like many talks here we are hiring uh

  554. 20:07

    as as I said we have full stack sort of

  555. 20:10

    uh we do the end toend thing hardware

  556. 20:12

    software autonomy full stack front end

  557. 20:14

    back end uh wireless networking

  558. 20:17

    everything all the technologies on our

  559. 20:18

    mobile phones we're now making them fly

  560. 20:21

    um so uh come say hi or look at our

  561. 20:25

    website uh would love to talk more thank