Documentation

Hover, in plain language.

Five short pages. What Hover is, what to expect when you bring it into your operation, how it handles security, and the questions public-safety teams ask first.

Hover is a managed drone-relay platform. We carry live video and MAVLink between a drone in the field and the people who need to see and respond to it — command staff, dispatch, mutual-aid partners, public-information officers — across the cellular and satellite links agencies actually have.

This documentation is for evaluators. It's not a deployment runbook (Anarion handles deployment for managed customers) and it's not field-operator training (those materials ship with the deployment). Read these pages in order, or skip to whichever question you walked in with.

01 / Architecture

How it works

Three components, one stream of video, one stream of telemetry, between the drone and the room. Why it survives cellular reality.

02 / Deployment

What to expect when deploying

A managed rollout. What we provide, what your team handles in the field, and the rough timeline.

03 / Security

Security and data handling

Per-session credentials, transport, what's encrypted, what's logged, what we keep, what we don't.

04 / FAQ

Common questions

CGNAT, drone compatibility, recording and evidence, compliance, and how pricing actually works.

Where to go next

If you're a public-safety operator evaluating drone-streaming options, start with How it works and then the FAQ. If you've already decided Hover is a fit and you're looking at procurement, Deployment and Security are the two pages your IT and legal teams will want.

If you're a procurement or legal reader, the Security page covers the questions we get most often: how credentials work, what data we hold, what we log, and what we will and won't sign in an MSA.

Questions a page didn't answer?

hello@hoverfeed.com