A full Bitcoin node, external LND/CLN, explorers, databases and other services can consume far more storage/RAM than Alby Hub itself.
Users consolidating a sovereign Bitcoin/Lightning server.Requisiti hardware di Alby Hub: RAM, archiviazione, disponibilità e backup
Scopri i requisiti di RAM, disco, swap, operatività 24/7, porta Lightning e backup di Alby Hub, quindi scegli l’hardware ZimaOS più adatto.
Alby Hub requirements at a glance
Alby Hub publishes deployment-specific resource guidance. The current Docker guide lists 512 MB RAM minimum with 1 GB recommended, 1 GB swap with 2 GB recommended on smaller servers, and at least 1 GB storage. Alby's current installation reference is more conservative for the default embedded LDK backend: 2 GB RAM, or 512 MB RAM plus 2 GB swap. When Alby Hub connects to an external Lightning backend, the Hub layer can be much lighter.
- RAM - Docker
- Current official Docker guidance: 512 MB minimum, 1 GB recommended.
- RAM - embedded LDK
- Current project installation reference recommends 2 GB RAM for the default internal LDK node, or 512 MB RAM plus 2 GB swap.
- RAM - external node
- When connected to an external Lightning backend, current project guidance says about 256 MB RAM can be enough for the Alby Hub layer.
- Storage
- At least 1 GB is the documented baseline. Keep Hub data, keys, logs and Lightning state on a persistent volume with additional recovery headroom.
- Network / uptime
- Alby Hub is intended to run 24/7. Current installation guidance says Lightning port 9735 should be reachable for optimal channel connectivity.
- Best Zima starting point
- ZimaBoard 2 832 already exceeds all current Alby Hub RAM guidance by a wide margin. Higher Zima tiers are for a broader Bitcoin/Finance/self-hosted stack, not Hub compute.
From official requirements to the right setup
Alby Hub sizing starts with the Lightning backend and recovery model.
-
Official requirements
Choose the backend first. The default embedded LDK node carries the higher memory recommendation, while Alby Hub connected to an external node can run with much less RAM.
-
Confirm your needs
Plan an always-on deployment. Alby Hub is designed to stay online so connected apps, Lightning addresses and inbound payments can reach it; power and network reliability matter more than extra CPU cores.
-
Leave room to grow
Persist the Hub data directory and secure the recovery phrase. Lightning application state, keys and logs must survive container recreation or storage replacement.
-
Run it on ZimaOS
Install Alby Hub from ZimaOS, verify the selected backend, Lightning connectivity, channel/backup status and a documented recovery procedure before placing meaningful funds on the node.
Check every playback client
- Embedded LDK versus external Lightning backend
- 512 MB minimum / 1 GB Docker recommendation
- 2 GB LDK conservative recommendation or swap strategy
- At least 1 GB persistent storage
- 24/7 power and network reliability
- Lightning port 9735 reachability
- 12-word recovery phrase stored offline
- Channel-backup / recovery configuration
Official minimum requirements
Alby Hub has explicit current resource guidance, but the figures differ by deployment/backend and should not be collapsed into one number.
For a ZimaOS Docker deployment, 512 MB RAM is the current Docker minimum and 1 GB is recommended. For the default embedded LDK node, keeping roughly 2 GB available is the more conservative official target; external-node mode can be much lighter.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Docker RAM minimum | 512 MB | Current Alby Hub Docker guide. |
| Docker RAM recommended | 1 GB | Current Alby Hub Docker guide. |
| Swap | 1 GB minimum; 2 GB recommended on smaller servers | Current Docker guidance. |
| Embedded LDK conservative RAM | 2 GB, or 512 MB + 2 GB swap | Current project installation reference for the default backend. |
| External-node Hub RAM | About 256 MB | Project guidance when Alby Hub connects to an external Lightning node. |
| Storage | At least 1 GB | Persist Lightning/application state and leave extra room for logs/backups. |
When to upgrade your hardware
Alby Hub rarely needs a faster CPU; reliability, backend choice and surrounding services drive upgrades.
The same host runs a broader Bitcoin/Lightning stack
Memory pressure appears on an embedded LDK deployment
Power/storage reliability is not good enough for a wallet node
If a small host relies heavily on swap, moving from the 512 MB edge case toward 1–2 GB real RAM reduces swap dependence and leaves more room for container/OS overhead.
Very small VPS/SBC deployments close to the documented floor.A self-custodial wallet/node should prioritize persistent storage, backups and uptime. Replacing fragile storage or adding UPS/recovery can be more valuable than CPU upgrades.
Users holding meaningful Lightning/on-chain balances.Plan hardware growth with confidence
Scale Alby Hub by improving uptime and recovery before buying more compute.
Use real RAM instead of depending on swap when possible
Alby's Docker guide permits low-memory operation with swap, while the project installation reference gives a more conservative 2 GB recommendation for embedded LDK.
ZimaBoard 2 832's 8 GB RAM makes swap-based sizing irrelevant for a normal Hub.Keep the work/data directory on reliable persistent storage
Alby Hub's Docker/project guidance requires a persistent volume because Lightning and application state are stored to disk.
Use reliable eMMC/SSD/SATA storage and include Hub state in a broader recovery strategy.Back up the 12-word recovery phrase offline
Current Alby Hub recovery guidance instructs users to back up the recovery phrase; it is fundamental to wallet recovery.
Do not keep the only recovery phrase inside the same ZimaOS machine or backup volume.Use channel backups/recovery features for Lightning state
Alby's current documentation distinguishes the recovery phrase from Lightning channel-backup mechanisms and offers encrypted dynamic channel backups for supported recovery scenarios.
A RAID array or larger NAS is not a substitute for the wallet's documented cryptographic/channel recovery process.Can it run on ZimaOS?
Alby Hub is currently listed in the ZimaOS App Store under Finance.
Install Alby Hub from the ZimaOS App Store
Use the packaged self-custodial Lightning wallet/node and keep the application data volume persistent.
Open Alby Hub in the ZimaOS App StoreSize the Docker deployment from Alby's current guide
The current Docker guide gives 512 MB minimum / 1 GB recommended RAM, swap guidance and at least 1 GB storage.
Read Alby Hub Docker guidanceTreat backup/recovery as part of the hardware page
Because Alby Hub is a self-custodial wallet/node, a hardware recommendation is incomplete without an offline recovery phrase and a Lightning channel-recovery plan.
Read Alby Hub backup and recovery guidanceChoose Zima hardware for Alby Hub
Alby Hub is lightweight enough that ZimaBoard 2 832 already offers very large resource headroom. Reliability and recovery matter more than higher CPU tiers.
Is this a standalone Alby Hub or part of a larger Bitcoin/Finance server?
Standalone embedded-LDK or external-node Alby Hub
ZimaBoard 2 832 exceeds the documented Hub requirements by a wide margin.
- Normal always-on Alby HubZimaBoard 2 832
- Hub plus more Finance/network servicesZimaBoard 2 1664
Larger Bitcoin/Finance/storage platform
Move to ZimaCube only when other node/storage/backup services justify the larger platform.
- Integrated Finance/Bitcoin storage serverZimaCube 2 Standard
Meeting the documented RAM/disk baseline does not guarantee payment availability or fund safety. Lightning liquidity, backend configuration, network uptime, recovery phrase/channel backups and software updates all matter.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A normal self-hosted Alby Hub with embedded LDK or external Lightning backend. | 24/7 Lightning wallet/node connectivity, NWC apps and persistent Hub state. |
|
8 GB RAM is far above Alby's current 512 MB–2 GB guidance; uptime, backups and storage reliability matter more. | Get Now |
| ZimaBoard 2 1664 | Alby Hub plus more Bitcoin, Networking and Finance services. | A larger always-on sovereign-computing stack on one compact host. |
|
16 GB is for surrounding services; Alby Hub itself does not require this memory tier. | Get Now |
| ZimaCube 2 Standard | An all-in-one personal cloud also running Alby Hub and larger backup/storage workloads. | Finance apps, backups and other self-hosted services with multi-drive capacity. |
|
Choose ZimaCube for the wider server platform, not because Alby Hub needs a Core i3 or six drive bays. | 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
FAQ topics follow query fan-out around 512 MB/1 GB/2 GB RAM, embedded LDK versus external nodes, swap, 24/7 uptime, port 9735 and wallet/channel recovery.
How much RAM does Alby Hub need?
For the current Docker deployment, Alby documents 512 MB minimum and 1 GB recommended. A separate current installation reference gives a more conservative 2 GB recommendation for the default embedded LDK backend, or 512 MB plus 2 GB swap.
Why do Alby Hub docs mention 512 MB, 1 GB and 2 GB RAM?
They describe different operating margins and deployment guidance. 512 MB is the Docker minimum, 1 GB is the Docker recommendation, and 2 GB is the more conservative recommendation for the internal LDK backend without relying on swap.
Does Alby Hub need less RAM with an external Lightning node?
Yes. Alby's project guidance says the Hub layer can use about 256 MB RAM when it connects to an external backend because the Lightning node itself runs elsewhere.
Does Alby Hub need to run 24/7?
Ideally yes. The official project says it should run continuously so connected apps, Lightning addresses and incoming payments can reach it.
Should port 9735 be open for Alby Hub?
Alby's current installation reference says Lightning port 9735 should be open and reachable for optimal channel connectivity. Exact networking still depends on backend and deployment.
Can swap replace RAM for Alby Hub?
Alby's documentation explicitly supports low-memory configurations with swap, such as 512 MB RAM plus roughly 2 GB swap for the default backend. On ZimaBoard 2 with 8 GB RAM, there is no reason to target that edge-case setup.
Is the 12-word recovery phrase enough to recover Alby Hub?
It is essential, but Lightning recovery deserves separate attention. Current Alby documentation distinguishes wallet recovery from channel-backup mechanisms and offers encrypted dynamic channel backups for supported recovery scenarios.
Can ZimaBoard 2 832 run Alby Hub?
Yes. Its 8 GB RAM is multiple times higher than even Alby's conservative embedded-LDK recommendation, and its always-on server form factor is a better fit than sizing around the minimum 512 MB case.
What sources and further reading informed this Alby Hub hardware guide?
Alby's current Docker and project installation documentation provides the 512 MB/1 GB/2 GB RAM, swap, disk and port-9735 guidance. The official repository confirms persistent SQLite/application state and backend differences. Current backup/recovery docs define the recovery-phrase and channel-backup model. ZimaOS confirms the current Finance app.
