The official table increases database and app-server CPU/RAM at 500 and 1,000-user tiers.
Growing organizations.Requisiti hardware di Psono: RAM, CPU, PostgreSQL e file
Pianifica l’hardware per Psono utilizzando le stime ufficiali basate sugli utenti per CPU, RAM e disco, oltre alle indicazioni per l’implementazione di PostgreSQL, fileserver, SSL e ZimaOS.
Psono requirements at a glance
Psono is a password manager whose production guidance explicitly separates the database, app/client/admin service and optional fileserver/cache roles.
- <100-user database
- Official rough estimate: 1 CPU, 1.5 GB RAM and 20 GB disk.
- <100-user app server
- Official rough estimate: 1 CPU, 1 GB RAM and 10 GB disk.
- <500-user database
- Official rough estimate: 2 CPUs, 3 GB RAM and 20 GB disk; app server: 2 CPUs, 2 GB RAM and 10 GB.
- Database
- Production preparation calls for PostgreSQL 14, preferably the latest supported release.
- Domain and TLS
- A domain/subdomain and publicly trusted SSL certificate are hard requirements; IP-only or plain HTTP setups are unsupported.
- Best Zima starting point
- ZimaBoard 2 832 can host a small single-box lab deployment, but production-grade Psono should follow upstream separation of database and application roles.
From official requirements to the right setup
Use Psono's user-based component table and keep production role separation in mind.
-
Official requirements
Choose the target user tier. For fewer than 100 users, upstream estimates 1 CPU/1.5 GB/20 GB for PostgreSQL and 1 CPU/1 GB/10 GB for the application service.
-
Confirm your needs
For production, separate the database from the application; separate the fileserver as well when file storage is used, and add Redis for high-availability designs.
-
Leave room to grow
Provide PostgreSQL, a real domain/subdomain and a trusted SSL certificate. Psono explicitly does not support IP-only, HTTP or untrusted-certificate production setups.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with psono/psono-combo plus PostgreSQL for a small deployment, but do not present a single-host container stack as equivalent to Psono's production-grade separated architecture.
Check every playback client
- Expected users
- PostgreSQL role
- App/server role
- Fileserver needed
- Redis/HA needed
- Domain/subdomain
- Trusted TLS
- Backup retention
Official minimum requirements
Psono publishes rough component-level estimates by user count rather than a single combined server minimum.
Do not sum the table into a universal 'Psono minimum' without context. The estimates assume separate production roles, and actual usage can materially change resource needs.
| Requirement | Official minimum | What this supports |
|---|---|---|
| <100 users DB | 1 CPU / 1.5 GB RAM / 20 GB disk | Official rough estimate. |
| <100 users app server | 1 CPU / 1 GB RAM / 10 GB disk | Official rough estimate. |
| <500 users DB | 2 CPU / 3 GB RAM / 20 GB disk | Official rough estimate. |
| <500 users app server | 2 CPU / 2 GB RAM / 10 GB disk | Official rough estimate. |
| PostgreSQL | 14, preferably latest | Current software requirement. |
| Domain + trusted SSL | Hard requirement | IP, HTTP and untrusted certificates are unsupported. |
When to upgrade your hardware
Psono should scale by separating roles and adding resources as users, files or high availability requirements grow.
User count approaches the next sizing tier
Fileserver data or bandwidth expands
High availability becomes necessary
Psono recommends a separate fileserver to avoid storage and bandwidth contention.
Teams storing files or backups in Psono.HA adds multiple app servers and a central Redis cache in Psono's reference architecture.
Mission-critical deployments.Plan hardware growth with confidence
Scale Psono by separating database, files and high-availability roles before simply increasing one container's limits.
Keep PostgreSQL on dedicated durable storage
Upstream recommends separating the database for reliable restoration and easier scaling.
Use SSD-backed PostgreSQL storage.Use 8–16 GB for a small single-host lab
Provides room to run the combo container and PostgreSQL together for small/non-HA deployments.
ZimaBoard 2 832 or 1664.Use ZimaCube for fileserver capacity
Optional Psono fileserver storage can scale independently based on user file volume.
ZimaCube 2 Standard.Scale out for production HA
Psono's production guidance uses separate VMs/servers and Redis as user counts and availability needs rise.
Use multiple hosts/VMs rather than relying on one larger Zima box.Can it run on ZimaOS?
No public official ZimaOS one-click Psono App Store page was verified for this guide. Psono can be deployed through Install Custom App, but production-grade guidance favors role separation.
Custom install Psono in ZimaOS
Use Install Custom App with psono/psono-combo and PostgreSQL, persist settings/database data, and expose the service only behind a trusted HTTPS domain.
Custom install Psono in the ZimaOS app ↗Use Psono's official combo image
Psono CE provides psono/psono-combo:latest, which bundles the server, web client and admin portal; PostgreSQL remains a separate dependency.
Review Psono CE installation ↗Follow Psono's production topology guidance
Current preparation docs recommend separate database, app and fileserver roles and add Redis for HA.
Review Psono production requirements ↗Choose Zima hardware for Psono
Psono's small-user component estimates fit compact Zima hardware, but production architecture matters more than simply putting every role on one larger server.
Is this a small single-host deployment or a production environment that should follow role separation?
Small / non-HA deployment
Run the combo app plus PostgreSQL with durable storage and trusted HTTPS.
- Entry compact choiceZimaBoard 2 832
- More headroomZimaBoard 2 1664
Fileserver-heavy or production role separation
Use storage-capable hardware for files, but separate database/app/HA roles across VMs or hosts.
- Storage platformZimaCube 2 Standard
- Stronger VM hostZimaCube 2 Pro
Single-host Zima recommendations are practical lab/small-deployment options; they are not equivalent to Psono's production-grade separated and HA architectures.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small Psono single-host labs or small deployments. | psono-combo plus PostgreSQL for a modest user count. |
|
Combining roles is simpler but less aligned with upstream production separation guidance. | Get Now |
| ZimaBoard 2 1664 | Small Psono with more database/app headroom. | Psono combo, PostgreSQL and other modest services. |
|
16 GB provides headroom but does not create high availability. | Get Now |
| ZimaCube 2 Standard | Psono fileserver-heavy storage roles. | Optional encrypted file storage, backups and broader NAS duties. |
|
Use role separation for production rather than putting every Psono service on one host. | Get Now |
| ZimaCube 2 Pro | Stronger virtualization host for separated Psono roles. | Multiple VMs/containers, PostgreSQL, app services and broader infrastructure. |
|
True HA still requires independent failure domains, not multiple VMs on one physical server. | 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 Psono RAM, CPU, PostgreSQL, fileserver, TLS and ZimaOS deployment.
How much RAM does Psono need for fewer than 100 users?
Psono's rough production estimates allocate 1.5 GB RAM to the database VM and 1 GB RAM to the app-server VM, with optional fileserver resources separate.
How many CPU cores does Psono need for fewer than 100 users?
The rough estimate uses 1 CPU for the database and 1 CPU for the application server.
Which database does Psono require?
Current preparation guidance specifies PostgreSQL 14, preferably the latest supported version.
Does Psono require HTTPS?
Yes. A domain or subdomain with a publicly trusted SSL certificate is a hard requirement; IP-only and plain HTTP setups are unsupported.
Does Psono need a separate fileserver?
Only if you use file storage, but production guidance recommends separating it to avoid storage and bandwidth contention.
Does Psono need Redis?
Redis is not necessary for small deployments in the official table; it is introduced for high-availability setups.
Can ZimaBoard 2 run Psono?
Yes for a small single-host deployment, though production-grade Psono recommends separating database and application roles.
When should I use multiple hosts instead of a larger Zima box?
When high availability, role isolation or larger user/file workloads make Psono's separated production architecture important.
What sources informed this Psono hardware guide?
Current Psono production preparation, CE installation and PostgreSQL documentation plus current Zima product pages.
