Hotel WiFi in Dubai is regulated by the Telecommunications and Digital Government Regulatory Authority (TDRA, formerly TRA) under a compliance framework that catches most boutique and mid-size hotels off-guard - but compliance is only half the requirements list. The other half is engineering and procurement: per-room coverage specs, guest-density capacity, roaming between floors, conference WiFi and PMS integration - the items your RFP must pin down before vendors quote. This guide walks both layers, with the cost drivers that decide a hotel WiFi quote.
What WiFi requirements must a Dubai hotel actually meet?
A Dubai hotel must meet two sets of WiFi requirements: TDRA-aligned guest compliance (captive portal, AUP, filtering, 12-month logging) and engineering specs that decide whether guests get a usable connection (-65 dBm in every room, 2.5 devices per guest, seamless roaming, segmented PMS and staff networks). An RFP that covers only one of the two buys a network that fails the other.
What captive portal and identity logging does the TDRA framework expect?
Every Dubai hotel guest connecting to WiFi must authenticate via a captive portal that verifies and logs identity. The verification methods ISPs and auditors accept in practice: passport number (international guests), Emirates ID (UAE residents), or OTP-verified UAE mobile number. Some hotels accept room number plus check-in date for registered guests once PMS integration is live. Logs must include: timestamp of connection, device MAC address, assigned IP address, identity used (passport/EID/mobile), session duration, total data used. Logs retained 12 months minimum - confirm current specifics with TDRA or your ISP at design stage.
What must the Acceptable Use Policy (AUP) cover?
The captive portal must display an Acceptable Use Policy that the guest must explicitly accept before connecting. Standard AUP elements: prohibition of illegal content access (the captive portal blocks these regardless), prohibition of using VPNs or proxies to get around filtering, statement that guest activity may be logged, statement of liability for misuse, contact information for the hotel IT manager. AUP must be available in English and Arabic at minimum.
What content filtering must hotel guest WiFi apply?
National filtering is applied by the licensed ISP (e&, du), and hotel guest WiFi should also block the content categories restricted under UAE telecom rules: gambling, pornography, content critical of UAE leadership, certain religious/political content, VoIP services not registered with TDRA (some hotels block Skype, WhatsApp voice, FaceTime). Implementation via DNS filtering (Cloudflare Gateway, Cisco Umbrella, NextDNS), URL filtering at the firewall (FortiGate, Meraki MX content filtering), or the filtering built into the captive portal platform (Tanaza, Cloud4Wi and similar). Keep filter lists updated and confirm the categories with your ISP.
What bandwidth caps and session limits should you specify?
Good practice is a fair bandwidth allocation so no single guest can saturate shared infrastructure. Standard per-guest caps: 5 to 10 Mbps for free tier, 15 to 50 Mbps for paid premium tier. Session length typically 24 hours then re-authentication required. Some hotels implement daily download caps (e.g. 2 GB free, unlimited on paid). Per-room device limits (e.g. 4 devices per room) prevent abuse.
How should guest, staff, IoT and PMS networks be segmented?
TDRA does not explicitly require network segmentation, but it is best practice and protects against the most common hotel breach pattern. Standard VLAN architecture: Guest VLAN (10) isolated from everything, IoT VLAN (20) for smart TVs and minibar sensors, PMS VLAN (30) restricted to property management system traffic, Staff VLAN (40) for back-of-house, Server VLAN (99) restricted. Inter-VLAN traffic firewalled at Cisco Meraki MX, Aruba Central or Ubiquiti UDM Pro.
| Hotel Size | AP Count |
|---|---|
| Boutique 20-40 rooms | 15-25 APs |
| Mid-size 50-120 rooms | 30-60 APs |
| Premium 120-200 rooms | 60-100 APs |
| Resort 200+ rooms | 100-200+ APs |
Hotel WiFi AP counts by size - Dubai 2026
How many access points does a Dubai hotel need?
Plan one access point per 3 to 4 guest rooms for corridor designs, or one in-room wall-plate AP per room on premium properties. Dubai's concrete construction attenuates WiFi far harder than imported rules of thumb assume, so write a signal floor into the RFP rather than an AP count: minimum -65 dBm on the 5 GHz band at the headboard and desk of every room, verified by post-install survey, not predictive heatmap alone. Hospitality wall-plate APs (Ruckus H550, Aruba AP-505H, UniFi U6 In-Wall) mount over the room's network outlet and add switched ports for the TV and phone. In-room designs cost more per room in hardware and cabling, but make per-room performance targets enforceable.
Why corridor-only designs fail in Dubai
Most failed hotel networks we re-survey assumed one corridor AP could serve 6 to 8 rooms. Through two concrete walls and a tiled bathroom, the far room lands at -75 dBm - connected but unusable. Specify per-room signal strength in the contract, not AP count.
How do you size capacity for guest density?
Size hotel WiFi for 2.5 to 3 devices per guest, with 60 to 70 percent online at evening peak. Worked example - 100 rooms, 85 percent occupancy, 1.8 guests per room: 153 guests x 2.5 devices is roughly 380, plus 60 to 100 staff and IoT clients - design for 450 to 500 concurrent connections. A WiFi 6/6E AP serves 30 to 50 active clients, so coverage sets AP count in room wings while density rules lobbies, pool decks and F&B.
What roaming performance should the RFP demand?
Specify seamless roaming: 802.11k/v/r enabled, one SSID property-wide, handoffs fast enough that a video call survives the walk from room to lobby to pool. That requires every AP on one controller or cloud platform (UniFi, Cisco Meraki, Aruba Central, Ruckus One), a channel plan with minimum-RSSI so sticky clients release distant APs, and consistent VLAN tagging so devices keep their IP mid-walk. Properties that grew one AP brand at a time should budget to unify the estate - mixed-vendor roaming drops guest sessions between floors.
What do conference rooms and banquet halls need?
Conference WiFi needs its own capacity plan: one device per seat minimum, two per seat for corporate events, on high-density ceiling APs with a dedicated SSID and bandwidth pool. A 200-seat ballroom needs 4 to 6 high-density APs (Ruckus R650 class, Aruba 630 series, UniFi U6 Enterprise) on wired multi-gigabit uplinks - never mesh. Dubai event organisers write WiFi service levels into venue contracts, so build a bookable premium tier: per-event SSIDs, configurable bandwidth, a named engineer on call.
Should your RFP require PMS integration?
Not strictly mandated but strongly recommended for guest experience. PMS integration auto-creates captive portal authentication on check-in using the room reservation - guests do not have to enter passport details twice. Supported PMS platforms: Opera (Oracle Hospitality), Cloudbeds, Mews, Protel, RoomRacoon, Hotelogix. Integration cost depends on the PMS vendor's interface fee and the customisation needed, so it is quoted per property.
Which vendor stack fits which hotel size?
Boutique hotels (20-40 rooms): Ubiquiti UniFi (UDM Pro plus U6 Pro APs) plus an EasyWiFi or Tanaza captive portal, the most cost-effective route. Mid-size (50-120 rooms): Cisco Meraki MR series plus Cloud4Wi or Tanaza captive portal, or Aruba InstantOn with a cloud portal. Premium (120-200 rooms): Cisco Meraki MR plus MX series, full Dashboard licensing for audit trail. Resort (200+ rooms): Ruckus enterprise WiFi plus a dedicated Cloud4Wi-class portal, or Cisco Meraki with full enterprise tier. Each is quoted on AP count, cabling and licensing after a site survey.
Get a vendor-neutral design before you tender
Azizi Technologies surveys Dubai hotels and produces a coverage-and-capacity design you can tender to any vendor.
What belongs in a hotel WiFi RFP?
A complete hotel WiFi RFP fits on two pages and forces every bidder to quote identical scope. Minimum line items:
- Property facts: room count, floors, construction type, public areas, conference capacity, current internet circuits.
- Coverage: minimum -65 dBm at 5 GHz in every room, proven by post-install survey at handover.
- Capacity: the concurrent-device design target and internet bandwidth per guest tier.
- Compliance: TDRA-aligned captive portal, verification method, 12-month log retention, filtering, English and Arabic pages.
- PMS integration: name your PMS and require a certified, referenceable integration - not 'compatible'.
- Segmentation: guest, staff, IoT, PMS and CCTV VLANs with documented firewall rules.
- Roaming: 802.11k/v/r on one management platform, one guest SSID property-wide.
- Acceptance: exact hardware models listed; tie 10 to 20 percent of contract value to passing the verification survey.
- Support: AMC scope, response SLA, monthly health report, pricing for years two and three.
Make vendors bid against your spec, not theirs
A written coverage-and-capacity spec eliminates lowball quotes - they cannot pass the acceptance survey and they know it. An Azizi Technologies site survey gives you that spec before you commit a dirham.
What is a realistic hotel WiFi project timeline?
From signed quote to guest-ready WiFi, typically: 2 to 3 weeks for a boutique property, 4 to 6 for a mid-size hotel, 8 to 12 for a resort with UAE stock available. The sequence:
- 1Week 1: on-site RF survey, cable-path inspection, predictive design, bill of quantities.
- 2Weeks 1-2: design sign-off, ISP circuit and captive-portal coordination, hardware ordering.
- 3Weeks 2-4: cabling and AP mounting floor by floor - never more than one floor out of service, ideally low season.
- 4Weeks 3-5: controller, VLANs, captive portal and PMS integration configured in parallel.
- 5Final week: verification survey, filtering and logging tests, staff training, documentation handover, snag list.
Who signs off on a hotel WiFi project?
Four sign-offs make or break a hotel WiFi project: the general manager or owner approves budget and guest-experience standard; the financial controller approves capex phasing and the AMC line; the IT manager signs technical acceptance against the RFP spec; and franchised properties need the brand's regional office to approve the design against brand connectivity standards. Holiday-home and serviced-apartment operators wear all four hats themselves - which makes a written spec more important, not less. Azizi Technologies runs the acceptance walk-through room by room, survey report in hand.
How do you stay ready for a TDRA compliance inspection?
Prepare as if a regulator, your ISP or your brand's auditor could check at any time. What a check typically covers: live captive portal demo, identity logging functionality, content filtering test (try accessing a blocked category), bandwidth cap enforcement test, log retention sample (request last 90 days of logs), AUP visibility, terms of service in Arabic. Confirm with TDRA and your ISP which penalties apply to your licence. Compliance audit prep typically takes 2-3 days for a mid-size hotel.
The most common Dubai hotel WiFi compliance gap
Identity logging that does not actually verify the identity. Many hotels deploy captive portals that ASK for passport number but do not VALIDATE it - any string passes. Any auditor will flag this. Compliant captive portals integrate with PMS (auto-verify against check-in record) or use OTP verification (real phone number must receive and enter code).
Dubai hotel WiFi compliance audit
Send your property name, room count, and current WiFi vendor. We will book a 60-minute on-site compliance audit, identify any TDRA gaps, and email a written remediation plan with AED quotes for any required changes.
Request a hotel compliance auditHotel WiFi Installation Dubai
