Choose the installation type before choosing an SBC. Home Assistant OS/appliance support is different from maintaining Home Assistant Container on a full Linux host. This page does not promote a generic Banana Pi HAOS image or deprecated installation route.
Quick picks
- Home Assistant Green: Simplest appliance. The support path and predictable hardware are the main advantages.
- Home Assistant Yellow: Integrated build. Compute Module architecture, radio integration and NVMe options suit a tidy installation.
- Raspberry Pi 5: Flexible supported HAOS. Official HAOS images and a wide case ecosystem, though it needs appropriate power and cooling.
- ODROID-M2: Container host. Capable hardware, but not an official HAOS target in the published support list.
- Banana Pi BPI-M7: Advanced container host. More CPU than most homes need and no official HAOS image. Choose only for a broader Docker host.
Comparison table
| Board | Best role | Why it makes the list |
|---|---|---|
| Home Assistant Green | Simplest appliance | The support path and predictable hardware are the main advantages. |
| Home Assistant Yellow | Integrated build | Compute Module architecture, radio integration and NVMe options suit a tidy installation. |
| Raspberry Pi 5 | Flexible supported HAOS | Official HAOS images and a wide case ecosystem, though it needs appropriate power and cooling. |
| ODROID-M2 | Container host | Capable hardware, but not an official HAOS target in the published support list. |
| Banana Pi BPI-M7 | Advanced container host | More CPU than most homes need and no official HAOS image. Choose only for a broader Docker host. |
| Orange Pi 5 Max | Community ARM container host | Fast hardware does not replace supervisor, add-on and recovery integration. |
| Radxa ROCK 5B+ | Community RK3588 host | Suitable for containers if radio pass-through and backups are designed deliberately. |
How we chose
This guide is based on published hardware specifications, official operating-system documentation, current support pages and maintainers' release information. It is not based on invented lab tests or claims that every board has been used for months. We weight the complete system: a fast processor cannot rescue an unsupported boot image, a poor power supply, a throttling enclosure or storage hanging from an unreliable bridge.
Community discussions also reveal a useful pattern. Owners rarely regret buying slightly less CPU. They regret discovering that the required container has no ARM image, that a radio dongle sits beside a noisy USB 3 cable, or that a board exposes PCIe but no practical case can hold the adapter. Those recurring failure modes shape the recommendations here.
Software, boot and maintenance
Appliance and Home Assistant OS
Home Assistant’s current installation documentation recommends Home Assistant OS for most users and identifies specific supported hardware paths. Do not infer an official image for every Banana Pi. Appliances and HAOS are outside the local Linux host check and FleetCare preview scope.
Home Assistant Container on full Linux
Container deployment requires a Linux host and container orchestration that you maintain. It does not provide Home Assistant OS apps. Verify the exact supported architecture, peripherals and any separately required services. A host observation cannot inspect Home Assistant entities, backups or container health.
For Container on full Linux only; this does not inspect Home Assistant, containers or HAOS: Check the Linux host running Home Assistant Container
Choosing a full-Linux container host
Storage, power and cooling
Prefer eMMC, NVMe or a properly powered SATA SSD for write-heavy services. MicroSD remains useful for installation and recovery, but databases, logs and container layers create frequent small writes. If microSD must be permanent, use endurance media, reduce logs and keep automatic backups. Our microSD endurance guide explains the warning signs.
Budget power for the board, storage, radios, fans and USB devices together. A supply can show the right voltage at idle and still sag during CPU boost or SSD start-up. Use the connector and rating the board maker specifies, avoid thin cables and inspect kernel logs after stress. The crash diagnostic checklist separates power, storage and thermal faults.
Modern high-end SoCs need a heatsink, and sustained workloads often need airflow. A large passive sink is quiet but only works if the enclosure can exchange air. A small fan can be effective but should be replaceable. Check throttling under the real workload before calling a build finished.
Accessories and build planning
Verify each radio adapter against the intended integration and current Home Assistant guidance, including firmware and device access. Plan USB placement and interference reduction without inventing a compatible radio SKU. Required storage, host power, cooling and a tested configuration/data restore matter more than an unsupported board’s headline specification. No unreviewed complete kit or price is promised.
Who should buy, and who should skip
Buy the recommended platform when its official or well-maintained community image supports every required interface and when you can obtain the proper power and cooling parts. Skip it if your project depends on a peripheral marked experimental, an amd64-only application on ARM, or a proprietary accelerator workflow that has not published support for your model.
Also skip an all-in-one build if one fault would take down routing, storage and automation together. Consolidation saves watts and boxes, but it enlarges the blast radius of updates and storage failures. Two modest systems can be easier to maintain than one heroic board covered in adapters.
Final checklist
- Confirm the exact board revision and current image.
- Check architecture support for every essential package or container.
- Draw the storage and PCIe path, including shared lanes.
- Use the maker's power recommendation and include peripherals in the budget.
- Add cooling appropriate to sustained load.
- Keep serial access, recovery media and tested backups.
- Recheck stock and listing identity immediately before buying.
Frequently asked questions
Is the fastest SBC automatically the best?
No. Software support, storage reliability and interfaces decide whether performance is usable. A slower board with a maintained image often finishes the project sooner.
How much memory is enough?
Four to eight gigabytes covers many headless services. More helps large container stacks, desktop browsers and local models, but unused RAM does not compensate for weak I/O.
Should I boot from microSD?
It is excellent for recovery and light read-mostly systems. Prefer eMMC, NVMe or SATA for databases and always-on write-heavy work.
Can one board run everything?
Technically, often. Operationally, consider whether a reboot or failed disk should also stop the router or home automation. Reliability is a system design choice.
Detailed recommendations
1. Home Assistant Green: Simplest appliance
The support path and predictable hardware are the main advantages.
2. Home Assistant Yellow: Integrated build
Compute Module architecture, radio integration and NVMe options suit a tidy installation.
3. Raspberry Pi 5: Flexible supported HAOS
Official HAOS images and a wide case ecosystem, though it needs appropriate power and cooling.
4. ODROID-M2: Container host
Capable hardware, but not an official HAOS target in the published support list.
5. Banana Pi BPI-M7: Advanced container host
More CPU than most homes need and no official HAOS image. Choose only for a broader Docker host.
6. Orange Pi 5 Max: Community ARM container host
Fast hardware does not replace supervisor, add-on and recovery integration.
7. Radxa ROCK 5B+: Community RK3588 host
Suitable for containers if radio pass-through and backups are designed deliberately.
Chooser matrix
| If you prioritise | Choose | Verify first |
|---|---|---|
| Lowest setup risk | Home Assistant Green | Official image and accessories |
| Specialised interfaces | Home Assistant Yellow | Kernel support and lane sharing |
| Experimentation | Radxa ROCK 5B+ | Serial recovery and community activity |
Bottom line
Home Assistant Green is the lowest-risk first system. Home Assistant Yellow is the integrated option for users who want a supported appliance with radio and expansion. Raspberry Pi 4 or 5 is the flexible HAOS choice. Use other ARM boards only when you knowingly accept Home Assistant Container or a community installation instead of an officially supported HAOS target.
Specifications and support can change. Recheck the board's official documentation and the chosen distribution immediately before ordering or upgrading.