Starlink has now been licensed to provide satellite internet services in the UAE.
On 28 August 2026, the UAE Telecommunications and Digital Government Regulatory Authority, TDRA, granted Starlink Satellite Communications LLC a 10-year General Space Services Licence. The licence covers services for individuals, businesses and government entities, as well as maritime and aviation connectivity. TDRA specifically positions satellite connectivity as an additional layer alongside fibre and 5G, including for locations or situations where terrestrial infrastructure is unavailable or disrupted.
For businesses operating guest WiFi, this creates a fairly practical question:
Can you use Starlink as your internet connection and still run a captive portal?
Yes.
The important distinction is where each part of the network sits. Starlink provides the connection to the internet. The guest WiFi network, access points, customer authentication and captive portal can continue to be managed by separate networking infrastructure.
A typical setup would look like this:
Starlink → business router or gateway → network switches/access points → guest WiFi → captive portal
That means a restaurant, hotel, beach club, event venue or remote hospitality location does not need to give up its managed guest WiFi simply because the underlying internet connection comes from a satellite.
Starlink supports third-party networking equipment
This is not a workaround.
Starlink officially supports connecting third-party routers and existing networking systems to most of its hardware.
Depending on the Starlink kit, the connection can be made directly through Ethernet or through an Ethernet adapter. Starlink also provides a bypass mode that disables the WiFi functionality of the Starlink router so that a third-party router can manage the network instead.
Starlink instructs third-party routers to obtain their WAN connection using DHCP, which is standard functionality on commercial gateways.
Starlink: Using a third-party router
This is the architecture that matters for captive portals. Starlink does not have to know anything about the guest login page. It simply carries the internet traffic generated by the network behind it.
What does that mean for UniFi?
UniFi is a good example because the responsibilities are quite clearly separated.
Ubiquiti's UniFi platform can create a dedicated guest network or VLAN and enable a captive portal on it. UniFi also supports an External Portal Server, allowing a third-party platform to handle the guest registration or authentication process and then authorize the customer onto the network.
Ubiquiti: UniFi Hotspots and Captive Portals
Ubiquiti: External Hotspot API
So there is no requirement for a special "Starlink captive portal integration."
Starlink provides the WAN connection. The UniFi gateway and access points manage the local WiFi network. The external captive portal handles the guest journey.
Ubiquiti also recommends isolating public guest networks from the rest of the business network, normally by placing them on a separate network or VLAN. That remains just as relevant when Starlink is the internet connection.
Ubiquiti: Best Practices — Guest WiFi
And MikroTik?
The principle is the same.
MikroTik RouterOS includes its own HotSpot gateway functionality and supports captive portals on Ethernet, wireless, VLAN and bridge interfaces. It supports local authentication, remote RADIUS authentication, walled gardens and customized login pages.
Starlink requires the connected third-party router to obtain its WAN address using DHCP. MikroTik supports DHCP clients on Ethernet interfaces, so there is nothing unusual about the WAN handoff itself.
MikroTik: HotSpot captive portal documentation
There are, however, two MikroTik-specific points worth knowing.
First, MikroTik currently states that its HotSpot implementation works reliably only with IPv4. Its HotSpot functionality relies on firewall NAT rules that are not currently supported in the same way for IPv6.
Second, more complicated multi-WAN configurations need some care. MikroTik notes that HotSpot uses the default routing table and that PCC-style load balancing using multiple routing tables can create problems. That becomes relevant if Starlink is being introduced alongside an existing fibre or mobile connection rather than as the only WAN.
Neither issue prevents a Starlink captive-portal deployment. They are network-design considerations rather than Starlink incompatibilities.
Why Starlink is interesting for guest WiFi in the UAE
For a venue with reliable fibre already installed, replacing it with satellite internet purely because Starlink is now available would be difficult to justify.
The more interesting cases are locations where getting that connection in the first place is the problem.
Temporary venues, outdoor sites, desert hospitality, remote locations, events, construction sites and other non-standard locations have traditionally had fewer options. In many of these environments, businesses have depended on 4G or 5G routers when fixed connectivity was unavailable.
Starlink adds another route to the internet.
It can also potentially be used as a separate backup connection at sites where losing internet access would interrupt payment systems, operational systems or customer connectivity. Starlink itself documents the use of third-party networking appliances for failover, load balancing and other advanced networking configurations.
Starlink: Connecting third-party networking equipment
This is where the UAE licence becomes interesting for guest WiFi. The physical location of a business becomes somewhat less limiting when deciding whether it can operate a properly managed WiFi network.
The advantages
For the right location, there are several obvious benefits.
More deployment options. A business does not necessarily need terrestrial fibre infrastructure at the site before it can provide internet access.
Existing WiFi infrastructure can remain in place. Starlink can sit upstream of UniFi, MikroTik or other commercial networking equipment rather than replacing the local network.
Useful as a secondary WAN. A separate satellite path can provide additional resilience where a suitable gateway supports WAN failover.
Business connectivity options are available. Starlink's Priority plans are designed for businesses and high-demand users and include prioritized network access, public IPv4 availability, a telemetry dashboard and priority support.
There are also some meaningful limitations.
Starlink does not replace good WiFi infrastructure
A Starlink dish can solve the connection from the property to the internet.
It does not solve WiFi coverage throughout the property.
A hotel still needs appropriately positioned access points. A large restaurant still needs sufficient wireless capacity. A guest network should still be separated from operational systems. A captive portal still needs to be configured correctly.
The satellite link is the backhaul. It is not the entire WiFi network.
For a small location, the difference may appear academic. For a hotel, resort, large restaurant, event site or other high-density environment, it is important.
Residential Starlink may be the wrong choice for busy guest WiFi
There is another limitation that is particularly relevant to hospitality.
Starlink's default IPv4 configuration uses Carrier-Grade NAT, or CGNAT. This means the customer does not receive a conventional publicly reachable IPv4 address.
More importantly, Starlink currently documents a limit of 1,200 concurrent TCP or UDP sessions on Residential and Roam plans. Once that limit is reached, new sessions cause older sessions to be dropped.
That does not mean 1,200 connected guests. One phone or laptop can create many simultaneous network sessions.
For a busy commercial guest network, it is therefore a mistake to look only at advertised download speed when selecting a plan.
Starlink recommends Priority plans for customers with high simultaneous connection requirements. Priority plans also offer a public IPv4 option and do not have the same CGNAT session limitation documented for Residential and Roam.
Starlink: CGNAT session limits
Do you need a public IP for a captive portal?
Not necessarily.
CGNAT does not automatically prevent a captive portal from working. A guest device can still make outbound internet connections through CGNAT.
The question is whether the specific network architecture requires connections to be initiated from outside the venue into the local network. Remote administration, certain VPN configurations, externally hosted controllers and other integrations can create that requirement.
Starlink makes a public IPv4 option available on Local Priority and Global Priority plans. It is dynamically assigned rather than a true static IP, although Starlink states that its reservation system generally retains the address through normal reboots.
There is an interesting UniFi implication here as well. Ubiquiti explicitly states that its Dynamic DNS functionality requires a public IP and will not operate with addresses in the 100.64.0.0/10 CGNAT range used by Starlink's default IPv4 service.
That does not affect every captive portal deployment, but it is exactly the kind of detail that should be checked before installing rather than afterwards.
Performance is still satellite performance
Starlink publishes expected performance ranges, but it does not guarantee that those speeds will be continuously available.
Performance can vary based on location, network demand, the service plan and other conditions. Starlink's current specifications state that business or Priority connections generally receive higher network precedence than standard services.
There is also a physical requirement that does not exist in quite the same way with fibre: the terminal needs a sufficiently clear view of the sky.
Starlink recommends an unobstructed installation and warns that buildings, poles, trees and other obstructions can cause interruptions, dropped packets and reduced bandwidth.
Weather is another variable. Starlink states that significant weather, including moderate to heavy rain, can cause temporary degradation or service dropouts.
In the UAE, where many of the interesting applications are likely to involve outdoor or remote sites, mounting position, power, environmental exposure and physical installation should therefore be treated as part of the network design.
So, can Affinect run over Starlink?
Yes, provided the local network is configured appropriately.
Affinect operates at the guest WiFi and captive-portal layer. Starlink would sit underneath that environment as the internet connection.
For example:
Starlink
↓
UniFi or MikroTik gateway
↓
Guest WiFi network
↓
Affinect captive portal
↓
Internet access
We would not describe this as a direct Starlink integration, because there should be no need for one.
The integration point remains the WiFi infrastructure managing the guest network.
The exact configuration should still be reviewed based on the Starlink hardware, Starlink service plan, router or gateway, access points and any requirements for failover, VPNs or remote access.
Frequently asked questions
Can I connect UniFi to Starlink and use a captive portal?
Yes. Starlink supports third-party routers through Ethernet, while UniFi supports guest networks, captive portals and external portal servers. The UniFi gateway manages the guest network; Starlink provides its internet connection.
Can I use MikroTik with Starlink?
Yes. Starlink provides a DHCP-based Ethernet connection for third-party routers, and MikroTik RouterOS supports DHCP WAN interfaces and HotSpot captive portals. MikroTik's current HotSpot documentation does, however, include IPv4 and multi-routing-table limitations that should be considered during configuration.
Do I need Starlink Business or Priority for a captive portal?
A captive portal itself does not automatically require a Priority plan. For commercial networks with many users, however, plan selection matters. Residential and Roam plans use CGNAT and Starlink currently documents a 1,200 concurrent-session limit. Priority plans are designed for higher-demand use and provide a public IP option.
Does Starlink replace my access points?
No. Starlink provides internet connectivity. A commercial property still requires appropriate routers, switches, access points, network segmentation and WiFi coverage.
Can Starlink be used as backup internet?
Yes. Starlink specifically documents the use of third-party networking appliances for features including failover and load balancing. The implementation depends on the gateway being used.
Is Starlink better than fibre for a hotel or restaurant?
Not necessarily. Where reliable fibre is already available, it will often remain the simpler primary connection. Starlink becomes particularly interesting where fixed infrastructure is unavailable, difficult to install, temporary or where an independent backup connection has operational value.
The practical conclusion
The UAE's approval of Starlink does not change how a captive portal works.
It changes where the internet connection can come from.
A managed guest WiFi network can still use UniFi, MikroTik or other compatible infrastructure to control access and run a captive portal while Starlink provides the upstream internet connection.
For businesses in locations that previously depended heavily on mobile connectivity or where fixed infrastructure was impractical, that adds a useful new option.
And for guest WiFi, that is considerably more relevant than whether the word "captive portal" appears anywhere in the Starlink router settings.
Run a branded captive portal on UniFi or MikroTik — including over Starlink backhaul — with Affinect.
Explore the Affinect platform