Skydio
Each of these is a real decision Skydio is working through, written so you can make the call yourself — incomplete information, someone who pushes back, no answer key.
Skydio makes drones, with tens of thousands operating all over the world. Its new winged platform, F10, introduces a new generation of autonomous systems, enabling longer missions and higher speeds. Skydio offers the Skydio Simulator, a high-fidelity, real-time digital replica of the physical world used both by customers and by Skydio's autonomy engineers. It has an on-prem product line offering air-gapped and self-hosted deployments. Its public safety work includes multi-site, citywide Drone as First Responder deployments, statewide highway and transit programs, and federal work through DOJ, alongside a Canadian public safety business. Skydio sells to security buyers including data centers, departments of corrections, military installations, corporate campuses, healthcare, manufacturing, and executive protection, and site security is the fastest-growing segment of its commercial business, where it is building a new market category in autonomous site security. Skydio translates FedRAMP, SOC 2, Texas RAMP, ISO 27001, and CJIS requirements into technical controls.
Your first one is free. No card.
62 live right now.
The rest
Settle if a static check is enough for F10 before tooling locks
F10 pilot units need a repeatable way to prove ground interfaces survive repeated handling. You must weigh a fast pilot-build path against evidence that the interfaces will hold up in fleet operations.
Choose a release path for the X10 Dock before build allocation
Some completed aircraft lose RF range only after final enclosure assembly. You have to weigh deployment allocation against a containment path that can be proven unit by unit.
Stabilize harness seating while ground-station rework grows
Ground stations are failing first test after harness installation, then passing only after reseating. You must weigh faster assembly against a test method that still catches real electrical faults.
Trace mission failures while on-call evidence stays fragmented
Planned missions are failing even when fleet health appears normal. You must decide what AI can rank safely and what engineers must confirm before a fix ships.
Link highway calls to missions without adding dispatcher work
Dispatch supervisors cannot reliably connect dock missions to the highway incidents that prompted them. You have to weigh usable proof of operational value against disruption to live dispatch work.
Set evidence links before six docks go live
Some dock missions reach dispatch but do not create a usable evidence record for investigators. You must weigh an on-time remote-operations launch against an evidence path the agency can defend.
Map CAD locations before dispatchers abandon the dock workflow
Highway markers and facility coordinates are sending dock missions to the wrong place. You must weigh fast dispatch integration against preserving the incident record operators need to review.
Route node-pressure alerts so severity is set within 15 minutes
EKS node-pressure alerts force on-call engineers to reconstruct AWS, Kubernetes, and Terraform context before assigning severity. You must decide what AI can assemble and what an engineer must verify before acting.
Set site access without exposing another facility’s mission records
Local supervisors cannot independently review the missions and detections at their own facilities without broader fleet access. You have to weigh fast site oversight against durable separation of operational records.
Choose regional controls while mission video demand climbs
Mission video slows when simultaneous incidents draw traffic through the existing regional path. You must weigh a hard-to-reverse cutover against the evidence needed to protect restricted operational data.
Restore fleet health after SSO refreshes empty the view
Authorized operators at three sites can sign in but lose their fleet view after an SSO refresh. You must restore access without turning a narrow permission failure into broader data exposure.
Settle what must be true before leaders approve the next sites
One dock is operating, but the next locations lack a shared path for daily remote operations. You have to weigh local site fit against a readiness bar that can support expansion.
Decide the rollout for eight sites until approval evidence is verified
Eight dock sites are booked, but the new approval path leaves readiness evidence uneven. You have to weigh coverage dates against a rollout that can be verified and sustained.
Settle ownership of dock checks before the next six sites activate
Six new dock sites are approaching activation with inconsistent answers about maintenance and support ownership. You have to weigh local operating differences against a handoff that Support and customer operators can run repeatedly.
Find where uploads degrade without disturbing real-time autonomy
Completed missions are returning without timely video or telemetry records at several dock sites. You must weigh diagnostic coverage against aircraft reliability, serviceability, and a manufacturable pilot build.
Choose a thermal fix or duty limit once the cutover releases parts
Camera compute thermal shutdowns are interrupting repeat dock missions at hot-weather sites. You must weigh a production change against a mission restriction while proving the real thermal margin.
Catch harness faults before docks leave the final-test station
Newly installed docks intermittently lose charging-state updates after passing final test. You have to weigh fault capture against the line time that keeps docks moving.
Rank detections for review without hiding the evidence operators need
Operators are spending review time on routine clips while relevant detections are buried across multi-site flights. You have to weigh faster triage against preserving the evidence operators need to trust the queue.
Commit the night-video release without weakening detection evidence
Night operators are receiving delayed video and inconsistent detection timing across active dock missions. You have to weigh a fleet-wide latency fix against evidence that is costly to verify and hard to undo.
Fix clip selection so glare stops crowding out rare scenes
Glare-heavy clips are crowding annotation and hiding rare operational scenes. You have to protect recall while making each annotation hour count.
Rank renewal risk before missed commitments reach the customer
Renewal calls are starting without a shared view of stalled usage, tickets, and commitments. You must weigh earlier risk signals against the cost of treating an operational pause as a renewal problem.
Group dock feedback while keeping every source visible
Repeat-visit signals are being split across field notes and bug reports, so recurring dock failures stay hard to size. You must weigh faster synthesis against the evidence Product Managers need to trust a theme.
Build a launch record for dock missions without implying approval
Reviewers cannot reconstruct a single account for completed dock missions without searching separate records. You must weigh a useful accountability record against implying that the platform authorizes flights.
Commit to an air-gapped cutover without splitting mission records
Active X10 Dock sites could lose one accountable view of mission history during the fixed cutover window. You must weigh operational continuity against the security boundary the new deployment requires.
Clarify dock closure when repeat visits keep returning
Closed X10 Dock repairs are producing repeat visits because recovery evidence and recurring faults are not consistently visible. You have to weigh a faster closeout flow against the proof operators need before trusting the next mission.
Route node alerts without hiding the evidence engineers need
EKS node-pressure alerts are consuming time while engineers reconstruct severity context across several systems. You must weigh faster routing against evidence an on-call engineer can trust.
Surface dock patterns without losing the evidence behind them
X10 Dock feedback describes recurring deployment friction, but Product Managers cannot quickly see which issues truly repeat. You have to weigh faster synthesis against reviewable evidence and restricted customer context.
Match invoice exceptions before close obscures material costs
Invoice exceptions are forcing reviewers to rebuild evidence across NetSuite and Coupa during close. You must decide what AI can prepare safely and what every reviewer must verify.
Turn alarms into dock patrols without losing GSOC context
Three security pursuits want event-triggered patrols, but their alarm signals carry incompatible context. You have to weigh one customer’s tailored workflow against a minimum pattern the next site can reuse.
Set dock rules while overlapping calls reach activation
Nine of 26 overlap rehearsals flagged duplicate dock assignments, with only four confirmed so far. You have to weigh dispatch speed against a coordination rule that can survive public activation and strict review.
Route dock video into the VMS before the trial closes
Only 11 of 34 on-time dock missions reached the watch commander’s VMS in time. You have to weigh a reusable streaming handoff against the customer integrator’s one-window VMS workaround.
Ship capacity guidance in X10 Dock without promising coverage
Customers are changing multi-drone mission plans after cellular capacity fails during active operations. You must weigh useful planning guidance against overpromising what carrier networks will deliver.
Decide whether to freeze the On-Prem release in 28 days or delay
Three runbooks describe incompatible responses to an urgent vulnerability in the air-gapped release candidate. You must weigh a fixed exercise date against an update path that has not yet been proven.
Fix the status of finished charges without a firmware rollback
Eighteen percent of completed charge cycles stay pending for over 20 minutes. You must weigh a focused status correction against losing newly released dock diagnostics in a rollback.
Settle one baseline for response time while agency definitions differ
Eight multi-Dock agencies are asking for response-time and operator-capacity evidence, yet none shares a common value baseline. You must weigh a reusable review service against each agency’s distinct operational definitions and policy constraints.
Choose a retention limit for Dock video while command still wants more
Fourteen possible duplicate video paths appeared in 62 mission records, but only five are verified so far. You must weigh command’s need for reviewable footage against policy’s need for strict retention before the city locks its operating plan.
Restore dispatch launches while one training window remains
Only 54% of dispatch-originated missions are completing, versus 91% of manually created missions. You must weigh a faster customer workflow change against a CAD change that could remove the handoff problem at its source.
Stand up local service for Dock sites instead of one-off calls
A multi-site Dock deployment has no predictable local path for maintenance, parts, or site access. You have to weigh fast mission recovery against vendor controls and the production demand for the same spares.
Decide on containment for battery lots before 486 X10 units ship
Traceability evidence conflicts across 486 battery assemblies near shipment and final build. You have to weigh delivery continuity against the containment level needed to protect field readiness.
Fix the backlog in X10 inspection without adding overtime
The final-inspection queue has reached 29 units while first-pass yield sits at 91%. You have to weigh near-term build-plan recovery against the training discipline that keeps defects from returning.
Package mission context without broadening downstream access
Operations managers spend about 12 minutes assembling each selected mission handoff from separate surfaces. You must weigh faster dispatch context against tightly scoped sharing of mission information.
Decide the camera update before fleet recovery becomes necessary
Seventeen camera resets have appeared in 4,200 flight hours, but low-light timing evidence conflicts across validation environments. You must weigh continued mission interruptions against committing a fleet-wide update that is costly to reverse.
Tune live video before cellular missions keep pausing
Cellular video latency has climbed to 1.8 seconds, and operators are pausing active missions. You must weigh scene detail against the timely view needed for remote supervision.
Catch gaps in mission setup without implying flight authorization
Pilot sites are finding missing mission details at launch after planning looked complete. You have to weigh earlier guidance against making a software result look like flight authorization.
Fix how healthy docks are marked unavailable before the next window
Healthy docks are being marked unavailable 8.4% of the time, forcing avoidable mission reroutes. You must weigh a fast rollback against a durable correction to shared dock state.
Choose between a link fix and an ingestion rollback
Seven percent of completed dock missions have telemetry but no linked video asset. You must weigh a cloud-side record correction against an ingestion rollback in one release window.
Price F10 fleets while tooling costs remain uncertain
Three proposed F10 fleet configurations cannot yet be compared on material, tooling, and cash exposure. You must weigh a usable planning model against assumptions that could misprice a long-lived deployment.
Decide which lots to release or quarantine before month-end close locks
Conflicted lot records put material value and a scheduled production build at risk. You must weigh customer delivery against traceable inventory and a defensible close.
Align cash with build readiness while supplier terms diverge
Several components are being held because the cash forecast uses payment terms that approved purchase orders no longer reflect. You must weigh a fast correction against the evidence needed to release material confidently.
Prove the staffing value of dock flights within 90 days
Pilot agencies are flying from their first docks, yet command staff cannot see whether staffing changed. You must weigh a repeatable value programme against each agency’s different dispatch reality.
Prove the staffing case before four docks enter the renewal
The first dock is flying more missions, yet leaders cannot agree whether staffing hours have fallen. You must weigh a fast expansion case against operational evidence the agency can defend.
Rebuild CAD launches before the quarterly review tests the staffing case
Only 42% of eligible calls enter through the CAD-to-launch workflow, leaving pilots to handle direct dispatch requests. You have to weigh a fast adoption reset against the agency’s established dispatch habits.
Rank missions by intervention risk before operators lose the window
Operators are watching routine flights while intervention-needed missions emerge too late. You must weigh earlier attention signals against false alarms and embedded limits.
Choose a tracking package before the exercise locks the release
Tracked vehicles disappear during video dips in concurrent missions, even when aircraft stay on route. You must weigh mission continuity against a release decision that cannot be cheaply undone.
Catch vehicles in glare without draining mission power
Glare-heavy substation missions detect only 76% of labeled vehicles, despite normal video and flight data. You must weigh stronger visual recall against the latency and power limits that keep missions usable.
Trace mission settings without exposing restricted fleet details
Fleet administrators cannot reliably reconstruct which configuration governed a completed docked mission. You must weigh a usable evidence trail against least-privilege access to sensitive fleet settings.
Commit access boundaries before the air-gapped copy
Four privileged access paths cannot yet be reconciled between machine summaries and manual evidence. You have to weigh a fixed operating date against access controls that will be costly to unwind.
Restore remote access after the node rollout
Remote Flight Deck authentication fell to 96.9% after one EKS node rollout. You have to weigh a fast rollback against the risk of disrupting sessions that still work.
Settle which sites are ready for remote work while waivers differ
Six utility sites are preparing for shared remote operations, but their handoff requirements do not match. You must weigh a reusable launch path against the controls each site needs to operate safely.
Commit the utility rollout despite nine unstable substations
Nine of 24 substations show intermittent remote-operation connectivity 21 days before storm season. You have to weigh coverage urgency against site work that becomes expensive to reverse.
Settle go or no-go for three county sites before Friday
Three county sites have conflicting power and LTE evidence days before dock shipment. You have to protect the training date without treating an incomplete record as proof.