Open DroneLog

Open-source drone flight analysis, honestly reviewed. No marketing fluff, just what you get when you run your own flight data dashboard.

TL;DR

• What it is: Free, open-source drone flight log analyzer for DJI and Litchi pilots — desktop app or Docker-deployable web dashboard, all data stays on your hardware [README][homepage].
• Who it’s for: Drone pilots (hobbyist and commercial) who want to analyze telemetry, replay flights in 3D, and track battery health without handing their GPS coordinates to a commercial cloud [README].
• Cost savings: Commercial alternatives like Airdata UAV and DroneLogbook run subscription models. Open DroneLog is free forever — no tiers, no paywalls, no usage limits [homepage].
• Key strength: Local-first storage backed by DuckDB — genuinely fast analytics, 3D flight replay, and PDF report generation for regulatory compliance, all running entirely on your machine [README].
• Key weakness: AGPL-3.0 license (not MIT), single-developer project (1,230 GitHub stars as of this review), and DJI’s own format parsing requires their Developer API key for some log types, adding a setup hurdle [README].

---

What is Open DroneLog

Open DroneLog is a drone flight log analyzer built by a single developer (Arpan Ghosh) who wanted to organize and analyze DJI flight data without feeding it to a commercial platform. The result is a Tauri v2 desktop app for Windows, macOS, and Linux, plus a Docker-deployable web app for self-hosted use on a NAS or home server [README][homepage].

The pitch is simple: your flight logs contain GPS tracks, battery telemetry, speed, altitude, cell voltages, and RC signal data. That data is yours. Open DroneLog lets you visualize it, search it, export it, and replay it in 3D — with nothing leaving your network.

What makes it technically interesting is the choice of DuckDB as the storage engine [README]. DuckDB is an in-process analytical database optimized for aggregate queries over large datasets — exactly the right tool for scanning thousands of flight records to find patterns in battery degradation or maximum altitude across 200 flights. It’s not a generic SQLite choice; it’s a considered pick for the workload.

The project supports DJI flight logs (.txt format from the DJI Fly app), Litchi CSV exports, and Airdata CSV exports [README]. Third-party apps like Dronelink and DroneDeploy are also supported. External parser plugins can be configured via parsers.json for additional formats [README]. The website compares favorably against “popular commercial alternatives” in a feature matrix on its homepage, though the full table wasn’t available in scraped text [homepage].

As of this review, the project has 1,230 GitHub stars. It was featured in Self-Host Weekly’s March 2026 edition [1], which covers the most interesting new self-hosted projects each week — a meaningful signal for a tool in this niche. The project is clearly one person’s work, which is both a strength (clear vision, fast iteration) and a risk (bus factor of one).

---

Why People Choose It

The case for Open DroneLog comes down to three things commercial pilots feel in their gut: cost, privacy, and export lock-in.

Versus Airdata UAV and DroneLogbook. Both are subscription-based cloud platforms. You upload your flight logs to their servers, and in exchange you get a web dashboard. The problem is that “your flight logs” means your GPS coordinates, altitude patterns, client job locations, and battery failure events are now sitting in someone else’s database. For a commercial drone pilot — the kind doing Part 107 work for real estate or infrastructure inspection — those logs represent client locations. Uploading them to a third-party cloud is a legitimate concern [homepage].

Open DroneLog doesn’t have this tradeoff. The README states explicitly: “All data in a local DuckDB” [README]. There is no cloud sync feature because there’s no cloud. The homepage drives this home with three repetitions of “No subscriptions. No advertisements. You are in control of your data” — which reads like marketing copy, but it’s also technically accurate.

On the DJI platform lock. DJI dominates the consumer and prosumer drone market. Their global market position means most non-hobbyists own DJI hardware [3]. DJI’s own flight log format has gone through multiple versions, and the app that exports those logs (DJI Fly) doesn’t always make migration easy. Open DroneLog specifically targets this situation — it’s a way to own your own data archive even if you keep using DJI hardware [README][homepage].

