UniFi Gateway, Switching and Wi-Fi Design
UniFi can combine gateways, switching and Wi-Fi in one management experience. Model selection and lifecycle still require engineering because performance, redundancy and support vary across the product range.
Build the physical and logical design together
Confirm scale, topology, power, uplinks, management, licensing, security, testing and lifecycle before selecting hardware.
Platform and architecture fit
Select a gateway from WAN interfaces, IDS/IPS throughput, VPN, users, UniFi device count, applications, storage and high-availability needs. Advertised routing and inspected-security throughput are different planning values.
Choose switches and APs for ports, PoE, uplinks, radio, density and environment. Use current technical specifications and avoid assuming similarly named models have identical power or Layer 3 features.
- Gateway inspected throughput
- Applications and device capacity
- Switch and AP model features
- HA and support expectations
Ports, power and physical infrastructure
Calculate PoE by actual endpoints and include surge, UPS and heat. Multi-gigabit APs need suitable cabling and switch ports. Survey Wi-Fi placement and validate coverage, capacity and roaming after installation.
Coordinate SFP/SFP+ optics, DAC support, VLAN trunks and native networks. Label physical ports and keep a site-specific device and MAC inventory.
- PoE and UPS calculation
- RF survey and validation
- Optic and uplink compatibility
- Port and VLAN records
| Component | Role | Confirm |
|---|---|---|
| Cloud Gateway | Routing, security and applications | Throughput, storage and capacity |
| Switch | Ports, PoE and uplinks | Model features and power |
| Access point | Wireless service | Survey, clients and mounting |
| Control plane | Management and lifecycle | Ownership, backup and updates |
Management, security and lifecycle
Assign console ownership to the client organization, enable multifactor authentication and use named roles. Back up before major changes and record recovery ownership. Support files may contain sensitive operational data and should not be public.
Use official release channels and distinguish Early Access from general releases. Stage gateway, switch and AP updates and verify VPN, routing and clients afterward.
- Client console ownership
- MFA and named administrators
- Official release channel
- Backup and rollback procedure
Commissioning and closeout
Test WAN, failover, VLANs, DHCP, firewall, VPN, PoE, wireless and alerts. Verify adoption and recovery without relying on factory reset as the first troubleshooting step.
Deliver topology, port maps, controller ownership, backups, versions and survey results. Link to official downloads rather than hosting software.
Before final acceptance, reconcile the installed bill of materials with the approved design and current manufacturer records. Confirm model, hardware revision, serial, support status, software, license or subscription, rack location, power source, switch port and uplink for every managed component. Review alarms and logs after a representative traffic period, not only at the instant the link becomes active. Operations should receive a protected configuration backup, recovery access procedure, escalation path, maintenance assumptions and a list of known exceptions. Where cloud management is used, verify that the client organization—not an individual installer account—owns the tenant, subscriptions and recovery contacts. These controls make later support, expansion and replacement practical across multiple sites.
- WAN and policy acceptance
- Wired and wireless validation
- Adoption and recovery tests
- Protected closeout records
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Discover
Inventory sites, users, applications, circuits and existing assets.
Engineer
Select topology, hardware, power, optics, licenses and policy.
Stage and deploy
Preconfigure, back up and install through change control.
Validate
Test performance, resilience, monitoring and recovery and deliver records.
Information to gather before design
Good decisions are easier when the project team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Site and application requirements
- Topology, ports, PoE and uplinks
- Management, licenses and administrator roles
- Security, software and recovery
- Testing and documentation standards
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Is UniFi license-free?
Many management functions do not use per-device licenses, but hosting, support and other services may have costs.
Can any UniFi switch power any AP?
No. Verify PoE standard, wattage, port and total budget.
Should Early Access firmware be used in production?
Only through an explicit risk, pilot and rollback process.
Where are official UniFi downloads?
Use Ubiquiti’s official download and release portal.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Plan a testable network-infrastructure project
Share available drawings, site counts, pathways, distances, applications and turnover requirements. We will help identify the surveys, materials, testing and documentation the project needs.