The official standard Linux stack has materially higher CPU, RAM, and storage requirements than Lite. Moving to business use or a standard deployment changes the host baseline before user growth is considered.
Businesses, organizations, or administrators moving beyond personal/home-lab Lite deployments.Bitwarden-Hardwareanforderungen: Lite- vs. Standard-Self-Hosting
Vergleiche die Anforderungen für das Self-Hosting von Bitwarden Lite und der Standardversion in Bezug auf RAM, CPU, Speicher, Docker, HTTPS, Datenbankauswahl und die benutzerdefinierte Bereitstellung unter ZimaOS.
Bitwarden requirements at a glance
Bitwarden has two very different official self-hosting profiles. Bitwarden Lite is a single-container option for personal users and home labs, while the standard Linux deployment is the supported path for business environments. Size the host for the profile you actually run, plus the database, reverse proxy, backups, and other ZimaOS apps sharing the machine.
- Deployment
- Bitwarden Lite: single-container deployment for personal use and home labs. Standard Linux: multi-container deployment intended for broader production and business use.
- CPU
- Standard Linux minimum: x64 1.4 GHz; recommended: x64 2 GHz dual core. Bitwarden Lite does not publish a numerical CPU minimum.
- RAM
- Bitwarden Lite: at least 200 MB. Standard Linux: 2 GB minimum and 4 GB recommended.
- Storage
- Bitwarden Lite: at least 1 GB. Standard Linux: 12 GB minimum and 25 GB recommended, before allowing for host OS, backups, logs, attachments, and other services.
- GPU
- No GPU is required for Bitwarden password-vault hosting. Spend budget on reliable storage, memory headroom, HTTPS, backups, and host availability instead.
- Best Zima starting point
- ZimaBoard 2 832 is already ample for a personal Bitwarden Lite server. Choose ZimaBoard 2 1664 or ZimaCube 2 when Bitwarden shares the host with more databases, reverse proxies, backups, or other self-hosted services.
From official requirements to the right setup
Choose the Bitwarden deployment model first, then size the whole host around the database, persistent data, network exposure, backups, and co-hosted services rather than treating one RAM number as universal.
-
Official requirements
Separate Bitwarden Lite from the standard deployment. Lite officially requires at least 200 MB RAM and 1 GB storage and is intended for personal and home-lab use; the standard Linux deployment lists an x64 1.4 GHz CPU, 2 GB RAM, and 12 GB storage as minimums.
-
Confirm your needs
Choose the database and persistence model. Lite can use SQLite, PostgreSQL, MySQL/MariaDB, or MSSQL, but database maintenance and backups are your responsibility. Standard deployments ship with their own MSSQL-based stack by default.
-
Leave room to grow
Add whole-host headroom for ZimaOS, Docker, reverse proxy, TLS, backups, logs, attachments, and every other app sharing the server. The smallest container minimum is not a safe whole-server sizing target.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App rather than claiming one-click App Store support. Import an adapted Bitwarden Docker/Compose configuration, persist the required volumes, verify HTTPS and WebSocket access, then monitor memory, disk growth, and backup success before upgrading hardware.
Check every playback client
- Bitwarden Lite or standard deployment
- Personal/home-lab use or business/organization use
- SQLite, PostgreSQL, MySQL/MariaDB, or MSSQL database choice
- Persistent application and database volumes
- HTTPS certificate and reverse-proxy plan
- WebSocket connectivity for Bitwarden clients
- Backup and restore plan for database and persistent data
- Other ZimaOS apps and services sharing the host
Official minimum requirements
Bitwarden publishes separate official requirements for Lite and standard Linux self-hosting. These figures are not interchangeable: Lite is deliberately optimized for personal and home-lab use, while the standard stack carries higher host requirements and is the appropriate route for businesses.
For a ZimaOS home server, Bitwarden Lite is the most practical official custom-install target when the workload is personal or home-lab use. Do not apply its 200 MB container minimum to the standard stack, and do not treat standard deployment requirements as evidence that Lite needs several gigabytes of RAM.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Lite intended use | Personal users and home labs | Bitwarden states that Lite is not intended for business contexts; businesses should use a standard deployment option. |
| Lite RAM | At least 200 MB | This is the Bitwarden Lite container requirement, not a whole-host recommendation for ZimaOS plus databases and other services. |
| Lite storage | At least 1 GB | Allow additional capacity for the selected database, persistent vault data, attachments, logs, backups, and host growth. |
| Standard Linux CPU | x64 1.4 GHz minimum; x64 2 GHz dual core recommended | These figures apply to the official standard/manual Linux self-host deployment rather than Lite. |
| Standard Linux RAM | 2 GB minimum; 4 GB recommended | This covers the Bitwarden standard server stack baseline; whole-host sizing must still include ZimaOS and co-hosted services. |
| Standard Linux storage | 12 GB minimum; 25 GB recommended | Use durable storage with additional room for updates, logs, database growth, backups, and host-level data. |
| Docker | Docker Engine 26+ | Current Bitwarden Lite and standard Linux documentation require Docker Engine 26 or newer; Compose requirements depend on the deployment method. |
When to upgrade your hardware
Bitwarden itself is rarely compute-heavy. Upgrade when the deployment model or the surrounding server workload changes, not because password count alone crosses an arbitrary threshold.
You move from Lite to the standard deployment
Bitwarden shares the host with more services
Persistent data and backup work keep growing
Reverse proxies, databases, monitoring, backups, file services, photo platforms, and other containers can consume more RAM and I/O than Bitwarden itself. Whole-host pressure is a stronger upgrade signal than the vault process in isolation.
ZimaOS users consolidating multiple self-hosted apps on one server.Database size, attachments, logs, backup retention, snapshots, and restore windows can make storage capacity and I/O the practical bottleneck even when CPU usage remains low.
Long-running deployments, larger organizations, and users keeping attachments or multiple backup copies.Plan hardware growth with confidence
Scale the layer that is actually under pressure. Bitwarden does not benefit from a GPU, so most growth decisions are about deployment profile, database operations, durable storage, and whole-host headroom.
Keep personal deployments on Bitwarden Lite
Lite uses one official Bitwarden container and is explicitly aimed at personal and home-lab use, reducing the compute and memory footprint compared with the standard stack.
ZimaBoard 2 832 already provides substantial CPU and RAM headroom for Lite; size persistent storage and backups separately.Choose the database deliberately
Lite supports SQLite, PostgreSQL, MySQL/MariaDB, and MSSQL. A separate database can improve operational fit for some environments, but it also adds another service to update, monitor, back up, and restore.
Use SSD-backed persistent storage and leave extra RAM for an external database service when you intentionally add one.Move persistent data and backups off the smallest system volume
The official storage minimum is only an application baseline. Keep the live database, persistent data, and backup copies on storage with enough capacity and a tested recovery path.
Use SATA SSD or ZimaCube storage expansion when the installation, attachments, logs, snapshots, or backup retention outgrow the onboard system disk.Upgrade the host for consolidation, not GPU acceleration
Choose more memory, storage, and CPU only when Bitwarden is part of a larger self-hosted stack or when you adopt the standard deployment. Password-vault hosting does not require dedicated graphics.
ZimaBoard 2 1664 adds memory headroom; ZimaCube 2 adds stronger platform and storage capacity for a broader always-on service stack.Can it run on ZimaOS?
Bitwarden is not currently offered as a one-click ZimaOS App Store app. You can still run the official Bitwarden server on ZimaOS through Install Custom App; for personal and home-lab use, Bitwarden Lite is the cleaner official container target.
Custom install Bitwarden in ZimaOS
Open the ZimaOS dashboard and use Install Custom App to import an adapted Docker Compose/YAML configuration for Bitwarden. For a home server, the official ghcr.io/bitwarden/lite image is the simplest fit. Persist /etc/bitwarden and the selected database, then verify ports, environment variables, and the required Bitwarden installation key before launch.
Custom install Bitwarden in the ZimaOS app ↗Use Bitwarden Lite for personal and home-lab deployments
Bitwarden Lite is an official single-container deployment with a 200 MB RAM and 1 GB storage minimum. Bitwarden states that it is intended for personal users and home labs rather than business contexts.
Read Bitwarden Lite deployment requirements ↗Keep HTTPS and WebSocket access working
Self-hosted Bitwarden requires HTTP and HTTPS traffic and relies on WebSocket connectivity. If you place Bitwarden behind a reverse proxy, confirm the proxy, certificates, port mappings, and WebSocket handling before exposing the vault remotely.
Review Bitwarden networking requirements ↗Choose Zima hardware for Bitwarden
For Bitwarden, deployment type and whole-host consolidation matter more than raw compute. Lite is small enough for ZimaBoard 2 832; choose larger Zima systems when you run the standard stack, add databases and backups, or consolidate many always-on services.
Are you running Bitwarden Lite for personal/home-lab use, or a larger standard/consolidated server stack?
Personal or home-lab Bitwarden Lite
Bitwarden Lite has a very small official floor, so ZimaBoard 2 is chosen for reliable whole-host headroom rather than because Bitwarden needs 8–16 GB itself.
- Best starting pointZimaBoard 2 832
- More room for companion appsZimaBoard 2 1664
Standard Bitwarden or a larger multi-service host
Use more memory and storage headroom for the standard stack, external databases, reverse proxy, backups, monitoring, and other self-hosted services.
- Compact higher-headroom hostZimaBoard 2 1664
- Storage and service consolidationZimaCube 2 Standard
These are workload-based Zima recommendations, not Bitwarden performance guarantees. Actual use depends on deployment type, database engine, users, attachments, TLS/proxy setup, backup retention, update behavior, and other applications sharing the host.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Personal Bitwarden Lite, a reverse proxy, backups, and a few lightweight companion services. | Official Bitwarden Lite container with SQLite or another modest database setup, HTTPS proxying, regular backups, and ordinary ZimaOS services. |
|
The 32 GB eMMC is far above Bitwarden Lite's 1 GB app minimum but is not ideal as the only long-term location for OS, live database, logs, and backups. Add durable SATA storage and keep an independent backup. | Get Now |
| ZimaBoard 2 1664 | Bitwarden plus more ZimaOS services, an external database, or the standard Linux server stack with extra host headroom. | Bitwarden Lite or standard deployment alongside reverse proxy, database, monitoring, backup jobs, and additional self-hosted applications. |
|
Sixteen gigabytes is for whole-host consolidation, not a Bitwarden requirement. Use persistent SATA/SSD storage for important application data and backups rather than relying only on the onboard eMMC. | Get Now |
| ZimaCube 2 Standard | A broader always-on self-hosted platform where Bitwarden is one service among databases, backups, storage, media, and productivity apps. | Standard Bitwarden or Lite plus many other containers, multi-drive backup retention, snapshots, and larger shared storage requirements. |
|
ZimaCube 2 Standard is unnecessary for Bitwarden alone. Choose it when the wider server stack, backup design, or storage layout—not the password vault process—justifies the larger platform. | 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 questions cover the main Bitwarden hardware search intents: Lite versus standard requirements, RAM, CPU, storage, GPU, SSD use, HTTPS, ZimaBoard sizing, and what the published minimums actually include.
How much RAM does Bitwarden need?
It depends on the official deployment profile. Bitwarden Lite requires at least 200 MB RAM and is intended for personal users and home labs. The standard Linux deployment lists 2 GB RAM as the minimum and 4 GB as recommended. Add host headroom for ZimaOS, Docker, the database, reverse proxy, backups, and any other containers.
Can Bitwarden run on 1 GB or 2 GB RAM?
Bitwarden Lite can fit within a 1 GB host more plausibly because its official container minimum is only 200 MB, but the whole system still needs memory for the OS, Docker, database, proxy, and maintenance tasks. The standard Linux deployment officially starts at 2 GB RAM, so 2 GB should be treated as the floor rather than a comfortable multi-service ZimaOS target.
Does Bitwarden need a GPU?
No. Bitwarden password-vault hosting does not require GPU acceleration. CPU, RAM, durable storage, HTTPS, database reliability, and backups matter far more than graphics hardware.
How much storage does Bitwarden need?
Bitwarden Lite lists at least 1 GB storage. The standard Linux deployment lists 12 GB minimum and 25 GB recommended. Those figures are application baselines; real host capacity must also cover ZimaOS, Docker images, database growth, attachments, logs, updates, snapshots, and backup retention.
What is the difference between Bitwarden Lite and standard self-hosting?
Bitwarden Lite is an official single-container deployment designed to reduce CPU and memory use and is intended for personal users and home labs. It can use SQLite, PostgreSQL, MySQL/MariaDB, or MSSQL, but you manage the database. Standard self-hosting uses the larger official server stack and is the path Bitwarden directs businesses to use.
Does Bitwarden need an SSD?
Bitwarden does not publish SSD as a strict minimum, but SSD-backed persistent storage is a sensible practical choice for the live database, Docker data, updates, and reliable backups. HDDs are better suited to secondary backup capacity than to the main small transactional database when an SSD is available.
Can ZimaBoard 2 run Bitwarden?
Yes. ZimaBoard 2 uses an x86 Intel N150 and offers 8 GB or 16 GB RAM, which is well above Bitwarden Lite's official 200 MB minimum and also above the standard Linux deployment's 4 GB recommended RAM. For important vault data, add durable SATA SSD storage and maintain a separate tested backup instead of treating onboard eMMC as the only copy.
Does self-hosted Bitwarden require HTTPS?
Self-hosted Bitwarden expects HTTP and HTTPS traffic, with default ports 80 and 443 for standard deployments, and Bitwarden clients also require WebSocket connectivity. When using ZimaOS Install Custom App behind a reverse proxy, verify certificate handling, port mappings, and WebSocket forwarding before relying on remote access.
What sources informed this Bitwarden hardware guide?
Bitwarden's current official self-host documentation was used to separate Lite from standard deployment requirements and to verify networking behavior. Current Zima product pages were used only for Zima hardware specifications and workload matching; they are not treated as Bitwarden minimum requirements.
