Self-host Firefly III with Levelrail
VerifiedA self-hosted personal finance manager for tracking budgets, bills, and spending.
- Authorfirefly-iii
- LicenceAGPL-3.0-or-later
- Memory512 MiB
- Archarm64
- Services2
How to self-host Firefly III
-
Pull the images
2 images are pulled on your server.
Show images
mariadb:11fireflyiii/core:version-6.2.3
-
Create the app
2 services start in a single Compose app, with 2 named volume mounts for your data, on port 8080.
-
Fill in the secrets
4 secrets are generated and stored encrypted, 7 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Firefly III requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-or-later, network copyleft (agpl) license
- Verified. Verified on arm64 with image tag version-6.2.3. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 8080 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Firefly III. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Firefly III docs page.
Deploy Firefly III your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Firefly III from the CLI
levelrail-cli templates deploy firefly-iii --name my-firefly-iii Deploy Firefly III with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/firefly-iii/deploy Firefly III configuration
Firefly III services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | mariadb:11 | none | firefly_db_data -> /var/lib/mysql |
| firefly | fireflyiii/core:version-6.2.3 | 8080 | firefly_upload_data -> /var/www/html/storage/upload |
Firefly III environment variables
| Variable | Service | Value |
|---|---|---|
| MYSQL_DATABASE | db | Preset by the template |
| MYSQL_PASSWORD | db | Generated at deploy |
| MYSQL_ROOT_PASSWORD | db | Generated at deploy |
| MYSQL_USER | db | Preset by the template |
| APP_KEY | firefly | Generated at deploy |
| APP_URL | firefly | Preset by the template |
| DB_CONNECTION | firefly | Preset by the template |
| DB_DATABASE | firefly | Preset by the template |
Show all 11 variables
- DB_HOSTfireflyPreset by the template
- DB_PASSWORDfireflyGenerated at deploy
- DB_USERNAMEfireflyPreset by the template
Ports and volumes
- Ports
- 8080
- Volumes
- 2 named mounts: firefly_db_data -> /var/lib/mysql, firefly_upload_data -> /var/www/html/storage/upload
Firefly III FAQ
How much memory does Firefly III need?
The catalog lists about 512 MiB of memory for Firefly III across its 2 services.
Does Firefly III run on arm64?
For Firefly III, arm64 is tested; amd64 is image published.
What licence is Firefly III under?
Firefly III is licensed under AGPL-3.0-or-later, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Firefly III need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Firefly III bundle?
The template includes MySQL, running as its own service.
Which ports does Firefly III use?
Firefly III listens on port 8080 inside the stack.
Where does Firefly III keep its data?
In named volumes: firefly_db_data mounted at /var/lib/mysql and firefly_upload_data mounted at /var/www/html/storage/upload.
Can I deploy Firefly III on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id firefly-iii for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image mariadb:11, fireflyiii/core:version-6.2.3 is what you deploy there.