Vaultwarden itself may use little RAM, but reverse proxy, databases, backups, photo services and monitoring can make whole-host headroom the real issue.
Users consolidating a larger Productivity/self-hosting stack.Maskinvarukrav för Vaultwarden: CPU, RAM, lagring och databas
Lär dig mer om kraven på processor, RAM, SQLite, bilagor, HTTPS och säkerhetskopiering för Vaultwarden och välj sedan lämplig ZimaOS-hårdvara.
Vaultwarden requirements at a glance
Vaultwarden does not publish a formal numerical CPU or RAM minimum. The Rust-based server is intentionally much lighter than the official Bitwarden server stack, and project discussions report successful deployments on Raspberry Pi 1/Zero-class hardware. For a real self-hosted password server, the more important requirements are persistent `/data`, HTTPS, database and attachment growth, reliable backups and enough host headroom for the rest of the server.
- CPU
- No numerical official minimum. Vaultwarden is lightweight for personal/family use; CPU demand rises with more concurrent users, organizations, WebSocket/API activity and external database work rather than media-style compute.
- RAM
- No formal numerical minimum. Project discussions mention Raspberry Pi 1/Zero-class systems and suggest around 1 GB as a comfortable low-end reference as the database grows, but this is community/maintainer guidance rather than a specification.
- Database
- SQLite is the most common default deployment. PostgreSQL is also supported for users who deliberately choose an external database architecture.
- Storage
- Persist `/data`. Password records and most state live in the database, while file attachments and Send attachments live as separate filesystem data and can dominate storage growth.
- HTTPS
- The web vault requires HTTPS and a secure browser context because it uses the Web Crypto API. Vaultwarden recommends placing the service behind a reverse proxy.
- Best Zima starting point
- ZimaBoard 2 832 is far above Vaultwarden's usual resource needs and is a strong personal/family starting point. Choose more memory or ZimaCube capacity for a larger Productivity stack, attachment storage and other self-hosted services—not for Vaultwarden alone.
From official requirements to the right setup
Vaultwarden sizing is primarily a reliability and data-layout problem, not a raw compute problem.
-
Official requirements
Start with the deployment model: run the recommended container image, persist `/data`, and use HTTPS/reverse proxy so the web vault has the secure browser context it requires.
-
Confirm your needs
Choose the database deliberately. SQLite is the common small-instance path; PostgreSQL can be used when you want a separately managed database service and its operational trade-offs.
-
Leave room to grow
Estimate filesystem growth from attachments and Sends separately from the database. A vault with thousands of credentials can remain small while large attachments make storage and backup size grow much faster.
-
Run it on ZimaOS
Install Vaultwarden from the ZimaOS App Store, create a tested backup of both database and required filesystem data, then monitor actual memory/database/attachment growth before considering a hardware upgrade.
Check every playback client
- Personal/family versus small-organization user count
- SQLite versus PostgreSQL database
- Number and size of file attachments
- Send attachment use
- HTTPS and reverse-proxy availability
- Persistent `/data` storage
- Automated database plus filesystem backup
- Other Productivity and network services sharing the host
Official minimum requirements
Vaultwarden's current project documentation does not publish a numerical CPU, RAM or disk-capacity minimum.
Do not turn one Raspberry Pi, 128 MB, 256 MB or 1 GB community deployment into an official minimum. The project is genuinely lightweight, but a password manager should be sized for reliable persistence, backup, HTTPS and the rest of the host—not the smallest number that can boot.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | No numerical official minimum | Vaultwarden is designed as a resource-efficient Bitwarden-compatible server. |
| RAM | No numerical official minimum | Project discussions report Pi 1/Zero-class deployments; 1 GB is a practical community reference, not a formal requirement. |
| Persistent data | /data | The official Docker example mounts a persistent host path to `/data`. |
| Default/common database | SQLite | The backup wiki describes SQLite as the most common setup. |
| Alternative database | PostgreSQL supported | A separately managed database can be used when desired. |
| Web-vault security | HTTPS / secure context required | The Web Crypto API used by the web vault requires a secure context. |
When to upgrade your hardware
Upgrade Vaultwarden only when data growth or the surrounding server stack proves the small-service baseline is no longer enough.
The host runs many other self-hosted services
Attachments and backup sets keep growing
You intentionally move from SQLite to an external database
Vaultwarden's backup documentation says attachments are stored outside the SQL database and can be arbitrarily large. Storage and backup windows can therefore grow faster than database size.
Organizations or users storing document/SSH-key/file attachments.PostgreSQL introduces another service with its own memory, storage, backup and operational needs. Upgrade for the combined architecture rather than a presumed Vaultwarden process requirement.
Larger or operationally managed self-hosted deployments.Plan hardware growth with confidence
Scale Vaultwarden by protecting state and controlling attachment/database growth.
Keep SQLite for a normal personal/family deployment
The project describes SQLite as the most common setup and it avoids adding another database service to a small server.
ZimaBoard 2 832 has ample host resources for this pattern.Use PostgreSQL only when its operational model helps
PostgreSQL is supported, but it adds another persistent service and backup path rather than automatically making a small vault faster.
Leave RAM and durable storage for the database if you deliberately adopt it.Back up the database correctly plus filesystem data
Vaultwarden recommends SQLite `.backup`/the built-in backup command for an active SQLite database and separately requires attachment data to be backed up.
Keep backup copies outside the live `/data` path and test restores.Add storage for attachments, not password records
Credential database data is often small; attachments can be arbitrarily large and are stored outside SQL tables.
Move to larger SATA/multi-drive storage only when attachment and wider server data growth justify it.Can it run on ZimaOS?
Vaultwarden is currently available in the ZimaOS App Store in the Productivity category.
Install Vaultwarden from the ZimaOS App Store
Use the packaged application and persist the application data volume.
Open Vaultwarden in the ZimaOS App StorePut the web vault behind HTTPS
Vaultwarden's official README says the web vault requires HTTPS because Web Crypto needs a secure browser context and recommends using a reverse proxy.
Read Vaultwarden deployment guidanceBack up more than just a casual copy of db.sqlite3
Use the documented SQLite backup method and preserve required filesystem data such as attachments. Test a restore before relying on the backup.
Read Vaultwarden backup guidanceChoose Zima hardware for Vaultwarden
Vaultwarden is lightweight. Choose hardware from the whole Productivity stack, attachment storage and database/backup architecture rather than password count alone.
Is Vaultwarden a personal/family password service or one component of a larger Productivity server?
Personal/family Vaultwarden
ZimaBoard 2 832 offers very large headroom for Vaultwarden itself.
- Personal/family password serverZimaBoard 2 832
- Vaultwarden plus more Productivity servicesZimaBoard 2 1664
Larger all-in-one server with attachments, backups and many applications
Move to ZimaCube for storage and broader server capacity, not because Vaultwarden needs Core-class compute.
- Integrated multi-drive Productivity serverZimaCube 2 Standard
- Larger application/database/storage stackZimaCube 2 Pro
There is no official Vaultwarden CPU/RAM minimum or fixed users-per-server benchmark. Database choice, attachments, concurrent clients, reverse proxy and co-hosted services all affect practical resource use.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A personal or family Vaultwarden server. | SQLite Vaultwarden, reverse proxy and a few lightweight companion apps. |
|
Vaultwarden itself is unlikely to exhaust this hardware; backup reliability matters more. | Get Now |
| ZimaBoard 2 1664 | Vaultwarden plus more Productivity, proxy and database services. | Larger self-hosted application stack and more memory headroom. |
|
16 GB is for consolidation, not a Vaultwarden requirement. | Get Now |
| ZimaCube 2 Standard | A multi-drive Productivity/storage server that includes Vaultwarden. | Password service plus attachments, backups and broader self-hosted storage. |
|
Choose it for storage/application consolidation, not Vaultwarden CPU demand. | Get Now |
| ZimaCube 2 Pro | A larger all-in-one self-hosted Productivity platform. | Many services, databases, backup jobs and fast local storage workflows. |
|
10GbE and Core i5 resources benefit the overall platform rather than Vaultwarden alone. | 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 FAQ topics follow query fan-out around RAM, Raspberry Pi/low-power hosting, SQLite versus PostgreSQL, attachments, HTTPS and backups. Reddit and project discussions were used to surface recurring user questions without turning anecdotal numbers into official requirements.
How much RAM does Vaultwarden need?
Vaultwarden does not publish a formal RAM minimum. Project discussions report successful deployments on Raspberry Pi 1/Zero-class systems, and community guidance often treats around 1 GB as comfortable for a small instance with room for database growth.
Is 4 GB RAM overkill for Vaultwarden?
For Vaultwarden alone, usually yes. Recent Reddit users report very small container footprints, but 4 GB can still be useful if the same host runs a reverse proxy, backups and other containers.
Can Vaultwarden run on a Raspberry Pi or other low-power server?
Yes. The project community reports Vaultwarden running on very small Raspberry Pi-class systems. For a new 24/7 server, prioritize modern architecture, reliable storage and backups rather than the absolute lowest resource floor.
When should Vaultwarden use PostgreSQL instead of SQLite?
SQLite is the most common small-instance path and is appropriate for many personal/family deployments. PostgreSQL is useful when you deliberately want a separate managed database service; it is not automatically required just because the vault grows.
Do Vaultwarden attachments increase database size?
Attachments are stored as separate files outside the SQL database and can be arbitrarily large. They therefore affect filesystem storage and backup size more directly than the SQLite database itself.
Why does Vaultwarden require HTTPS?
The web vault uses the browser Web Crypto API, which requires a secure context. Vaultwarden's official README therefore says HTTPS is required and recommends a reverse proxy.
Can I back up Vaultwarden by copying db.sqlite3?
For a live SQLite database, Vaultwarden recommends the SQLite online `.backup` method or its built-in backup command. Attachments and other relevant files under `/data` also need separate backup; a database-only copy is not a complete Vaultwarden backup.
Can ZimaBoard 2 832 run Vaultwarden?
Yes. Its Intel N150 and 8 GB RAM provide far more capacity than a normal personal/family Vaultwarden deployment needs and leave room for reverse proxy and other Productivity services.
What sources and further reading informed this Vaultwarden hardware guide?
The Vaultwarden repository is the primary deployment source and establishes the lightweight Rust server, HTTPS requirement, recommended container path and persistent `/data`. The official backup wiki explains SQLite, attachments and restore requirements. Project hardware discussions and recent Reddit threads were used for query fan-out around low-memory/Pi hosting and whether several gigabytes of RAM are excessive; those experiences are not treated as formal minimums. The ZimaOS App Store confirms the current Productivity-category package.
