I sympathize with the poster, as deploying my own stack should've been an easier migration from their EdgeRouter kit than it turned out to be - though wisely, I had budgeted a six hour window for a process that ultimately took ~2hrs.

Ubiquiti's niche really is the "I want Enterprise features but I also don't want to be my own CCIE to run this shit," and in that sense it overachieves nicely. Does it have idiosyncrasies? You betcha, and OP found this out first hand. Would I trust this for blind/hands-off remote site deployment? Hell naw, that's what Meraki is for. Would I build a data center around these? Maybe, depending on the data center's function?

Honestly, my wishlist for the product suite is a stronger focus on self-hosting, removing the Bluetooth app requirement for initial setup of hardware, improving zero touch provisioning, and letting me use Identity without having to tie it to their servers (e.g., local LDAP or SAML/SSO integration). That'd make me a happy dinosaur.

Interesting, for my part I would never build a data center (or underpin critical infrastructure) with Ubiquiti but I have a lot of it at blind remote sites and it works well enough - WAN failover, and they've built out a fair bit of downstream failover as well - shadow gateways, RPS, etc. Has replaced a lot of Meraki subscriptions.