# Node hardware options > Source: https://timechain.wiki/wiki/node-hardware-options · TimechainWiki, the Bitcoin encyclopedia. (note · self-custody) > The 2026 landscape for running a Bitcoin full node spans four main approaches: **Umbrel** ($60-300 hardware bundles or DIY) — the most consumer-friendly plug-and-play platform; **Start9 Embassy** ($300-800 bundles or DIY) — a sovereignty-focused alternative with strong privacy defaults; **Raspiblitz** (DIY on Raspberry Pi 4/5, ~$150 in parts) — open-source and community-driven; and **custom Bitcoin Core builds** on existing hardware — for the technically inclined. Platform choice tracks technical comfort, sovereignty posture, and budget rather than brand loyalty. Tier 1-2 holders typically benefit from Umbrel or Start9: faster setup, integrated services (Electrum server, Lightning, BTCPay, mempool.space), and sane defaults. Start9 is structurally preferable where minimum-third-party-dependency posture matters; Raspiblitz and custom builds offer maximum control for the DIY-inclined. See [Running a full node](https://timechain.wiki/wiki/running-a-full-node.md) for the framework on whether to run one at all. --- ## Why this note matters The platform choice for running a full node is sometimes treated as a brand-loyalty question; the synthesis treats it as a fit-to-purpose question. The note matters because: - It establishes the **comparative landscape** as of 2026, which has stabilized around the four approaches above - It clarifies the **sovereignty vs UX trade-off** — Umbrel is friendlier; Start9 is more sovereignty-aligned; both work - It provides the **selection criteria** for the holder's specific situation --- ## What this is A "node hardware option" is the combination of: - **Hardware** — a small computer to run the node software - **Operating system / platform** — the software stack that manages the node and ancillary services - **Storage** — the disk space for the blockchain - **Network** — the connection to the Bitcoin network The four mainstream approaches in 2026: ### Umbrel **Vendor**: Umbrel (umbrel.com); founded by Mayank Chhabra. Open-source. **Hardware options**: - **Umbrel Home** ($300+) — pre-built dedicated device (Intel NUC-class hardware) - **DIY on Raspberry Pi** ($60-150 in parts; Umbrel publishes the parts list) - **Existing hardware** — Umbrel OS installs on most Linux-compatible machines **Platform**: Umbrel OS — Linux-based, with the Umbrel app store providing Bitcoin Core, Electrs, Lightning (LND), BTCPay, mempool.space, Sparrow Server, and dozens of other services in one-click installation **Distinguishing features**: - The most consumer-friendly UX in the space - App-store paradigm — install services with a click - Active development; frequent feature additions - The largest community of node operators **Trade-offs**: - Some defaults are convenience-first rather than sovereignty-first (e.g., the dashboard is accessed via a local web interface; Umbrel can route through their cloud service for remote access if the holder opts in) - The app store includes services that some sovereignty-aligned holders would not install (some are non-Bitcoin) - Closed-source components in some peripheral services (the core Bitcoin/Lightning is open-source) See [Umbrel](https://timechain.wiki/wiki/umbrel.md) for the full product treatment. ### Start9 Embassy **Vendor**: Start9 Labs (start9.com); founded by Aiden McClelland and Matt Hill. Open-source. **Hardware options**: - **Start9 Server One** ($700+) — dedicated server hardware; substantial computing power - **Start9 Server Pure** ($1000+) — premium hardware - **DIY on Raspberry Pi** — supported with the StartOS image - **Existing hardware** — StartOS supports various platforms **Platform**: StartOS — Linux-based, with explicit sovereignty design choices. The Marketplace includes Bitcoin Core, LND, BTCPay, and a curated set of services. **Distinguishing features**: - Sovereignty-first design philosophy - Minimum-third-party-dependency posture — everything is intended to run on the holder's hardware without cloud services - Tor by default; explicit privacy posture - Strong focus on reproducible builds and verified software **Trade-offs**: - Higher hardware cost than Umbrel options - Smaller community; fewer third-party services - The sovereignty-first defaults can feel paranoid to casual users - Active development but slower-paced than Umbrel See [Start9](https://timechain.wiki/wiki/start9.md) for the full product treatment. ### Raspiblitz **Vendor**: Raspiblitz community (raspiblitz.org); originally by Christian Rotzoll. Open-source, community-driven. **Hardware**: - DIY on Raspberry Pi 4 or 5; total parts cost ~$150-250 - The community publishes detailed build instructions **Platform**: Raspiblitz OS — purpose-built for Lightning operation; menu-driven configuration **Distinguishing features**: - Community-driven, no vendor lock-in - Lightning-focused; the project's heritage is in Lightning operation - Educational; the build process teaches the holder about node operation - Lowest-cost option for serious node operation **Trade-offs**: - DIY assembly required; not plug-and-play - The UX is less polished than Umbrel or Start9 - Community support varies; less guaranteed than commercial vendors - Performance limited by Raspberry Pi hardware (adequate but not high-performance) ### Custom builds Running Bitcoin Core directly on existing hardware (a Linux server, a Mac mini, a NAS device, a dedicated workstation). **Distinguishing features**: - Maximum control over the configuration - Can leverage existing hardware - No vendor in the loop at all - Best for holders who already operate Linux servers and want Bitcoin to join the stack **Trade-offs**: - Manual setup; manual maintenance - No integrated app-store experience - Requires more technical familiarity - No one to call for support --- ## Who each approach is for ### Umbrel A strong fit for: - **First-time node operators** — the UX is the most approachable in the space - **Multi-service users** — users who want Bitcoin Core + Lightning + BTCPay + mempool.space + Sparrow Server all running together - **Plug-and-play preference** — users who want to buy hardware and have it work out-of-the-box - **Active operators** — users who will use the dashboard regularly and benefit from the polished UX ### Start9 A strong fit for: - **Sovereignty-aligned users** — the design philosophy matches the strongest self-custody stance - **Privacy-conscious users** — Tor-by-default; minimum third-party dependencies - **Users willing to pay for the design** — the hardware is more expensive but the experience is differentiated - **Users who would otherwise build custom** — Start9 provides much of the custom-build benefit with less setup cost ### Raspiblitz A strong fit for: - **DIY-inclined users** — the build process is part of the value - **Budget-constrained users** — lowest total cost - **Lightning-focused users** — the project's heritage is Lightning - **Educational users** — learning happens through the setup ### Custom builds A strong fit for: - **Technical users** — who already operate Linux servers - **Existing-hardware users** — leveraging a NAS or home server - **Maximum-control users** — who want to choose every component of the stack - **Holders running other services** — Bitcoin Core joins an existing operational stack --- ## Comparison | Dimension | Umbrel | Start9 | Raspiblitz | Custom | |---|---|---|---|---| | Setup cost | $60-300 | $300-1000 | $150-250 | Variable (existing hardware) | | Setup time | 1-2 hours (after IBD) | 1-2 hours (after IBD) | 4-8 hours (assembly + IBD) | Variable | | UX | Best (app store paradigm) | Good (curated marketplace) | Adequate (menu-driven) | None (manual) | | Sovereignty | Good | Best (explicit philosophy) | Good (open-source) | Best (no vendor) | | Privacy defaults | Reasonable | Strong (Tor by default) | Reasonable | Manual | | Community size | Largest | Smaller | Medium | N/A (individual) | | Third-party services | Largest app store | Curated marketplace | Limited | Manual install | | Lightning support | Excellent | Good | Excellent (the heritage) | Manual setup | | Update mechanism | Push from Umbrel | Push from Start9 | Manual or scripted | Manual | | Hardware lock-in | None (DIY supported) | None (DIY supported) | None | None | For most Tier 1-2 holders, Umbrel or Start9 is the right choice. The decision between them is largely about sovereignty preference vs UX preference. For DIY-inclined holders, Raspiblitz or custom builds are reasonable. --- ## Specific configuration notes ### Storage The Bitcoin blockchain is ~700 GB as of 2026-05-14 and grows ~50 GB/year. Storage planning: - **Minimum**: 1 TB SSD (provides multi-year headroom) - **Recommended**: 2 TB SSD (provides decade+ headroom) - **High-performance**: NVMe SSD (faster IBD; faster wallet queries) Spinning hard drives work but are substantially slower for the random-access patterns Bitcoin Core uses. SSD is the standard for any serious node operation. ### Memory - **Minimum**: 4 GB RAM (Raspberry Pi 4 with 4 GB works for basic operation) - **Recommended**: 8 GB RAM (better performance; smoother IBD) - **High-performance**: 16 GB+ (faster IBD; multiple-service operation) ### Network - **Bandwidth**: 5 GB/month upload + download is typical for a non-promiscuous node; 50+ GB/month for nodes serving more peers - **Connection stability**: persistent residential connections are fine; mobile/tethered connections are inappropriate - **NAT/firewall**: incoming connections (allowing others to query your node) require port-forwarding configuration; outgoing-only is fine for basic operation ### Power - **Raspberry Pi-class hardware**: 5-15 watts continuous - **Dedicated server hardware** (Umbrel Home, Start9): 20-50 watts continuous - **Annual electricity cost**: $5-50 depending on hardware and local rates The total operational cost of a node is small. The capital cost ($60-1000 depending on platform) is the principal investment. --- ## Tradeoffs and considerations ### The Umbrel vs Start9 debate This is the most-discussed comparison in the space. The summary: - **Umbrel**: friendlier UX; larger ecosystem; some convenience-first defaults - **Start9**: stronger sovereignty defaults; smaller ecosystem; sovereignty-first philosophy Both are open-source. Both work. The right choice depends on the holder's preferences: - "I want my node to just work and be easy to use" → Umbrel - "I want my node to embody the strongest sovereignty stance" → Start9 For holders without strong preferences either way, Umbrel's accessibility makes it the marginal default; Start9 is the upgrade for those who specifically value the sovereignty posture. ### The "do I need a Lightning node?" question Many node platforms bundle Lightning. The decision: - **If you want to actively use Lightning**: yes, run a Lightning node; the bundled platforms handle this - **If you're Bitcoin-only**: no Lightning is needed; the Bitcoin Core + Electrs configuration is sufficient - **If you're undecided**: the bundled platforms make adding Lightning later straightforward; install Bitcoin Core first, add Lightning when ready ### The remote-access question How do you reach your node when you're not at home? Options: - **Local access only** — the node is accessible only on the home network; convenient but limiting - **VPN to home network** — secure; requires VPN setup - **Tor hidden service** — Start9 defaults to this; Umbrel supports it; provides remote access without exposing the IP - **Vendor cloud relay** (Umbrel) — Umbrel offers a relay service for remote access; convenient but introduces a vendor dependency For sovereignty-aligned holders, Tor is the standard. For convenience-first users, VPN or vendor relay is reasonable. ### Hardware longevity Node hardware should last 5-10 years; the operating environment (low power, low heat, indoor) is gentle. The principal failure modes: - **SSD wear-out**: SSDs have finite write cycles; for node operation, this is typically not a binding constraint over 10 years - **Power-supply failure**: more common than other failures; replaceable - **Network-interface failure**: rare - **Capacitor aging**: real over decade horizons For Tier 2+ holders, redundancy considerations (running two nodes; having spare hardware) may be appropriate. --- ## Tiered application **Tier 0:** A node is generally optional. If running one, Raspiblitz DIY is the cheapest entry point; Umbrel is the smoothest. **Tier 1:** Umbrel or Start9 are appropriate. The platform investment is one-time; the operational benefit accrues. **Tier 2:** Start9 is structurally preferable if sovereignty alignment matters; Umbrel works. For Lightning operation, consider Raspiblitz's Lightning heritage. **Tier 3:** Multiple nodes at multiple locations (redundancy and privacy); possibly mixed platforms (Start9 at primary; Umbrel as secondary); Tor by default; explicit privacy configuration. --- ## Common pitfalls **Buying hardware before deciding on the platform.** The platform shapes the hardware requirements. Decide platform first; buy hardware to match. **Underestimating storage.** A node that fits today's chain barely fits 2-3 years from now. Plan with 5+ year headroom. **Using spinning disks for the chain.** Performance is meaningfully worse than SSD; the IBD takes substantially longer. SSD is the standard. **Co-locating the node with everyday-use computer.** The dedicated machine pattern is structurally cleaner. The synthesis doesn't recommend running a node on the holder's primary laptop. **Not configuring Tor.** For the sovereignty benefit, Tor is the standard. Umbrel makes it easy; Start9 defaults to it. Skipping Tor undermines part of the node's purpose. **Treating the node platform as a security boundary.** The platform provides the operating environment; the security depends on the platform's defaults, the holder's configuration, and the broader operational discipline. Umbrel or Start9 is not a substitute for good opsec. **Forgetting to back up the node configuration.** Lightning channels, wallet configurations, and app data are not trivially recoverable without backup. Both Umbrel and Start9 provide backup mechanisms; use them. **Operating the node on an unstable network.** Frequent connectivity drops degrade the node's value. A stable wired connection is the standard; flaky Wi-Fi is suboptimal. --- ## Tooling and resources **Vendor documentation**: - **Umbrel**: umbrel.com; comprehensive docs; large community - **Start9**: start9.com; sovereignty-focused docs - **Raspiblitz**: raspiblitz.org; community-driven - **Bitcoin Core**: bitcoincore.org **Community resources**: - The respective subreddits and Discord servers for each platform - *Mastering Bitcoin*, Andreas Antonopoulos (3rd ed., 2023) — covers node operation generally - Various Bitcoin community tutorials **The synthesis document**: *Bitcoin Self-Custody & Security* (LegacyCipher, April 2026) — node hardware treated as part of the sovereignty layer. _As of 2026-05-14_: the platform landscape is stable. Umbrel and Start9 are both active; Raspiblitz remains community-driven. The choice between them is largely about user preference rather than technical capability. --- ## Open questions for further development - The Umbrel vs Start9 design-philosophy debate continues. As both platforms mature, will the gap narrow, or will they remain meaningfully different? - Lightning Network requirements are growing (channel size limits, Liquid sidechain integration, etc.). How will node platforms accommodate these? - The "node-as-a-service" pattern (running your node on a remote VPS) is sometimes proposed; the trade-offs are real but the sovereignty benefit is preserved at some level. Should the framework engage this category? - AssumeUTXO and faster sync mechanisms may reduce the IBD barrier. How will this affect platform choices and adoption rates? --- ## Related notes **The framing context**: - [Running a full node](https://timechain.wiki/wiki/running-a-full-node.md) — the framework on whether to run one at all - [Self-custody as a moral act](https://timechain.wiki/wiki/self-custody-as-a-moral-act.md) — node operation as a sovereignty practice **Specific platform notes**: - [Umbrel](https://timechain.wiki/wiki/umbrel.md) — the consumer-friendly platform - [Start9](https://timechain.wiki/wiki/start9.md) — the sovereignty-focused platform **Adjacent operational notes**: - [Connecting wallets to your own node](https://timechain.wiki/wiki/connecting-wallets-to-your-own-node.md) — the wallet-side configuration **Hardware wallets**: - [Hardware wallets overview](https://timechain.wiki/wiki/hardware-wallets-overview.md) — paired with the node for signing - All per-device notes work with custom-node configurations **Custody configurations**: - [Multisig setups](https://timechain.wiki/wiki/multisig-setups.md) — coordinators query the node as backend - [Collaborative custody services](https://timechain.wiki/wiki/collaborative-custody-services.md) **The technical foundations**: - [Bitcoin Core](https://timechain.wiki/wiki/bitcoin-core.md) **The principal practitioners**: - [Andreas Antonopoulos](https://timechain.wiki/wiki/andreas-antonopoulos.md) — *Mastering Bitcoin* covers node operation **The sub-MOC home**: - [Practical self-custody and sovereignty](https://timechain.wiki/wiki/practical-self-custody-and-sovereignty.md)