Today Ubiquiti officially announced what they’re calling UniFi Fabrics — a license-free API for managing UniFi infrastructure at scale through their Site Manager. Fabric-level control, multi-site orchestration, no per-device licensing fees. A direct shot at Cisco Meraki’s pay-to-play dashboard model.

We were already using it.

The Session

Three sites across different states. Nine access points total. All running on factory defaults — auto power (max), auto channels (DFS-eligible), zero radio management. The result: co-channel interference, sticky clients clinging to distant APs, and throughput that made 802.11ax feel like 802.11b.

From a terminal, over WireGuard tunnels to each UniFi Cloud Gateway, we hit the API directly — the same integration endpoint that Ubiquiti formalized today. No controller GUI. No clicking through site-by-site. Just structured calls pulling radio environments, client association data, and PoE stats, then pushing targeted configuration changes back.

What We Fixed

• Channels: Moved all 9 APs off auto/DFS to specific non-DFS channels (1, 6, 11 on 2.4 GHz; 36, 44, 149, 157 on 5 GHz) — eliminating DFS radar events and co-channel overlap between sites
• TX Power: Dropped from auto (max) to appropriate levels per AP — medium or low depending on coverage area and wall density
• Minimum RSSI: Enabled on all APs (typically -70 to -75 dBm) to force clients to roam instead of death-gripping a weak signal
• Band steering: Verified prefer-5G enabled across all radios

We also pulled port-level traffic stats, PoE wattage per port, and full client lists with signal strength and association time — granularity that SNMP polling never gave us cleanly from UniFi gear.

A fourth site ran an ASUS router. Different vendor, different approach — SSH and wl commands. Still remote, still no physical access needed. The consistency of the UniFi API across the other three sites made the contrast obvious.

Why This Matters

Ubiquiti making this official and license-free is the right move. The API was already there under Integrations on the console — they just hadn’t put a name on it or built the multi-site orchestration layer publicly. Now it’s a product.

The Meraki comparison is inevitable and deserved. Cisco charges per-device annual licensing for dashboard access to your own hardware. Ubiquiti is saying: buy the hardware, get the API, manage at scale, pay nothing extra. For anyone running infrastructure across multiple sites — MSPs, distributed businesses, anyone with more than one location — that math is simple.

What I’ll remember from the session isn’t the announcement. It’s that an AI and a network engineer, working from a terminal with no physical access, tuned nine access points across three states in a single sitting. The API just needed to exist. It already did.

Signal received.