EyesOn · 2026-05-05

Why Drone Operations Teams Are the New Managed IT Services Client Nobody Talks About

The IT manager at a mid-size public safety agency in Oregon has a problem that didn't exist five years ago. He's responsible for the network, the servers, the endpoints — and now, apparently, the drone streaming infrastructure that the aerial unit deployed last quarter without looping in his department. The drone vendor sold the agency on a cloud-based platform. Nobody asked IT. Nobody documented the data flows. Nobody asked where the video was going when it left the drone.

This is the new managed IT services conversation. And most MSPs are completely unprepared for it.

What Drone Infrastructure Actually Looks Like From the IT Side

When an organization deploys drones operationally — not for a one-off shoot, but for recurring public safety, security, emergency response, or inspection work — they are deploying networked infrastructure. The drone is an endpoint. The controller is a client device. The video stream is data in transit. The platform that receives, displays, and stores that stream is a server.

Most organizations discover this after the fact. The drone program starts in the field operations department. IT finds out when someone files a ticket because the streaming platform won't load on the agency network, or when a security audit flags an unregistered cloud service receiving sensitive aerial video.

Here's what that infrastructure typically includes:

When that infrastructure is cloud-dependent — meaning video routes through a third-party server outside the organization's control — the IT department has a legitimate data governance problem on their hands. Public safety video, thermal imagery of private property, real-time positional data of active operations. All of it transiting infrastructure the organization doesn't own, can't audit, and can't pull the plug on without losing the whole service.

The Vendor Lock-In Pattern That Should Concern Every IT Manager

Cloud-based drone streaming platforms follow a familiar SaaS playbook. The agency signs up. The workflow gets embedded into operations. Pilots build muscle memory around the interface. Six months later, the vendor reprices. Or the vendor gets acquired. Or the vendor sunsets the tier the agency is on and bumps them to a more expensive plan.

DroneSense runs $1,500 to $5,000 per year per drone. FlytBase meters by viewer-minute, meaning a busy incident with multiple stakeholders watching a live feed generates billing the agency didn't plan for. LiveU requires $10,000-plus in hardware upfront.

The lock-in isn't just financial. It's operational. When the streaming platform is cloud-hosted by the vendor, the organization's ability to operate depends entirely on that vendor's uptime, their data center's connectivity, their decision not to have an outage at 2:00 AM during an active search. IT managers understand this risk profile — they deal with it in every other software category. But drone platforms often fly under the radar because the procurement happened outside IT's approval chain.

What Self-Hosted Drone Streaming Looks Like as an IT Problem

EyesOn, built by BarnardHQ out of Eugene, Oregon, is a self-hosted drone streaming platform. It runs on your server. Video never touches a third-party cloud. Access control, retention policy, network routing — all of it lives inside the organization's existing infrastructure perimeter.

For an IT manager, this changes the conversation entirely.

Instead of auditing a vendor's data processing agreement and hoping it covers your use case, you're looking at a Docker container running on hardware you already manage. Instead of worrying about what happens to your video data when your subscription lapses, you're looking at software that keeps running regardless of subscription status — no kill switch, no sudden service termination.

The EyesOn architecture from an IT perspective:

The Managed Tier and What It Actually Covers

For organizations that want self-hosted architecture without maintaining the server themselves, EyesOn's Managed tier ($999 setup, $499 per month) provides hosting managed by BarnardHQ directly. This is a meaningful option for smaller public safety agencies or county operations departments that have the operational need but don't have the IT staff to stand up and maintain a Docker deployment.

The Managed tier includes a dedicated support relationship, SLA coverage, and direct access to the person who built the software. Not a support ticket queue. Not a Tier 1 helpdesk in a different time zone. Bill Barnard, who wrote the code, is also the person who answers the phone.

For IT managers who've dealt with enterprise software vendors where getting a human with actual technical authority on the phone requires escalation through three tiers of support, this is a structural difference, not a marketing claim.

The other tiers scale down from there: - Personal: $149 setup, $39 per month — one server, community support, unlimited drones and viewers - Professional: $299 setup, $89 per month — up to five servers, email support - Enterprise: $499 setup, $209 per month — unlimited servers, priority support, custom branding option

First-year total cost for the Personal tier is $617. Compare that against $1,500 to $5,000 per drone per year for cloud platforms, and the math is straightforward for any organization running more than one aircraft.

Why Managed IT Services Providers Should Be Paying Attention

MSPs serving local government, public safety, utilities, or industrial clients are already managing infrastructure for organizations that operate drones or are actively considering drone programs. The drone streaming infrastructure question is coming. The client is going to ask about it — or, more likely, the client is already running a cloud-based streaming platform that their IT vendor doesn't know about.

There are two ways for an MSP to handle this.

The first is reactive: wait for the ticket, clean up the governance mess, help the client evaluate vendors after the fact. This is fine. It's also the same position MSPs were in fifteen years ago with shadow IT cloud storage before they started proactively auditing for it.

The second is proactive: get ahead of the drone infrastructure question now, understand what self-hosted streaming actually requires to deploy and maintain, and be the partner who brings the client a compliant architecture before the problem surfaces in an audit.

EyesOn is MIT licensed and open source. An MSP can stand up a test deployment, understand the stack, and validate it against client security requirements before recommending it. The Docker deployment path is designed for exactly this kind of technical evaluation.

What the IT Deployment Checklist Actually Looks Like

For an IT department or MSP evaluating EyesOn for a client, the practical checklist includes:

**Server requirements:** A Linux server with Docker support, adequate CPU for WebRTC transcoding, sufficient storage for recorded video depending on retention policy. Exact requirements depend on concurrent stream count and resolution.

**Network configuration:** Inbound WebRTC traffic from drone controllers (cellular or on-site Wi-Fi), outbound to viewer browsers. Port configuration is standard and documented. No proprietary protocol dependencies.

**Android companion app:** Deployed on the DJI RC Pro or compatible controller. Captures the full screen output including OSD overlay — altitude, speed, gimbal position, thermal palette. This data rides in the video stream, meaning viewers see exactly what the pilot sees, real-time.

**Access control:** Authentication managed at the server level. You define who can view live streams, who can access recordings, who can administer the platform. No vendor-controlled permission system.

**Backup and retention:** Standard IT backup applies. Video is stored as files on your server. Your retention policy, your storage, your call.

**Disaster recovery:** Because the software keeps running if the subscription lapses, a lapsed payment during a budget freeze doesn't ground your operations. The platform continues functioning. This is a direct design decision — no operational hostage-taking.

The Practical Next Step for IT Managers and MSPs

If your organization or a client is currently running drone operations through a cloud-based platform, pull the vendor agreement and find the data processing addendum. Identify where the video is being stored, in which jurisdiction, under what retention policy, and what happens to that data if the contract ends. Then ask whether the operational use case — public safety video, thermal imagery, sensitive site security — is appropriate for that data governance posture.

If the answer is no, or even if the answer is uncertain, the self-hosted alternative exists and is deployable today. EyesOn is live at eyeson.barnardhq.com. The documentation covers the Docker deployment path in detail. The Personal tier at $617 for the first year gives any IT department a practical way to validate the platform against their specific requirements before committing to organizational deployment.

Drone infrastructure is IT infrastructure. The organizations that figure that out now will have cleaner audits, better operational security, and significantly lower streaming costs than the ones that sort it out after a vendor repricing forces the conversation.

← Back to all posts