Vaultwarden
Lightweight server compatible with Bitwarden clients.
Small and undemanding. The hard requirements are tested backups and reachability when you are away from home.
Planning figures used by the calculators: RAM 0.25 GB (our estimate), CPU 0.25 cores (our estimate), storage 1 GB (our estimate). These cover the application itself. Your own photos, films, documents and recordings are entered separately as data storage.
The table lists every figure we hold, what kind of claim it is, and the fragment of the archived document it came from.
Source: Vaultwarden container image guide, retrieved 2026-09-08, archived as document 19 on the sources page.
Add Vaultwarden to a stack or read how we label a number.
| property | value | basis | evidence | document |
|---|---|---|---|---|
| architecture | Multi-arch image, runs on Raspberry Pi 2 or newer | vendor documented | Quoted from the archived document: The `vaultwarden/server` image is also multi-arch, meaning it supports multiple CPU architectures under a single image name. | Document 19, retrieved 2026-09-08 |
| cpu plan cores | 0.25 cores | our estimate | Our reasoning: No published figure. Password vault sync is bursty and short; a quarter of a core is our planning share. | No document, our reasoning only |
| ram plan gb | 0.25 GB | our estimate | Our reasoning: The project publishes no sizing figures. A single Rust binary with SQLite for a household; we plan 256 MB. Measure your own instance before trusting this. | No document, our reasoning only |
| storage plan gb | 1 GB | our estimate | Our reasoning: No published figure. Vault data is small; attachments grow it. We plan 1 GB. | No document, our reasoning only |