On compliance. Commercial pilots in the US operating under Part 107 are required to maintain flight logs. The tool’s PDF report feature and “user selectable fields” for what gets printed is explicitly designed for this: “Perfect for commercial drone pilots, regulatory compliance, and client deliverables” [homepage]. This is a concrete use-case-driven feature, not marketing filler.

---

Features

Based on the README and website:

Core analytics engine:

• DuckDB-powered queries with automatic downsampling for large datasets [README]
• Smart deduplication — prevents duplicate imports based on drone serial, battery serial, and start time [README]
• Multi-format import: DJI logs (.txt), Litchi CSV, Airdata CSV, with automatic unit detection (metric/imperial) [README]
• Optional external parser plugins via parsers.json [README]
• Tags (manual and automatic): auto-tags flights as Night Flight, High Speed, Cold Battery, and more [homepage]

Flight visualization:

• 3D terrain flight maps with altitude-aware aircraft marker [README][homepage]
• Map type selection: Satellite, Topographic, OpenStreetMap [README]
• Flight replay with speed control from 0.5× to 16× [README]
• Live telemetry overlay during replay, including RC joystick visualization [README]

Telemetry charts:

• Height, speed, battery, cell voltages, attitude, RC signal, GPS, distance-to-home, velocity [README]
• Battery full capacity and remained capacity tracking over time [README]
• Synchronized drag-to-zoom across all chart panels [README]
• Per-profile telemetry color customization, collapsible panel controls [README]
• Weather data overlay per flight [homepage]

Export and reporting:

• PDF flight log reports with user-selectable fields [homepage]
• Bulk export to CSV, JSON, GPX, and KML [README]
• Batch export across multiple flights [homepage]
• Full database backup and restore for moving data between devices [README]

Deployment options:

• Tauri v2 desktop app for Windows, macOS, Linux (and Raspberry Pi) [README][homepage]
• Docker / Docker Compose for self-hosted web deployment [README]
• AppImage for Linux without installation [README]
• PWA for mobile access [README]
• REST API for programmatic access [README]
• Profiles with password protection [README]

What it does not have:

• Multi-user team features or RBAC
• Cloud sync (by design)
• Support for FPV-specific log formats natively (the parsers.json plugin system is the path forward here)
• DJI Enterprise / Matrice log formats without additional parser configuration

---

Pricing: SaaS vs Self-Hosted Math

Open DroneLog: Free. Zero. No subscription, no free tier with upgrade prompt, no paywalls [homepage][README].

• Desktop app: download and run
• Self-hosted web: Docker on any machine, VPS, or NAS — you pay the server cost

The VPS math:

• Hetzner CAX11 (ARM, 2 vCPU, 4GB RAM): €4.49/mo
• Open DroneLog Docker: zero additional cost

That’s roughly $5–6/mo to run your own always-available drone log dashboard if you want a server deployment.

Commercial alternatives — pricing not available in provided sources. What is documented is that Airdata UAV and DroneLogbook both operate subscription models, and that the Open DroneLog homepage comparison explicitly positions itself as the free alternative to these platforms [homepage]. Specific tier pricing for those services wasn’t available in the sources reviewed, so no direct cost comparison is included here — the principle is that Open DroneLog replaces a recurring subscription with a one-time Docker setup.

For pilots already paying for a NAS (Synology, UGREEN): Open DroneLog is a natural fit — it’s a Docker Compose deployment on hardware you already own. Marius Hosting, which publishes Docker installation guides for popular NAS setups [2], covers this category of app extensively. The cost in that scenario is literally $0/mo beyond what you already pay for hardware.

---

Deployment Reality Check

