DroneSight, Wingbits and Dronetag: bounded landscape findings

Direct Remote ID networks, receiver platforms and a separate ADS-B contribution analogue.

Research FindingsDraft record

Scope and approach

As of 2026-10-09 America/Los_Angeles, inspect DroneSight (user starting reference), Wingbits and Dronetag using their public home, product, contributor, terms, pricing and technical pages. International scope is provisional because launch geography is unknown. This worker owns only these profiles and their source records; the coordinator owns the study synthesis and review. Company profiles provide the detailed claim and capture trail.

Findings

Company / category Collection and output Participation and access Evidence boundary
DroneSight: direct community Remote ID network ASTM F3411 broadcasts aggregated into mapped activity Selected beta hosts get free loaned receivers and platform access; no cash reward evidenced Beta and coverage are vendor claims; dynamic map data not captured; no public API found in inspected pages.12
Dronetag: receiver/platform and claimed commercial network Remote ID receivers, raw feeds and licensed cloud/local visualization Customers deploy purchased receivers; authenticated APIs documented 3,000+ receivers is vendor installed-scale claim; shared data access and live activity unverified.345
Wingbits: ADS-B contribution analogue Aircraft ADS-B observations, live/history products and documented API Purchased approved stations; variable data-quality/quantity rewards Not evidence of Remote ID or noncooperative drone detection; numeric API plan price not captured.789

Analysis for data gathering

These sources expose three distinct collection arrangements: community-hosted loan receivers, customer-owned receivers with optional software, and incentivized aircraft-data stations. They do not establish that DroneRadar can pay $10 monthly sustainably. Compare source signal, receiver placement, accessible data rights, and participation terms before comparing network counts or detection ranges.

Contradictions and missing evidence

No independent performance tests, audited active-node counts, coverage ground truth, contributor earnings histories or rights to resell network data were obtained. No other companies were researched in this bounded assignment. Initial sandbox DNS capture failures were retained and followed by successful authorized network captures; originals were not overwritten.

Next research questions

  1. Which drone signals and countries matter for the user's initial data collection?
  2. What data can each provider actually license/export, with what retention, sharing defaults and redistribution permissions?
  3. What fraction of installed receivers is online and contributes externally accessible observations?
  4. Can DroneSight demonstrate its beta coverage, and can Dronetag clarify Sensor+ status and Cloud billing interval?
  5. What are Wingbits' rendered plan/hardware prices and realized contributor rewards?

Original URLs and exact captures are in each profile and the footnotes below. All evidence here is official vendor material or direct inspection of published files; operational claims have not been independently established. Researcher capture/content inspection is complete; independent evidence review is recorded in study review.

Sources, provenance and record details
Record type
Research Findings
Status
draft
Generated
by: codex/gpt-6 at: '2026-10-10T04:57:36Z'
Recorded checks
No verification metadata recorded.

Sources

All record metadata
type: Research Findings
title: 'DroneSight, Wingbits and Dronetag: bounded landscape findings'
description: Direct Remote ID networks, receiver platforms and a separate ADS-B contribution
  analogue.
status: draft
generated:
  by: codex/gpt-6
  at: '2026-10-10T04:57:36Z'
sources:
- id: ds-host
  resource: /references/SRC-87920e76e95d/source.md
  title: DroneSight host a receiver
- id: ds-terms
  resource: /references/SRC-726546dae9a6/source.md
  title: DroneSight receiver host terms August 2026
- id: dt-home
  resource: /references/SRC-82ee83970aac/source.md
  title: Dronetag home
- id: dt-scout
  resource: /references/SRC-148960c5f336/source.md
  title: Dronetag Scout
- id: dt-api
  resource: /references/SRC-6a2cbcb96b02/source.md
  title: Dronetag REST API getting started
- id: dt-sub
  resource: /references/SRC-0a9c88d8051c/source.md
  title: Dronetag subscriptions
- id: wb-stations
  resource: /references/SRC-f0fd4a8cc665/source.md
  title: Wingbits stations
- id: wb-schema
  resource: /references/SRC-71ec93c01119/source.md
  title: Wingbits OpenAPI schema
- id: wb-pricing
  resource: /references/SRC-b80b4a009bdc/source.md
  title: Wingbits pricing