Check database query time and storage I/O alongside application CPU during a representative busy session.
Concurrent collaborators and migrations.Vikunja-hardwarevereisten: RAM, CPU, opslag en database, bijlagen en teamgebruik
Plan de RAM, CPU, SQLite of PostgreSQL, taakbijlagen en teamworkloads voor Vikunja, met actuele informatie over Docker-opslag en praktische serverdimensionering voor ZimaOS.
Vikunja hardware requirements at a glance
Vikunja publishes no numerical whole-host minimum in the reviewed Docker guide. SQLite is suitable for personal use; the project recommends PostgreSQL or MySQL for more than a handful of users. Persist task attachments separately from database state.
- RAM
- No numerical official minimum published. Include database resources and active collaborators rather than sizing only the Go application at idle.
- CPU
- No numerical official minimum published. Bulk imports, task queries, synchronization and concurrent requests determine practical activity.
- Storage
- Preserve attachments under /app/vikunja/files and, with default Docker SQLite, the database under /db. Add backups, exports and growth headroom.
- Database
- SQLite is the default. PostgreSQL 12+, MySQL 8.0+ and MariaDB 10.2+ are listed in current configuration docs; the current full example uses PostgreSQL 18.
- Docker / network
- Use the official vikunja/vikunja image and container port 3456. Set VIKUNJA_SERVICE_PUBLICURL to the actual reachable address and preserve the service secret.
- Best Zima starting point
- ZimaBoard 2 832 is a practical personal/small-team task host with durable state. Choose more RAM for external SQL and other shared services when measurements justify it.
From official requirements to the right setup
Plan the complete Vikunja workload before selecting a server.
-
Official requirements
Select the current stable Vikunja image and database mode. Use SQLite for a modest personal setup or the documented PostgreSQL/MySQL route when collaboration grows.
-
Confirm your needs
Estimate active collaborators, task/search queries, attachment size and bulk migration activity. The number of old completed tasks alone does not define request pressure.
-
Leave room to grow
Persist /app/vikunja/files and the actual database. The official Docker SQLite path is /db/vikunja.db; a files-only mount does not protect the database. Keep consistent backups and the service secret.
-
Run it on ZimaOS
Custom install in ZimaOS using available host port mapping for 3456, writable volumes and the actual public URL. If using an external database, size and back up that service independently.
Check every playback client
- SQLite versus PostgreSQL/MySQL
- Concurrent collaborators
- Import/synchronization batch size
- Task attachment volume
- Persistent /db for SQLite
- Persistent /app/vikunja/files
- Service secret and public URL
- Database permissions and backup restore
Official minimum requirements
Reviewed October 30, 2026 against the linked upstream deployment documentation. Numerical values retain their stated minimum, recommendation or example scope; select release-compatible instructions before installation.
No 1 GB or 2 GB official host minimum is invented here. Database choice changes the deployment footprint. Persisting attachments without the SQLite database is incomplete, and an external database is a separate workload rather than free capacity.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Whole-host RAM | No numerical official minimum published. | Include the chosen database and co-hosted services. |
| CPU cores | No numerical official minimum published. | Concurrent requests and imports drive practical compute. |
| Disk capacity | No numerical official minimum published. | Database, attachments, exports and retained backups need separate accounting. |
| Default database | SQLite | For more than a handful of users, upstream recommends MySQL or PostgreSQL. |
| Other supported database versions | PostgreSQL 12+, MySQL 8.0+, MariaDB 10.2+ | Current full Docker example uses PostgreSQL 18; use correct data-directory layout for that major version. |
| Official image / port | vikunja/vikunja; 3456 | Use the image platform matching Zima amd64 hardware and the current stable release. |
| Persistent Docker paths | /app/vikunja/files and /db for default SQLite | The official image presets /db/vikunja.db; preserve both state and files. |
When to upgrade your hardware
Use observed Vikunja workload pressure to decide when an upgrade is warranted.
Team queries/imports cause latency
SQLite becomes unsuitable for shared activity
Attachments and exports outgrow available space
Follow the upstream database recommendation for larger multi-user usage and plan the supported migration/backup path.
More than a handful of active users.Track uploaded files and backup retention separately from task records.
Teams attaching images and documents.Plan hardware growth with confidence
Address storage, memory, compute and deployment limits separately.
Preserve database and attachments correctly
Use durable volumes and test a consistent restore of both data types.
ZimaBoard 2 with suitable persistent SSD storage.Add RAM for SQL and shared apps
Choose 16 GB when external SQL and other services crowd the host.
ZimaBoard 2 1664.Expand attachment retention
Allocate additional capacity for uploads, exports and versioned backups.
SATA/PCIe SSD according to measured growth.Improve database/concurrency before replacing hardware
Use the appropriate database and inspect I/O/query behavior before adding CPU.
A modest host remains suitable for ordinary task management.Can it run on ZimaOS?
No specific public official one-click Vikunja ZimaOS app page was verified. Use Custom Install with the official image and current database/persistence configuration.
Custom install Vikunja in ZimaOS
Deploy vikunja/vikunja, persist files plus the actual database, map an unused host port to 3456 and configure the public URL/service secret. Reproduce the supported SQL service if selected.
Custom install Vikunja in the ZimaOS app ↗Use the official Vikunja deployment instructions
Keep the selected stable release, persistent paths and companion services aligned with upstream documentation.
Review Vikunja official installation ↗Verify database and URL configuration
Check current database versions, Docker environment overrides and persistence paths before increasing resources.
Review Vikunja deployment details ↗Which Zima hardware fits Vikunja?
Start with the lowest reasonable host for the actual workload. Product specifications were checked against the current product pages.
Which workload best matches your Vikunja deployment?
Personal tasks or modest collaboration
Use durable SQLite/files or a small documented SQL deployment.
- Workload optionZimaBoard 2 832
Task management alongside more services
Choose memory for the entire database/application stack.
- Workload optionZimaBoard 2 1664
These are practical workload recommendations, not official app requirements, compatibility certification, measured capacity limits or performance guarantees. Include all co-hosted services and independent backups.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Personal and small-team tasks | Vikunja with appropriate persistent database and attachment volumes. |
|
No fixed user/task capacity is promised; database choice and query behavior matter. | Get Now |
| ZimaBoard 2 1664 | More companion services | Vikunja, external SQL and broader light app consolidation. |
|
Extra RAM does not itself increase CPU cores or migrate a SQLite database. | 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
Answers to Vikunja RAM, CPU, storage, Docker, database and ZimaOS sizing questions.
How much RAM does Vikunja need?
No numerical official minimum is published in the reviewed Docker guide. Measure active usage with the selected database and all host services included.
How many CPU cores does Vikunja require?
No numerical core floor is given in the reviewed deployment docs. Concurrent task requests, imports and synchronization affect practical demand.
Should I use SQLite or PostgreSQL?
SQLite is the default and suits personal use. Upstream recommends PostgreSQL or MySQL for more than a handful of users; current configuration lists supported versions and the full Compose example uses PostgreSQL 18.
What must I persist with SQLite?
The official image stores SQLite at /db/vikunja.db, so persist /db as well as /app/vikunja/files. Retain service configuration/secrets and test a database-plus-attachment restore.
Does Vikunja need a GPU?
No GPU is required for standard task management. Use a supported runtime/image platform matching the host; Zima systems use amd64.
Can ZimaBoard 2 run Vikunja?
It is a practical personal/small-team host with reliable persistent storage. Select memory for the entire workload, including external SQL and other apps.
Why can the page open while API requests fail?
Check the public URL used by the browser, reverse-proxy routing, database reachability and file permissions. These are deployment configuration issues and do not automatically indicate insufficient hardware.
When should I choose ZimaCube 2?
Choose it for broader storage or processing requirements beyond ordinary task management. Large attachments and combined services should be measured before moving to a larger tier.
What sources informed this Vikunja hardware guide?
This guide was reviewed against the linked project deployment documentation on October 30, 2026. Zima device choices are editorial workload guidance, separate from upstream requirements and measured performance.