The desktop app installation is straightforward on Windows and macOS. On macOS, there’s a friction point: because the developer doesn’t pay Apple’s $99/year developer signing fee, the binary triggers Gatekeeper’s “damaged file” warning [homepage]. The README and website document two workarounds — right-click to open, or run xattr -cr in Terminal. It’s a one-time step and the website explains it clearly [homepage], but it will confuse non-technical pilots who see “damaged and can’t be opened” for the first time.

Linux users need to build from source, which requires a Rust toolchain and Tauri dependencies [README]. An AppImage is also available as a no-install option [README].

Docker deployment is the self-hosted path. The README covers it; you need Docker and docker-compose, and the setup follows the standard pattern. No bundled database server is required since DuckDB runs in-process [README].

What can go sideways:

• macOS signing friction will stop non-technical users who don’t read instructions first [homepage]
• DJI Developer API key is required for some log parsing functionality. The README includes a section “How to obtain your own DJI Developer API key” [README] — which signals this is a setup step that some users will struggle with
• Single-developer project. At 1,230 GitHub stars, Open DroneLog is relatively niche. There’s no company behind it, no commercial support tier, and no SLA. If the developer loses interest, the project stops [README][homepage]
• AGPL-3.0 license. This matters if you’re planning to build something on top of it. AGPL requires that any modified version you run as a network service be released publicly. For a drone pilot just using the tool, this is irrelevant. For a company wanting to embed it in a fleet management product, this is a legal question [README]
• Log format compatibility depends on parser support. DJI has changed log formats before; older firmware versions may not match the parser, requiring manual updates [README]

Realistic install time: 20–40 minutes for the desktop app including the macOS signing workaround if needed. Docker on a NAS: 30–60 minutes for someone comfortable with Docker Compose.

---

Pros and Cons

Pros

• Genuinely free. No subscription, no premium tier, no feature paywall. The project’s explicit philosophy is “free forever” [homepage].
• Privacy-first by architecture. Not “privacy-respecting with an option to opt out of telemetry” — the data literally never leaves your machine. The storage engine is local DuckDB [README].
• DuckDB performance. Using an analytical database for flight log queries is the right call. Large log collections query fast; time-series telemetry charts don’t lag [README].
• 3D flight replay with speed control. The 0.5×–16× playback with live telemetry overlay is the kind of feature that justifies the whole tool for pilots reviewing incidents or analyzing technique [README].
• PDF report generation. User-selectable fields and compliance-ready output for Part 107 logbook requirements is a real differentiator from generic log viewers [homepage].
• Cross-platform. Windows, macOS, Linux, Raspberry Pi, Docker — the same data, accessible everywhere [README][homepage].
• Smart auto-tagging. Auto-detecting Night Flight, High Speed, and Cold Battery conditions on import is genuinely useful for batch analysis [homepage].
• Battery health tracking. Tracking full capacity and remaining capacity trends over time catches degrading cells before they cause an incident [README].

Cons

• AGPL-3.0, not MIT. More restrictive for developers wanting to build on it or embed it commercially compared to more permissive licenses [README].
• Single-developer project. No company, no support team, no SLA. The project exists because one person cares about it [README][homepage]. GitHub stars (1,230) are respectable for the niche but not a large community safety net.
• macOS Gatekeeper friction. The “damaged file” warning on first launch is a real barrier for non-technical pilots and requires a Terminal command to fix [homepage].
• DJI API key dependency. Some log parsing functionality requires a DJI Developer API key, adding a registration step and dependency on DJI’s developer program [README].
• No multi-user or fleet management. Profiles with password protection exist, but this isn’t a team tool. A drone fleet with multiple pilots needs something else [README].
• No cloud sync by design. If you want your logs accessible across devices without managing a server, this is the wrong tool — that’s the exact feature it refuses to provide [homepage].
• Niche community. The self-hosted ecosystem for drone tools is small. Finding answers to edge cases, troubleshooting DJI format changes, or contributing plugins requires interacting with a small contributor pool [README].

---

Who Should Use This / Who Shouldn’t

Use Open DroneLog if:

