Self-Hosted vs Managed Drone Streaming: Which Tier Makes Sense?

The #1 question on the first call. Here's the framework, cost breakdown, and the three questions that actually determine which tier fits your agency.

Most agencies coming to EyesOn ask the same thing on the first call: "Should we self-host or let you manage it?" The honest answer is: it depends on three factors — IT capacity, data sovereignty policy, and how much maintenance burden your team can absorb. The money is usually the last question, not the first.

What each tier actually is

Self-hosted

You run the EyesOn server on hardware you control. That could be a Synology NAS at the station, a $300 mini-PC at the department HQ, a Linux VM in the agency data center, or a $10/mo VPS. You get the software, the install script, the documentation, and community or email support (depending on tier). You handle upgrades, backups, and uptime.

Managed

BarnardHQ runs EyesOn for you on dedicated hardware. You get a custom domain (e.g., eyeson.youragency.gov), SSL, monitoring, automated backups, automatic updates, and a 4-hour response SLA. You get an admin URL, credentials, and the ability to generate streams and guest links. Everything else is our problem.

Cost breakdown

On paper, self-hosted is cheaper by roughly 3x. But that math assumes your IT time is free, which it isn't, and that nothing ever breaks, which it will.

The three questions that actually decide it

1. Do you have IT capacity?

Be honest. "IT capacity" doesn't mean you have someone technical on the team — it means you have someone who will reliably apply security patches, respond when monitoring alerts, and be available on weekends when a bad update breaks something. For most small departments and volunteer SAR teams, the answer is no. That's not a failing; it's a resource constraint.

If you don't have dedicated IT capacity, the realistic cost of self-hosted is not $1,800/year. It's $1,800/year plus a $30,000/year risk that the platform is offline during the one call you actually need it.

2. Does your policy require on-premise?

Some agencies have written policy that operational video must remain on agency-controlled infrastructure. If that applies to you, self-hosted isn't a choice — it's a requirement. EyesOn's self-hosted tiers are specifically built for this case: video never touches our infrastructure unless you enable TURN relay for mobile viewers (and even then, TURN sees encrypted SRTP, not decoded video).

If your policy doesn't require on-premise, this is not a real constraint. Managed is fine.

3. How much of your team's time are you willing to spend on infrastructure?

Self-hosted Professional tier, well-run, costs about 2–4 hours of admin time per month on average. Mostly unremarkable — apply an update, check that backups are running, glance at logs. But every 4–6 months something will need attention for a half-day: major version upgrade, certificate renewal issue, hardware replacement. If those hours come out of your available operational time, factor that in.

The decision framework

• Self-hosted Personal ($39/mo): single-drone agency with technical capacity, validating the workflow. Fine for proof of concept. Not for primary ops.
• Self-hosted Professional ($89/mo): the sweet spot for agencies with basic IT capacity. Most small PDs, rural fire districts, and mid-sized SAR teams land here.
• Self-hosted Enterprise ($209/mo): agencies with real IT capacity and a policy-driven reason for on-premise. Unlimited streams and viewers, fleet management, Cloudflare Tunnel support, priority support.
• Managed ($499/mo): agencies without IT capacity. Volunteer SAR teams. Small departments that want the capability without the maintenance burden. Regional coordinators who need it to "just work."

Common mistake: choosing self-hosted because it looks cheaper

We regularly talk to departments that chose a cheaper self-hosted tier initially and migrated to Managed twelve months later. The pattern is always the same: the IT person who championed the original deploy got promoted, retired, or moved to another agency, and nobody inherited the operational knowledge. The platform drifted, then failed at a bad moment.

If you don't have redundancy in your IT function, Managed is not a premium tier — it's the appropriate tier.

Common mistake: choosing Managed when policy requires on-premise

The reverse also happens. A department signs up for Managed, ships an incident, and then has a public-records-request conversation where counsel asks "where is this video physically stored?" Sometimes the answer is fine. Sometimes it isn't. Get that conversation done before the deploy, not after.

The middle path: start Managed, migrate later

A workable approach for agencies that want to eventually self-host but aren't ready yet: start on Managed, build the workflow and train the team, then migrate to self-hosted Professional or Enterprise once your IT capacity is in place. We support that migration. You don't lose anything by starting Managed and moving on-premise later.

Related

• EyesOn — full product page with tier comparison
• Drones for Public Safety — pillar guide
• Public Safety Drone Program Startup Checklist