BarnardHQ · 2026-04-29

What My IT Background Actually Built Into BarnardHQ (And Why It Shows Up in the Field)

Before the drones, there were servers. Before the flight logs, there were network diagrams. Before 614 logged flights across the Willamette Valley and Coast Range, there were years of IT infrastructure work — building systems that had to stay up, stay secure, and stay accountable whether anyone was watching or not.

That background didn't disappear when I started flying commercially. It got embedded into how BarnardHQ operates. And the more I talk to other operators, the more I realize that the gap between a drone pilot and a drone operation isn't flight hours — it's the managed systems thinking that runs underneath everything else.

This post is about that gap, and what filling it actually looks like in practice.

What "Managed IT Services" Actually Means for a Drone Operation

Managed IT is a term that usually conjures images of help desks, patch Tuesday, and remote monitoring dashboards for office networks. And yes, that's part of it. But the core principle behind managed IT is something more fundamental: your systems don't degrade silently, data doesn't walk out the door, and when something goes wrong at 2 AM, you already have a protocol.

That principle applies directly to drone operations — and most operators are running without it.

The Hidden Infrastructure of a Commercial Drone Business

Here's what's running at BarnardHQ that most clients never see:

**DroneOps Command** — a self-hosted flight logging and operations management platform I built from the ground up. It tracks every flight: timestamp, aircraft, location, duration, weather conditions, purpose. 614 flights, 9,164 miles, 148+ hours logged with full metadata. This isn't a spreadsheet. It's a queryable database that answers questions like "what was the battery cycle count on the M30T during the March 2025 SAR operation" or "how many hours has the Matrice 4TD accumulated since acquisition."

**DroneOps Sync** — handles data pipeline management between flight systems and storage. Raw footage, processed deliverables, and mission reports move through defined workflows, not manual drag-and-drop.

**EyesOn** — a self-hosted drone streaming platform with sub-second WebRTC latency. Built specifically because the commercial alternatives either charge per viewer-minute (FlytBase), require $3,000+ hardware per unit (Blu-Link), or cost $1,500–5,000 per drone annually (DroneSense). EyesOn runs on your own server. Your data doesn't touch a third-party cloud. If the subscription lapses, the software keeps running.

**Local AI reporting via Ollama + Mistral 7B** — post-mission analysis that runs on-premises. No data leaves the server. This matters when the deliverable involves sensitive inspection footage, private property, or law enforcement-coordinated SAR imagery.

**Live airspace awareness via OpenSky Network** — ADS-B traffic integration, not just an app that pings the FAA database. Operational airspace awareness that's current, not cached.

This is the managed IT layer under a drone operation. None of it is visible from the outside. All of it affects what clients actually receive.

Why This Matters for Clients Who Hire BarnardHQ

A client hiring BarnardHQ for a commercial inspection, a SAR support deployment, or a security patrol isn't hiring just a pilot. They're hiring an operation that runs with the same discipline that managed IT demands of enterprise infrastructure.

Let me make that concrete.

Data Accountability

When Lane County Sheriff's Office shared last-known-position coordinates and cell ping data during the Jonathan House search in March 2025, that information went into a managed operations workflow — not a personal email thread, not a phone screenshot. The 6 hours of M30T thermal and optical footage from 800+ acres of Coast Range foothills was logged, tagged, and preserved for post-flight secondary review. LCSO got the data they needed in a form they could actually use.

That's not a drone capability. That's a data management discipline.

Operational Continuity

The Beau recovery in Springfield — a 1 AM emergency callout after a vehicle accident, a panicked Doberman somewhere in dense Oregon woods — worked partly because the gear was ready. Batteries charged. M30T preflighted. CZI IR3 infrared zoom dome light staged and tested. That readiness doesn't happen by accident. It's the result of a maintenance and readiness protocol that runs continuously, not just before scheduled jobs.

Managed IT people recognize this immediately: you don't patch the server the night before the audit. You run continuous monitoring so the audit is a non-event.

Security Operations With Chain of Custody

The Yard Patrol incident — thermal acquisition of a subject attempting forced entry on a locked trailer at 2:30 AM — generated footage that became an operational record. The strobe activation, loudspeaker deployment, and suspect departure were logged as a timestamped incident report, not just a story the operator tells at conferences. If that footage were ever needed for an insurance claim or law enforcement follow-up, it exists in a retrievable, documented form.

That's evidence chain of custody thinking applied to drone operations. It comes from IT security background, not flight school.

The Open Source Component: DroneOps Suite

Everything I've described — DroneOps Command, DroneOps Sync, EyesOn — is open source, MIT licensed. The code is available. Other operators can run it. The reason I built it in the open isn't altruism; it's because the managed drone software market is either vendor-locked, overpriced for independent operators, or designed for enterprise fleets with dedicated IT departments.

A one-pilot operation running a DJI Mini 5 Pro and a Mavic 3 Pro out of a truck in rural Oregon doesn't need $5,000/year in SaaS subscriptions to have professional data infrastructure. They need something they can deploy on a $50/month VPS, own outright, and modify when their workflow changes.

EyesOn's pricing structure reflects this: Solo tier is $149 setup plus $39/month — $617 in year one for unlimited drones and unlimited viewers. That's less than what DroneSense charges per single aircraft per year.

The open-source release is also how I pressure-test the work. If the code has to survive scrutiny from other operators and developers, it has to be good.

What Managed IT Discipline Fixes in a Drone Operation

If you're running a commercial drone operation and any of the following is true, you're running without managed IT infrastructure:

None of these are drone problems. They're IT problems. And they're solvable with the same discipline that managed IT has applied to business infrastructure for the last 30 years.

What I'd Prioritize If Starting From Scratch

For an independent operator building out the IT layer of their business, in rough order of impact:

1. **Centralized flight logging** — something queryable, not a spreadsheet. At minimum, timestamp, aircraft, location, battery cycles, weather, and mission type per flight. 2. **Segregated storage** — client deliverables on their own volume, isolated from everything else, with access logs. 3. **Documented maintenance records** — propeller replacements, battery discharge cycles, motor hours, firmware versions at time of flight. 4. **Streaming that you control** — self-hosted or at minimum a platform where your data stays yours. EyesOn exists specifically for this. 5. **Incident reporting workflow** — a form or template you fill out after anything unusual happens, filed and retained.

None of this requires a software engineering background. It requires the discipline to build it before you need it.

The Takeaway

BarnardHQ is a one-man drone operation. But it runs with the infrastructure discipline of an organization that takes data, accountability, and operational continuity seriously — because that background is where it came from.

If you're a commercial operator looking at the DroneOps suite, EyesOn is live and available with full documentation at the Solo tier. If you're a business evaluating drone service providers and want to understand how your data gets handled from flight to delivery, that's a conversation worth having before you hire anyone.

The tools are at BarnardHQ.com. The code is open. The flight logs are real.

← Back to all posts