How to choose a single board computer
Choose by workload, not by benchmark. A home automation hub wants low idle power and GPIO. A small NAS wants NVMe or SATA and real gigabit or faster networking. A media box wants hardware decode for the codecs you actually play.
Software support outlives the silicon
The spec that decides how long a board stays usable is not printed on the box: whether it runs mainline Linux or a vendor kernel fork. A vendor fork pins you to that vendor's image and stops receiving updates when they lose interest. Mainline support means the board keeps working with current distributions for years.
Community size is a real feature
A board with a large community has working images, forum answers and tested projects. A faster board with none of that costs you weekends. This is why the most popular boards stay popular despite being outperformed on paper.
Storage and IO
microSD is convenient and the usual point of failure. Boards with eMMC, NVMe or SATA are far more reliable for anything running continuously. Check whether the PCIe lane is shared with another port.
Power and thermals
Idle draw matters for anything on all year. Peak draw sets the power supply, and undersized supplies cause random reboots that look like software faults. Most performance boards need a heatsink or a fan to hold clocks.
NPU claims
An NPU figure in TOPS says nothing about whether your framework can use it. Check for actual driver and runtime support before buying on that number.
Common mistakes
- Buying on CPU benchmark and finding the board has no working image for your use case.
- Assuming GPIO pinout matches another board's. It usually does not.
- Running from a phone charger that cannot hold voltage under load.