Bulk CSV/CAMT jobs create temporary CPU/database activity.
Users importing long transaction histories.Firefly IIIのハードウェア要件：RAM、CPU、ストレージ
RAM、CPU、MariaDBまたはPostgreSQL、取引データのインポートとバックアップを考慮したFirefly IIIのハードウェア構成と、実用的なZimaOSカスタムインストールの推奨事項。
Firefly III requirements at a glance
Firefly III publishes official Docker images and database options but no universal CPU, RAM or disk minimum. Practical sizing depends on the app, database, transaction history, imports and backups.
- RAM
- No numerical official minimum published; the app, database and optional Data Importer share whole-host memory.
- CPU
- No numerical official core minimum; normal use is light, while imports and reports create bursts.
- Storage
- No universal official minimum; transaction history, database files, logs/imports and backups determine capacity.
- Database
- Current configuration supports MySQL/MariaDB, PostgreSQL and SQLite; official Compose uses MariaDB by default.
- Docker
- Official stable images are published as fireflyiii/core and the official Docker repository includes Compose files.
- Best Zima starting point
- ZimaBoard 2 832 is ample for personal use; 16 GB is useful when adding the Data Importer and other apps.
From official requirements to the right setup
Size Firefly III from its real service stack and persistent data rather than using a guessed one-size-fits-all server number.
-
Official requirements
Use Firefly III's official Docker image and Compose files; upstream does not publish a universal CPU/RAM minimum.
-
Confirm your needs
Choose the database: MySQL/MariaDB, PostgreSQL or SQLite are supported, with MariaDB used in the default Compose stack.
-
Leave room to grow
Estimate transaction history, import frequency, reports and backup retention; large imports create temporary processing load.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with the official Compose setup and add the Data Importer only if needed.
Check every playback client
- Transaction/account count
- Import frequency
- Data Importer required
- Database choice
- Backup retention
- Reverse proxy/HTTPS
- Cron/maintenance tasks
- Other ZimaOS services
Official minimum requirements
Firefly III's current project and Docker documentation provide deployment options but do not publish numerical host CPU/RAM/storage minimums.
Do not invent a 1 GB or 2 GB official minimum. Whole-host sizing must include the chosen database and any Data Importer.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | App, database and optional importer determine memory. |
| CPU minimum | No numerical official minimum published | Imports/reports create bursty work. |
| Storage minimum | No numerical official minimum published | Database, logs/imports and backups determine capacity. |
| Official image | fireflyiii/core:latest | Current stable Docker image tag. |
| Default Docker database | MariaDB/MySQL | Official Compose uses MariaDB by default. |
| Other DB options | PostgreSQL and SQLite supported | Current environment configuration documents mysql, pgsql and sqlite. |
When to upgrade your hardware
Upgrade Firefly III when measured workload, storage growth or background processing outgrows the current host.
Large imports take longer
Database history and reports grow
More finance/business apps share the host
Long-lived financial history increases database/cache and backup size.
Multi-year finance archives.Firefly III may remain light while surrounding services consume resources.
All-in-one servers.Plan hardware growth with confidence
Scale Firefly III by addressing the actual bottleneck—database, storage, processing or concurrency—before simply buying a larger server.
Use SSD-backed database storage
Fast durable SQL storage improves consistency and responsiveness.
SATA/NVMe on ZimaBoard 2 or SSD tiers on ZimaCube 2.Use 16 GB for importer and other apps
Extra RAM benefits the broader Docker stack.
ZimaBoard 2 1664.Use larger storage for backup retention
Long snapshot/backup retention may justify more capacity.
ZimaCube 2 Standard.Use stronger CPU only for broader workloads
Firefly III alone rarely needs high-end CPU.
ZimaCube 2 Pro when other services justify it.Can it run on ZimaOS?
Firefly III is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can still be deployed through Install Custom App.
Custom install Firefly III in ZimaOS
Use Install Custom App with the official Firefly III Compose configuration, persist database/application volumes and configure secrets.
Custom install Firefly III in the ZimaOS app ↗Use Firefly III's official Docker images
The project publishes stable fireflyiii/core images and official Compose files.
Review Firefly III Docker repository ↗Add the Data Importer only when required
Official documentation provides a Compose workflow for Firefly III plus the Data Importer and database.
Review Firefly III Docker installation ↗Choose Zima hardware for Firefly III
Choose Zima hardware for the complete Firefly III workload, including its database, storage and background services.
Is this a simple personal finance server or part of a larger home-server stack?
Personal Firefly III
Use ZimaBoard 2 with SSD-backed database storage.
- Best starting pointZimaBoard 2 832
Firefly III plus importer and more apps
Use more RAM/storage for the broader stack.
- More app headroomZimaBoard 2 1664
- Broader storage platformZimaCube 2 Standard
These are practical workload recommendations, not official throughput or user-count guarantees.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Personal Firefly III installations. | Firefly III, MariaDB/PostgreSQL, reports and backups. |
|
Add durable SSD-backed database storage. | Get Now |
| ZimaBoard 2 1664 | Firefly III plus Data Importer and other finance apps. | Larger Docker stack with more databases and automation. |
|
16 GB is whole-host headroom, not an official minimum. | Get Now |
| ZimaCube 2 Standard | Finance server combined with broader NAS/backup use. | Firefly III plus long snapshot retention and other storage services. |
|
Choose it for wider storage duties, not because Firefly III needs six HDD bays. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
These answers cover Firefly III RAM, CPU, storage, Docker and ZimaOS deployment.
How much RAM does Firefly III need?
Firefly III does not publish a numerical official server RAM minimum.
How many CPU cores does Firefly III need?
There is no numerical official core minimum.
Which databases does Firefly III support?
MySQL/MariaDB, PostgreSQL and SQLite are supported; official Compose uses MariaDB by default.
How much storage does Firefly III need?
No universal official disk minimum; database history, imports and backups determine capacity.
Does Firefly III need an SSD?
Not as a hard requirement, but SSD-backed SQL storage is sensible for financial data.
Does Firefly III need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run Firefly III?
Yes. The 8 GB model is ample for Firefly III and a small database.
Does Firefly III have official Docker images?
Yes. The project publishes fireflyiii/core images and official Compose files.
What sources informed this Firefly III hardware guide?
Current Firefly III Docker repository, documentation and environment configuration plus current Zima product pages.
