# Choose the Right System for Homebridge (https://docs.homemanager-app.de/guide/choose-your-system)
Homebridge requires very little computing power. The software runs on Node.js and processes commands asynchronously on a single-threaded event loop. Running dozens of smart lights, switches, plugs, or blinds in Apple Home needs little more than an energy-efficient single-board computer drawing a few watts.
Before purchasing new hardware, check whether an existing system in your local network is already running 24/7.
***
## Technical Requirements in Practice [#technical-requirements-in-practice]
### Processor and Computing Power [#processor-and-computing-power]
Standard home automation tasks like polling sensors, switching relays, or broadcasting state updates generate minimal processor load. A basic ARM or x86 multi-core CPU usually hovers in the low single-digit percentage range.
Significant processing power is only required when IP cameras are involved. Transcoding real-time RTSP video streams into HomeKit-compliant H.264/SRTP formats (via plugins such as Camera FFmpeg or camera-ui) depends heavily on hardware-accelerated video decoding and encoding. On x86 systems, Intel Quick Sync Video (QSV) handles this; on Apple systems, the native VideoToolbox framework offloads the work. Without dedicated hardware acceleration, a single 1080p stream can saturate weaker CPUs entirely.
### Memory (RAM) [#memory-ram]
* 512 MB RAM is the absolute minimum (found on devices like the Raspberry Pi Zero 2 W). Installing certain plugins requires compiling native C/C++ modules (`node-gyp`), which regularly causes out-of-memory errors on 512 MB systems.
* 1 to 2 GB RAM provides a reliable baseline for standard installations. This is ample memory for the host OS, the Node.js runtime, and dozens of plugins.
* 4 GB RAM or more is recommended when running multiple plugins as isolated child bridges, integrating multiple cameras, or hosting additional network services on the same machine.
### Storage Media and 24/7 Endurance [#storage-media-and-247-endurance]
Homebridge and system logging daemons continuously write status updates and logs to disk. Inexpensive consumer microSD cards lack effective wear leveling and tend to fail prematurely under constant 24/7 write operations.
When using memory cards, choose cards rated A2 (Application Performance Class 2), which are designed for high parallel random read and write IOPS. Solid-state drives (SSDs) connected via USB 3.0, SATA, or NVMe offer significantly higher durability and faster plugin startup times.
### Network: Wired Ethernet over Wi-Fi [#network-wired-ethernet-over-wi-fi]
Homebridge relies on Multicast DNS (mDNS) and Bonjour (UDP port 5353) so that Apple Home hubs (Apple TV, HomePod) and iOS devices discover accessories across the local subnet without manual configuration.
Many Wi-Fi routers and mesh nodes filter, drop, or delay multicast packets over wireless connections due to aggressive power-saving or restrictive IGMP snooping. This causes sluggish response times or recurring "No Response" errors in Apple Home. A wired Ethernet connection to your router or switch eliminates this problem at the network level.
***
## Hardware Options in Detail [#hardware-options-in-detail]
### 1. Raspberry Pi: Dedicated Single-Board Computer for Continuous Operation [#1-raspberry-pi-dedicated-single-board-computer-for-continuous-operation]
If you have no existing server setup and want an independent, low-maintenance device, the Raspberry Pi is the most widely adopted platform.
At idle, a Raspberry Pi typically consumes 3 to 5 watts, amounting to roughly 10 to 15 euros in annual electricity costs. Paired with a passive aluminum case (such as from Flirc), the system operates completely silently.
The Raspberry Pi 4 (with 2 GB or 4 GB RAM) and Raspberry Pi 5 are the recommended models. Older generations like the Pi 3 Model B+ struggle with modern Node.js versions and demanding plugins. The Raspberry Pi Zero 2 W is constrained by its 512 MB RAM and lack of an Ethernet port, making it suitable only for minimal test setups.
A reliable power supply is essential: the official Raspberry Pi power supply delivers a steady 5.1 volts. Standard phone chargers often suffer voltage drops (undervoltage) during peak loads, leading to system crashes and filesystem corruption.
[Read Raspberry Pi Installation Guide](/guide/install-raspberry-pi)
***
### 2. Synology NAS: Integration with Existing Network Storage [#2-synology-nas-integration-with-existing-network-storage]
If you already run a Synology NAS for backups, network shares, or photos, it is usually the most cost-effective option. The hardware is already powered on, connected to your router, and occupies no additional physical space.
The official Homebridge package can be installed directly through the DSM Package Center. It supports almost all DiskStation models, including entry-level j-series units with ARM processors (such as the DS120j or DS220j).
On Plus-series DiskStations with x86-64 processors (Intel or AMD), you can alternatively run Homebridge in an isolated container using the Synology Container Manager (Docker).
For sensors, lights, and switches, any DiskStation model provides sufficient performance. However, smaller series CPUs lack the processing headroom for real-time video transcoding from IP cameras.
[Read Synology NAS Installation Guide](/guide/install-synology)
***
### 3. x86 Mini PC (e.g. Intel N100): Scalable Alternative [#3-x86-mini-pc-eg-intel-n100-scalable-alternative]
Compact x86 systems powered by processors like the Intel N100 or N95 are a practical alternative to single-board computers.
Complete mini PCs including a case, power supply, 8 to 16 GB RAM, and an M.2 NVMe SSD often cost little more than a fully outfitted Raspberry Pi 5 kit with accessories.
Modern Intel N100 systems consume only 6 to 9 watts at idle. Integrated Intel Quick Sync Video provides hardware acceleration capable of handling multiple camera streams concurrently without significant CPU utilization.
These systems are especially well-suited if you plan to run Homebridge on a full Linux distribution (Debian, Ubuntu) or a hypervisor like Proxmox VE alongside other services such as Pi-hole, AdGuard Home, or Home Assistant.
[Read Docker Installation Guide](/guide/install-docker)
***
### 4. Docker on Linux, Unraid, or Proxmox: Containerized Deployment [#4-docker-on-linux-unraid-or-proxmox-containerized-deployment]
On existing Linux servers, Unraid setups, or Proxmox hosts, running Homebridge as a Docker container is the cleanest integration path.
Homebridge, the Node.js runtime, and all dependencies remain isolated within the container. The host operating system remains untouched, and updates can be deployed predictably using Docker Compose.
Mandatory network configuration: the container must use host networking (`network_mode: host`). Standard Docker bridge networks isolate multicast traffic, preventing Bonjour packets from reaching the physical LAN and causing Apple Home to lose connection to the bridge.
[Read Docker Installation Guide](/guide/install-docker)
***
### 5. Mac (macOS): Dedicated Mac mini for Camera-Heavy Setups [#5-mac-macos-dedicated-mac-mini-for-camera-heavy-setups]
A stationary Mac mini works well for setups with video cameras, whereas laptops are impractical for 24/7 server operation.
A dedicated Mac mini (especially with Apple Silicon, M1 or newer) provides substantial compute capacity with an idle draw of just 7 to 15 watts. Utilizing Apple's hardware VideoToolbox framework, macOS decodes and encodes demanding camera streams for HomeKit Secure Video silently and efficiently.
MacBooks (Air and Pro) are unsuited for continuous server operation: closing the lid or entering system sleep cuts network connections and halts background processes, rendering accessories unreachable in Apple Home.
[Read macOS Installation Guide](/guide/install-macos)
***
### 6. Windows: Temporary Evaluation Environment [#6-windows-temporary-evaluation-environment]
Homebridge provides an official installer to set up the service directly on Windows as a background process.
A native Windows installation is primarily useful for initial testing to evaluate plugin compatibility and Apple Home integration before investing in dedicated hardware.
For continuous 24/7 operation, standard desktop PCs are impractical: their idle power draw of 30 to 60 watts leads to noticeable energy costs. Furthermore, automated reboots triggered by Windows Update interrupt service availability unexpectedly.
[Read Windows Installation Guide](/guide/install-windows)
***
## Installation Guides Overview [#installation-guides-overview]
[How to Install Homebridge](/guide/install-homebridge) shows which method fits your setup. Detailed step-by-step guides are available for each platform:
***
## Daily Administration: Homemanager App and Web Interface [#daily-administration-homemanager-app-and-web-interface]
Everyday management requires no ongoing terminal interaction. Both administration methods offer graphical interfaces.
### Homemanager on iOS and iPadOS [#homemanager-on-ios-and-ipados]
Homemanager was developed as a powerful, beginner-friendly mobile management app for iPhone and iPad to control Homebridge and HOOBS directly across your local network:
* **Multi-server support:** Manage multiple Homebridge and HOOBS instances from a single centralized view.
* **Over 4,000 community integrations:** Browse plugins, discover new hardware support, and install extensions directly on your device.
* **Configuration built for mobile:** Edit plugin settings through native forms instead of editing JSON brackets and commas manually.
* **Quick actions:** Trigger system reboots, software updates, and child bridge restarts without reloading the main instance.
* **Visual system status:** Check CPU load, memory usage, uptime, and bridge state at a glance.
* **Live logs and setup codes:** Inspect log output in real time and scan the HomeKit QR code directly from your screen.
* **Fair licensing:** A permanent free Starter license for small setups, alongside one-time lifetime licenses without monthly subscriptions.
### Web Interface in the Browser [#web-interface-in-the-browser]
The standard web interface (Homebridge Config UI X) is available on every system. Accessible locally on port 8581 (e.g. `http://homebridge.local:8581` or your server's IP address), it provides full administrative controls and is well suited for detailed desktop configuration work.
***
## Frequently Asked Questions [#frequently-asked-questions]
Yes. The Homebridge configuration is completely decoupled from the underlying hardware. You can export a full backup archive at any time through the web interface or the Homemanager app.
Restoring this backup on a new server (for instance, when migrating from a Raspberry Pi to a Synology NAS or mini PC) preserves all settings, plugin configurations, and HomeKit pairing records. You will not need to re-pair accessories or recreate rooms, scenes, and automations in Apple Home.
A Raspberry Pi 3 Model B+ handles simple setups with lights, smart plugs, and basic sensors adequately. With more demanding plugins or major Node.js upgrades, however, the quad-core CPU reaches its performance limits.
The Raspberry Pi Zero 2 W has only 512 MB RAM and lacks an Ethernet port. This regularly leads to out-of-memory errors during plugin installation and compilation. Additionally, operating purely over Wi-Fi introduces multicast discovery delays in Apple Home. For long-term reliability, a Raspberry Pi 4 with at least 2 GB RAM is strongly recommended.
Docker Desktop runs containers inside a lightweight Linux virtual machine. Host networking (`network_mode: host`) does not function identically to native Linux: virtual network adapters fail to pass multicast traffic (mDNS and Bonjour) transparently to the physical local network.
As a result, Apple Home frequently loses connection to the bridge. On macOS and Windows, running Homebridge as a native background service is significantly more reliable. On native Linux servers and Synology NAS devices, Docker with host networking works reliably.
Yes. On Linux servers, x86 mini PCs, or NAS appliances, Homebridge routinely coexists with services like Pi-hole, AdGuard Home, or Home Assistant.
The only requirement is avoiding port conflicts. Homebridge uses port 8581 by default for its web interface. As long as other services use distinct network ports, they operate completely independently.
While Apple devices discover the bridge dynamically via mDNS, a predictable IP address is essential for the Homemanager app, browser bookmarks, and SSH management.
The cleanest solution is setting a DHCP reservation in your router (e.g. enabling "Always assign this network device the same IPv4 address").
***
## Further Reading [#further-reading]
### Homemanager Guides [#homemanager-guides]
* [Understanding and Using Child Bridges](/guide/child-bridges)
* [Pairing Homebridge with Apple Home](/guide/pairing-apple-home)
* [Updating System Software and Node.js](/guide/updating-system-software)
### Official Resources [#official-resources]
* [Official Homebridge GitHub Wiki](https://github.com/homebridge/homebridge/wiki)
* [Homebridge Backup and Restore Guide](https://github.com/homebridge/homebridge/wiki/Backup-and-Restore)
* [Official Project Website homebridge.io](https://homebridge.io)