Skip to content
FPV DB logo

FPV DB

Searchable database of FPV drone quads, motors, batteries, props and cameras, with calculators for flight time, thrust and battery current.

Actively maintained

FPV DB: data, price, alternatives
At a glancechecked Oct 29, 2026

not read yet

Use

For
FPV drone builders choosing components and checking build specs before flying
Activity
Actively maintainedsite updated 5 days ago
Used for
  • check thrust-to-weight ratio of a planned build
  • verify a Betaflight or INAV diff against the target firmware release
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 29, 2026
  • MCP servercom.fpv-db/fpv-dbverified in the MCP registry
  • Stateanswers, 5 toolschecked 2026-10-29
  • Address to connectfpv-db.com/mcp

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Databy use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare FPV DB with

Pick up to two.

All 10 alternatives to FPV DB →

All Data tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use FPV DB for?

Sign in to leave a note
Questions this page answers
  • What is FPV DB?

    Searchable database of FPV drone quads, motors, batteries, props and cameras, with calculators for flight time, thrust and battery current. It is listed in the Atlas under Data.

  • Who is FPV DB for?

    FPV drone builders choosing components and checking build specs before flying

  • Is FPV DB still maintained?

    Actively maintained: site updated 5 days ago.

  • What are alternatives to FPV DB?

    In Data, by use: Startuphub, Rephonic, Saber, The Wheel Atlas, Radar CNPJ.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk