The short version
Most people meet UniFi as Wi-Fi access points, then discover it covers considerably more. It is a platform rather than a product line: several applications sharing one console, one login and, importantly, one set of cabling and switching.
| Application | What it manages | Replaces |
|---|---|---|
| UniFi Network | Gateways, switches, Wi-Fi, VLANs, routing | Router, switches, wireless controller |
| UniFi Protect | Cameras, recording, retention, playback | NVR or DVR and camera software |
| UniFi Access | Door controllers, readers, credentials | Standalone access control system |
| UISP / airMAX | Long-range point-to-point wireless links | Trenched fibre between buildings |
The practical appeal for a small or mid-sized business is not any single application. It is that the cameras, the door readers and the access points can share the same PoE switches, the same cabling design and the same management interface, instead of arriving as three unrelated systems with three support arrangements.
UniFi Network: the foundation
Everything else depends on this. UniFi Network covers the gateway at the internet edge, the switching that distributes connectivity and PoE power, and the wireless access points.
The parts that matter in a business deployment are VLANs to separate staff, guest, voice, camera and device traffic; managed switching so ports can be identified and configured remotely; PoE budgeting so cameras and access points can be powered from the same switches; and remote management so changes and fault-finding do not require a site visit.
Ubiquiti networks for small and growing businesses covers where this fits well and where the limits appear, and UniFi vs Meraki vs Cisco vs Aruba vs Fortinet compares it against the alternatives.
UniFi Protect: cameras on the same platform
Protect is the video surveillance application. Cameras connect over PoE to the same switching as everything else, and recording happens on local storage in a console or dedicated recorder rather than in a paid cloud tier.
For businesses that already run UniFi networking, this is often the most compelling addition, because the cabling, switching and management are already in place. The camera project becomes an extension of the network rather than a separate system with its own recorder, software and login.
Practical considerations are storage sizing, retention expectations, camera placement and the privacy obligations that come with recording people. UniFi Protect for business CCTV covers the comparison with traditional NVR systems in detail.
UniFi Access: door entry without a separate system
Access handles door entry — controllers at the door, readers, credentials and the rules about who can enter where and when. Like Protect, it runs on the same console and shares the network.
The appeal is the same: one platform, one set of cabling, no separate access control server. The considerations are that doors involve hardware beyond the reader, including locks, power supplies, egress and fire compliance, which is where the project touches building trades rather than just IT. UniFi Access for door entry covers what a deployment involves.
Point-to-point wireless where cabling is impractical
Not every site is one building. Where a business needs to link a second building, a shed, a yard or a site across a road, trenching fibre is often disproportionate to the requirement.
Ubiquiti’s point-to-point wireless range covers this, providing a link between two locations with clear line of sight. It is a genuinely useful option for warehouses, factories, farms and regional sites, and it is covered in point-to-point wireless with airMAX.
Controllers and consoles
UniFi needs somewhere to run its applications. That may be a compact console suited to a single office, a rack-mounted device that also handles routing and recording, or self-hosted software for those who prefer it.
The choice matters because it determines which applications can run, how much camera storage is available, and whether the site has one device performing several roles or separate devices for each. It is worth deciding before ordering hardware rather than after.
Where the ecosystem ends
Being clear about the boundaries is as useful as listing the features.
Voice is not part of the practical stack in Australia. Ubiquiti’s voice product has never been generally available here, so a business should plan phones on a dedicated cloud platform. That is not a limitation in practice, because voice quality depends far more on the network and internet service than on who supplies the handsets. UniFi handles that underlying network well, which is exactly the part that determines whether calls work.
Deep enterprise features have limits. Businesses with complex routing requirements, formal support contracts with response-time guarantees, or specific compliance obligations may need a platform with heavier vendor support. That comparison is covered in UniFi vs Meraki vs Cisco vs Aruba vs Fortinet.
It still needs designing. Consolidating onto one platform does not remove the need for coverage planning, PoE budgeting, VLAN design and documentation. It makes those decisions easier to implement and inspect, not unnecessary.
Helpful starting points
If the network is the immediate problem, start with Ubiquiti network services. If cameras are the driver, read UniFi Protect for business CCTV first, since storage and retention decisions shape the hardware. If the appeal is mainly cost predictability, UniFi licensing and running costs sets out what is and is not included.