UniFi’s release cadence is a feature and a liability

One of the reasons UniFi Network is as capable as it is at the price is that Ubiquiti iterates quickly and publicly. Features that would sit in an enterprise vendor's roadmap for two years appear in an early-access build within months.

The trade-off is the one you would expect. A fast release cadence with a broad hardware matrix produces occasional regressions, and the ones that bite hardest are client-compatibility regressions — a specific device class that stops associating after an access point firmware update.

The operational pattern that works

• Stay one minor release behind the newest stable build on production sites. Not three behind, which accumulates its own risk, and not on early access.
• Turn off automatic firmware updates on anything that matters. The default is convenient for a home and wrong for a business.
• Read the release notes. Ubiquiti publishes them, and known issues are listed.
• Keep a test site. Even one access point and a switch in an office corner, adopted to the same controller as a separate site, lets you take the newest build first.
• Back up the controller before every update, and store the backup somewhere other than the console.

The wider point about ecosystem risk

This is not an argument against UniFi. It is an argument for treating it as what it is: a fast-moving platform with community-first support, bought at a price that reflects both of those things.

If your organisation needs a vendor contractually obliged to answer at 2am, that is a different purchase and a different budget. If it needs excellent software at a price that makes good networking affordable, the mitigation above is the cost of entry.