Larger accounting datasets and more complex reporting increase PHP and database work.
Growing companies with longer financial history.Configuration matérielle requise pour Akaunting : RAM, processeur, base de données et stockage
Planifiez l’auto-hébergement d’Akaunting pour la RAM, le CPU, la base de données, les pièces jointes et Docker, avec des recommandations pratiques d’installation personnalisée de ZimaOS pour les petites entreprises.
Akaunting requirements at a glance
Akaunting publishes software prerequisites rather than a numerical hardware table. Its official Docker repository provides an application-plus-database deployment path, while the on-premise docs require PHP 8.1+, a supported database and a web server.
- RAM
- No numerical official minimum published. Practical host memory must cover Akaunting/PHP, the database, queues and other ZimaOS services.
- CPU
- No numerical official core minimum published. Interactive accounting is light, but imports, reports, extensions and background jobs can add CPU demand.
- Storage
- No universal official minimum. Database records, uploaded documents, application extensions, logs and backups determine capacity.
- Database
- Official requirements support databases including MySQL, PostgreSQL, SQLite and SQL Server; the Docker workflow commonly pairs Akaunting with a database container.
- GPU
- No GPU is required for normal accounting, invoicing, reporting or inventory workflows.
- Best Zima starting point
- ZimaBoard 2 832 is a comfortable small-business starting point when paired with SSD-backed database storage; use 16 GB for more extensions and co-hosted business apps.
From official requirements to the right setup
Size Akaunting as a PHP/Laravel application plus its database, uploaded financial documents and backups.
-
Official requirements
Start with Akaunting's official software requirements: PHP 8.1+, a supported database, a web server and the required PHP extensions. Upstream publishes no numerical CPU/RAM minimum.
-
Confirm your needs
Estimate active users, invoices, transactions, imports, reports and installed extensions. Custom apps can change the resource profile beyond the core accounting application.
-
Leave room to grow
Put the production database and attachments on durable storage, and keep independent backups because financial history is the critical state.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with Akaunting's official Docker setup, persist the app/database volumes, complete the setup wizard, and expose the service through HTTPS.
Check every playback client
- Number of accounting users
- Invoices/transactions/import volume
- Installed Akaunting extensions
- Database choice
- Attachment/document growth
- Queue/background jobs
- Backup retention
- Other ZimaOS business apps
Official minimum requirements
Akaunting's current on-premise requirements specify software dependencies but not a numerical server CPU, RAM or disk floor.
Do not present a generic 2 GB or 4 GB number as Akaunting's official hardware minimum. For ZimaOS, 8 GB is practical whole-host headroom for a small deployment, but it is a recommendation rather than an upstream requirement.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | Official requirements focus on PHP, database and web-server compatibility. |
| CPU minimum | No numerical official minimum published | Reports, imports, extensions and queues change practical CPU demand. |
| Storage minimum | No numerical official minimum published | Database, files, extensions and backups determine capacity. |
| PHP | PHP 8.1 or higher | Current Akaunting on-premise requirement. |
| Database | MySQL, PostgreSQL, SQLite, SQL Server and compatible options | Current official documentation lists multiple supported database choices. |
| Container deployment | Official Akaunting Docker repository | Provides Docker Compose examples and a setup workflow. |
When to upgrade your hardware
Akaunting should scale when database activity, reporting or installed extensions create sustained load.
Reports and transaction volume increase
Extensions and integrations add background jobs
Attachments and backups grow
Payroll, inventory, banking and other extensions can add queues, scheduled tasks and external API work.
Businesses using a heavily extended Akaunting stack.Invoices, receipts, uploaded documents and database backups can become the main storage driver.
Document-heavy accounting workflows.Plan hardware growth with confidence
Scale Akaunting by keeping the database reliable and fast, then add RAM/CPU for larger extension and reporting workloads.
Use SSD-backed database storage
A responsive accounting database matters more than GPU capability for normal Akaunting use.
Use SATA/NVMe with ZimaBoard 2 or SSD storage on ZimaCube 2.Move to 16 GB for more extensions and business apps
Additional RAM gives the database, PHP workers and queues more headroom.
ZimaBoard 2 1664 is a compact 16 GB choice.Use multi-drive storage for document retention
Receipts, invoice attachments and backups may justify larger local capacity.
ZimaCube 2 Standard is a storage-first option.Choose stronger CPU for heavier reports and integrations
If reporting and scheduled work saturate the N150 class, stronger general-purpose CPU helps more than a GPU.
ZimaCube 2 Pro provides a stronger Core i5 platform.Can it run on ZimaOS?
Akaunting 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 using Akaunting's official Docker repository.
Custom install Akaunting in ZimaOS
Use Install Custom App with the official Akaunting Docker/Compose configuration, persist application and database data, configure database credentials, and complete the browser setup wizard.
Custom install Akaunting in the ZimaOS app ↗Use the official Akaunting Docker image
Akaunting maintains an official Docker repository with Compose examples and database/environment setup.
Review Akaunting Docker deployment ↗Match the current on-premise software requirements
Use PHP 8.1+ and a supported database/web-server stack when building or customizing the deployment.
Review Akaunting requirements ↗Choose Zima hardware for Akaunting
Akaunting is suitable for compact Zima hardware; database persistence and business-data protection matter more than acceleration.
Is this a small accounting server or a broader business-app/document platform?
Small business or personal accounting
Use ZimaBoard 2 with SSD-backed database storage and independent backups.
- Best starting pointZimaBoard 2 832
- More app headroomZimaBoard 2 1664
More extensions, documents and business services
Choose ZimaCube for stronger CPU/storage expansion when the broader workload justifies it.
- Storage-first platformZimaCube 2 Standard
- Higher-headroom platformZimaCube 2 Pro
These are practical recommendations, not official user-count or transaction-throughput tiers. Extensions, reporting, imports and co-hosted apps can change requirements.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small Akaunting deployments. | Akaunting, database, HTTPS proxy, light extensions and backups. |
|
Add SSD-backed database storage; onboard eMMC should not be the only location for financial data. | Get Now |
| ZimaBoard 2 1664 | Akaunting with more extensions and co-hosted business apps. | Larger database cache, queues, imports and additional containers. |
|
16 GB is whole-host headroom rather than an upstream Akaunting requirement. | Get Now |
| ZimaCube 2 Standard | Document-heavy accounting and larger local backup retention. | Akaunting plus receipts/invoice attachments, snapshots and broader NAS services. |
|
Choose it for storage topology; 8 GB Standard is not automatically better than a 16 GB ZimaBoard for memory-heavy app stacks. | Get Now |
| ZimaCube 2 Pro | Heavier business-app consolidation and reporting. | Akaunting, database, many extensions, integrations and other self-hosted business services. |
|
Large multi-user business deployments may still need separate database/application infrastructure. | 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 Akaunting RAM, CPU, database, storage, Docker and ZimaOS custom installation.
How much RAM does Akaunting need?
Akaunting does not publish a numerical official server RAM minimum. Practical memory depends on the database, PHP workers, extensions and other services.
How many CPU cores does Akaunting need?
There is no numerical official core minimum. Imports, reports, queues and extensions determine CPU demand.
How much storage does Akaunting need?
There is no universal official disk minimum. Plan capacity for the accounting database, attachments, extensions, logs and backups.
Which database does Akaunting support?
Akaunting's current requirements list database options including MySQL, PostgreSQL, SQLite and SQL Server.
Does Akaunting need an SSD?
SSD is not an upstream hard minimum, but SSD-backed database storage is strongly preferable for a self-hosted accounting server.
Does Akaunting need a GPU?
No dedicated GPU is required for invoicing, accounting, inventory or normal financial reporting.
Can ZimaBoard 2 run Akaunting?
Yes. The 8 GB model is a comfortable small deployment host when paired with durable SSD-backed database storage and backups.
Can I install Akaunting on ZimaOS?
Yes through Install Custom App using Akaunting's official Docker setup. A public official one-click ZimaOS page was not confirmed in the sources checked for this guide.
What sources informed this Akaunting hardware guide?
The guide uses Akaunting's current on-premise requirements and official Docker repository plus current Zima product pages for practical hardware matching.
