Deploy Open DroneLog
Self-hosted drone flight-log analyzer, maps and logbook
open-dronelog
Just deployed
/data/drone-logbook
Deploy and Host self hosted Open DroneLog (Other) on Railway
This template deploys Open DroneLog, a self-hosted drone flight-log analyzer and logbook, as independent community packaging of arpanghosh8453/open-dronelog 3.3.2 (AGPL-3.0, Copyright 2026 Arpan Ghosh). It is not affiliated with or endorsed by Open DroneLog, DJI, Litchi, Airdata, or DroneDeploy.
About Hosting Open DroneLog open-source software on Railway (self hosted Open DroneLog template)
Open DroneLog is AGPL-3.0 open-source software, and this template runs an unmodified upstream image, so your flight logs sit in a DuckDB database on a volume in your own Railway service.
Why Deploy Open DroneLog, the self-hosted drone flight-log analyzer on Railway
A vendor-hosted flight logbook keeps your flight history and telemetry on someone else's servers under their terms.
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Open DroneLog on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Railway vs Other Hosting Providers and VPS for Open DroneLog self hosting
Open DroneLog runs as one Railway service with a persistent volume, so the choice depends on how much server work you want to own.
| Provider | What You Get with Railway | What You Get with the Other Provider |
|---|---|---|
| DigitalOcean | A deployed service with a public HTTPS domain and a volume at /data/drone-logbook. | A Droplet you patch, configure and secure yourself, including Docker, the volume and TLS. |
| AWS | One click from the template with the health check, volume and variables already wired. | Broad networking and storage control, but you assemble the instance, disks and certificates. |
| Hetzner | Managed deployment of the single service with no server administration on your side. | Low-cost servers where you install the container and keep the volume and backups safe. |
Keep one replica either way, because DuckDB data on the volume is local persistent state.
Common Use Cases for hosted Open DroneLog
- Solo pilot logbook: Import your DJI .txt flight logs into one web UI, then browse every flight by date, drone, and battery without keeping a paper or spreadsheet logbook.
- Map review after a site survey: Open a flight on the map and scrub through the replay to check the path, altitude, and home point against the telemetry charts.
- Battery health tracking: Compare cycle counts and per-battery usage history over months so you can retire packs before they fail in the field.
- Team fleet records: Give each pilot or drone fleet its own profile, with the default profile locked by a generated password and extra profiles gated by the master password.
- Long-term data ownership: Keep all flight records in DuckDB on your own Railway volume, so the logbook stays under your control and survives redeploys.
Dependencies for Open DroneLog Docker hosted on Railway
This template runs one service built from the unmodified upstream image plus a Railway start wrapper.
Deployment Dependencies for Managed Open DroneLog Service
The open-dronelog service is public on port 8080, with a volume at /data/drone-logbook, a health check at /, and restart policy Always. Keep one replica. Unlock the default profile with DEFAULT_PROFILE_PASSWORD from Variables; that password is applied on first boot only. PROFILE_CREATION_PASS is required to create or delete extra profiles.
Implementation Details for Open DroneLog
The image ghcr.io/onepush-dev/open-dronelog:3.3.2 is the unmodified upstream ghcr.io/arpanghosh8453/open-dronelog:3.3.2 image plus a Railway start wrapper. Railway injects PORT=8080, which the Axum backend would also read, so the wrapper runs the backend with PORT=3001 and HOST=127.0.0.1, where nginx proxies /api, and nginx is rewritten to listen on 8080 for IPv4 and IPv6. Baked environment values are DATA_DIR=/data/drone-logbook, KEEP_UPLOADED_FILES=true and RUST_LOG=info. PROFILE_CREATION_PASS is hashed and cleared from the process environment at boot. Sessions use the X-Session header and live in memory, so a restart signs you out, but DuckDB data on the volume persists. SYNC_LOGS_PATH and SYNC_INTERVAL are not useful on Railway. Optional DJI_API_KEY can be set in Variables or in the app to decrypt newer DJI logs. DJI, Litchi, Airdata and DroneDeploy are named only as log formats this app can import.
How does Open DroneLog compare against other tools
Open DroneLog is an independent community packaging of arpanghosh8453/open-dronelog 3.3.2 (AGPL-3.0, Copyright 2026 Arpan Ghosh), not affiliated with or endorsed by Open DroneLog, DJI, Litchi, Airdata, or DroneDeploy.
Open DroneLog vs a vendor-hosted flight logbook (Vendor-Hosted Flight Logbook Alternative)
- Data location: Open DroneLog keeps flights in DuckDB on the /data/drone-logbook volume you control, while a vendor-hosted logbook keeps them on the vendor's servers.
- Setup effort: A vendor-hosted logbook usually needs only an account, while Open DroneLog needs you to unlock the default profile with DEFAULT_PROFILE_PASSWORD from Variables.
- Password changes: DEFAULT_PROFILE_PASSWORD is applied on first boot only, so later changes must be made in the app under Settings, Profile Password.
Open DroneLog vs reviewing logs in a spreadsheet (Spreadsheet Log Review Alternative)
- Parsing: Open DroneLog imports DJI .txt, Litchi and Airdata CSV, DroneDeploy Flight Recorder and Open DroneLog CSV files, then shows maps and telemetry charts, while a spreadsheet needs manual parsing and charting.
- Flexibility: A spreadsheet is better for custom formulas and one-off analysis, while Open DroneLog is better for repeatable flight review.
Open DroneLog with Docker vs Railway (Railway Alternative)
- Control: Running the image with Docker on your own machine gives full host control, while Railway handles the public domain, HTTPS at the platform edge, and the Always restart policy.
- Configuration: Railway sets variables and the volume from the dashboard, while Docker uses your own run or compose commands.
How to use Open DroneLog on Railway?
Follow these steps on your first day after the deploy finishes.
- Open the public domain Railway generated for the open-dronelog service.
- Copy DEFAULT_PROFILE_PASSWORD from the Variables tab and use it to unlock the default profile. It is applied on first boot only, so change it later in the app under Settings, Profile Password.
- Import flight logs, or add a manual flight if you have no log file yet.
- Enter PROFILE_CREATION_PASS when you create another profile, since it is required to create or delete extra profiles.
- For newer DJI logs, add DJI_API_KEY in Variables or enter it in the app.
- Keep one replica, because local state lives on the volume at /data/drone-logbook.
Replicas: 1 Health check: /
How to self host Open DroneLog on other VPS Services (Open DroneLog self hosting guide)
Clone the Repository
Clone the upstream repository so you have the source and its documentation on your server.
git clone https://github.com/arpanghosh8453/open-dronelog
cd open-dronelog
Install Dependencies
On a VPS you only need a container runtime. Install Docker, then confirm it runs before you go further.
docker --version
Configure Environment Variables
Set a data directory on a path that survives restarts, and set your own passwords.
export DATA_DIR=/data/drone-logbook
export DEFAULT_PROFILE_PASSWORD=your-strong-password
export PROFILE_CREATION_PASS=your-master-password
Start the Open DroneLog Application
Use the upstream flow: run the documented open-dronelog container with a data directory. nginx listens on port 80 and the API on 3001 by default, so map port 80 to a port on your host and place a reverse proxy with TLS in front of it.
docker run -d \
-p 8080:80 \
-v drone-data:/data/drone-logbook \
--name open-dronelog \
ghcr.io/arpanghosh8453/open-dronelog:3.3.2
Railway handles the container runtime, the persistent volume, HTTPS at the edge, and restarts for you.
Pricing and License of Open DroneLog (Open DroneLog pricing)
Open DroneLog is open-source software released under the AGPL-3.0 license, so you can self-host it without paying a license fee.
What you do pay for is the infrastructure it runs on.
Open DroneLog hosted vs self hosted comparison (Pricing, features, costs, and more)
This template packages the AGPL-3.0 software, and no vendor logbook plan prices are quoted here.
Monthly cost of self hosting Open DroneLog on Railway
Railway bills by usage, so the monthly cost depends on RAM and CPU use, the size of the volume at /data/drone-logbook, and any other services you add.
System Requirements for Hosting Open DroneLog on a VPS
On a VPS you supply the CPU, memory, and disk. Keep room for the DuckDB databases and any uploaded logs you choose to keep.
Frequently Asked Questions (FAQs)
How do I unlock the app after deploying?
Copy the generated DEFAULT_PROFILE_PASSWORD from the service Variables tab and enter it to unlock the default profile.
What if I change DEFAULT_PROFILE_PASSWORD later?
Changing the variable will not reset a profile password that already exists.
Why was I signed out after a redeploy?
Sessions are kept in memory, so a restart signs you out.
Are DJI or Litchi part of this project?
No. Those names refer only to log formats the app can import.
What should I back up?
Back up the volume mounted at /data/drone-logbook, which holds your DuckDB databases, profiles, and uploaded logs.
Template Content
open-dronelog
ghcr.io/onepush-dev/open-dronelog:3.3.2