Nebli Review: Private, PIN-Gated Drone Livestreaming Over LTE and Starlink

Most 'enterprise drone platforms' are actually two products fused into one: a command console (mission planning, dispatch, dashboards) plus a proprietary streaming and recording layer that only works if you commit to the whole console. Nebli takes the opposite bet — it is the streaming and recording rail on its own, designed to sit underneath whatever hardware, controller, and operational stack you already have, and pipe a live private view of any flight into a browser tab anywhere in the world. The surface area is deliberately small. A private page, PIN-gated, that opens over LTE, Starlink, or whatever connection the operator is already carrying. Cloud recording of every flight, mirrored to an SD card in the field. A REST API, signed webhooks with a per-attempt delivery log, scoped keys, and an MCP server so an AI client can query flight metadata directly. That is the whole product, and the design constraint is visible in every feature: teams that fly should not have to swap their console, their airframe, or their radios to get modern streaming and archival.

Most drone streaming products were designed for a WiFi ground station and then retrofitted for cellular. Nebli's transport goes the other way — the assumptions are LTE modems, Starlink terminals, and the carrier-grade NAT that most cellular connections sit behind. The technical claim on the homepage is specific: sequence-aware retransmit on both legs, plus a 75-millisecond reorder window so cellular jitter does not read as loss. In plain English, a packet arriving late is not treated the same as a packet arriving never — the difference between a stream that pixelates and stabilises versus one that stalls out entirely on a bad tower handoff. The practical effect matters more than the mechanism: the private share page works across LTE, Starlink, and CGNAT connections without asking the operator to reconfigure their carrier or their router. That is a genuinely useful primitive if you have ever tried to pipe RTSP through a carrier NAT and given up.

The share-page model is where Nebli is easiest to describe and easiest to underestimate. There are no viewer accounts. There is no mobile app to install. The page is PIN-gated, opens in any modern browser, and — critically — the pricing does not scale by viewer count. There is no per-viewer billing model on paid tiers, and Enterprise removes the viewer cap entirely for large-audience deployments. That is the opposite of how most video-streaming SaaS is priced, and it is where the enterprise story starts to make sense. Enterprise is also where the per-drone cap disappears (custom contract, unlimited drones, tenants, teams, and operators), so the total-cost story stops being 'streaming spend scales with team growth' and starts being 'streaming is a fixed line item.' For anyone who has watched their per-viewer or per-seat video bill balloon after a deployment expanded, that alone is worth an evaluation.

The integration surface is the part of Nebli most likely to be overlooked in a quick tour, and it is the part that determines whether the product survives contact with a real ops team. Every flight event can fire a signed webhook with a per-attempt delivery log — meaning your integration engineer can actually see which webhooks retried, which failed, and why, instead of guessing. Scoped API keys and a REST API round out the standard integration story. The MCP server is the unusual addition. Nebli exposes a Model Context Protocol server so AI clients (Claude Desktop, Cursor, any MCP-compatible tool) can query flight metadata directly without a custom wrapper. That is genuinely rare in the drone software category today — most enterprise drone platforms treat AI integration as a marketing bullet, not a wire protocol. For a small ops team that wants to ask an AI 'summarise last week's flights in the north corridor and flag any with sentry detections,' the MCP path removes the middleware. Hardware compatibility is the other quiet strength: DJI, Autel Robotics, PX4, ArduPilot, Parrot, Fotokite, Quantum Systems, and Freefly on the drone side, plus Axis Communications, Hikvision, and Dahua on the fixed-camera side. That breadth is what makes the 'sits underneath your existing stack' pitch credible in practice, and it is already in production with SmartBalloon aerostat-mounted cameras (Altametry) — a live deployment, not a landing-page hypothetical.

You do not have to pick a tier to start. Nebli's Pilot tier is genuinely free — one drone, one team, one operator, real live streaming and telemetry, PIN-gated share page, 7 days of cloud recording up to 50 GB, community support. That is a working production tier for a solo pilot, not a two-week trial that expires with your first real flight. Crew, at $1,490/year (with two months free on annual), lifts the ceiling to 5 drones, 3 teams, 5 operators, 30-day cloud retention up to 500 GB, and email support. Fleet, at $9,990/year, adds Sentry Mode (AI detections with 40 detection-hours per month), 1-year retention up to 5 TB, branded share pages with your logo and colors, 1-year flight history and telemetry capture, 8 drones across 3 tenants, 5 teams, and 25 operators. Enterprise is a custom contract with unlimited drones, unlimited storage, 200 detection-hours per month with no auto-pause, and named on-call support. The honest read on the ladder: Free is generous, Crew is priced for teams that have outgrown Free, and there is a genuine jump from Free to Crew. If you are a solo operator whose flights fit under Pilot's caps, stay there. If you are a team hitting the retention, drone, or seat ceilings, Crew pays for itself the first time you need to pull a flight from three weeks ago that Pilot would already have dropped.