• You’re a drone pilot (DJI or Litchi) who wants to analyze your own data without an ongoing subscription.
• You’re operating commercially under Part 107 and need compliant PDF flight log reports without paying a platform fee for them.
• You care about privacy enough that uploading GPS coordinates of your client locations to a cloud service feels wrong.
• You have a NAS or can deploy Docker, or you’re happy with the desktop app.
• You’re a hobbyist pilot who wants actual telemetry analysis — battery degradation curves, speed profiles, altitude maps — without a dashboard account.

Skip it (use Airdata UAV) if:

• You want a zero-setup cloud dashboard that works immediately after creating an account.
• You don’t care where your data lives and value convenience over control.
• You need multi-pilot fleet management with centralized data.
• The macOS command-line workaround for Gatekeeper is already too much friction.

Skip it (use DroneLogbook) if:

• You need a platform that’s commercially supported with an SLA.
• Your compliance requirements need a cloud-hosted, auditable system rather than local storage.

Skip it if:

• You fly FPV exclusively — DJI and Litchi are the supported formats, and while the parser plugin system exists for extensions, FPV log formats aren’t a first-class citizen.
• You manage a commercial fleet and need role-based access, team accounts, or API integration into operations software.

---

Alternatives Worth Considering

• Airdata UAV — the commercial cloud standard in this niche. Subscription-based, polished, multi-platform. The platform that most pilots migrate away from when they find Open DroneLog. Pricing data not available in reviewed sources.
• DroneLogbook — another commercial subscription platform focused on Part 107 compliance logging and fleet management. Better for team operations than Open DroneLog.
• DJI FlightHub 2 — DJI’s own enterprise fleet management platform. If your entire fleet is DJI Enterprise hardware, this is the native option. Expensive, proprietary, cloud-dependent, not self-hostable.
• Flylitchi — Litchi’s companion ecosystem. Relevant only if you fly Litchi missions; covers route planning more than log analysis.
• Healthybirds (various community tools) — there’s a long tail of hobby scripts and Python tools for parsing DJI CSVs, none with the feature set or polish of Open DroneLog.

For a drone pilot who wants to escape a subscription log platform, the realistic shortlist is Open DroneLog vs. Airdata UAV. If you’re technical enough to run Docker or tolerate the macOS workaround, Open DroneLog wins on cost and privacy by default. If you’re a non-technical pilot who just wants it to work with an email signup, Airdata is the path of least resistance.

---

Bottom Line

Open DroneLog fills a specific gap well: it’s the tool for the DJI pilot who doesn’t want to pay monthly to analyze data their own drone collected. The DuckDB backend and Tauri v2 stack are genuinely good technical choices for the problem, and features like 3D flight replay, battery degradation tracking, and Part 107-ready PDF reports are real, documented functionality — not vaporware. The trade-offs are equally real: this is a one-developer project, AGPL-3.0 complicates commercial use, and macOS users will hit a Gatekeeper hurdle before they see the dashboard. For a hobbyist or solo commercial pilot who can deploy Docker or tolerate a one-time Terminal command, those trade-offs are worth it to get a permanent, zero-subscription flight analytics dashboard. For a drone fleet operation or a non-technical pilot who wants instant setup, the commercial platforms still have the advantage.

---

Sources

1. Self-Host Weekly (13 March 2026) — Ethan Sholly, selfh.st. https://selfh.st/weekly/2026-03-13/
2. Marius Hosting — NAS self-hosted app installation guides. https://mariushosting.com/page/4/
3. “Top 10 Drone Manufacturers in the World (2025)” — ElectroIQ, Joseph D’Souza (updated Nov 03, 2025). https://electroiq.com/stats/drone-manufacturers/

Primary sources:

• GitHub repository and README: https://github.com/arpanghosh8453/open-dronelog (1,230 stars, AGPL-3.0 license)
• Official website: https://www.opendronelog.com
• Web app: https://app.opendronelog.com