What a Starlink installation actually involves on a Dubai building

The survey comes first, and what it is looking for

Everything about a satellite install is decided on the roof, which is why nobody should quote one from a floor plan. The survey is short, usually under an hour on an accessible roof, and it answers four questions: where can the dish see enough sky, where can it be fixed safely, where does power come from, and how does the cable get inside.

Sky view is the one people underestimate. A dish does not need a view of the whole sky, but it needs a wide unobstructed arc, and obstructions are counted in the direction the constellation passes rather than evenly. A parapet that looks low from standing height can clip the arc. So can the air conditioning plant that occupies most of a commercial roof in this city, a lift overrun, a water tank, or a neighbouring tower that is simply taller than yours.

The survey also establishes what the install is not going to be able to do. If the only clear patch of sky is on a part of the roof with no power and no route inside, the honest output of the survey is that the job is larger than expected, or that it is not worth doing. We would rather say that after an hour than after a purchase.

One more thing the survey settles is which of the two common failures you are at risk of. The first is an install that works on the day and degrades later, because the arc was marginal and a neighbouring building was under construction. The second is an install that never works properly because the obstruction was there all along and nobody looked up. Both are avoided by standing on the roof rather than by reading a specification.

Where the dish can actually go on a Dubai building

Flat commercial roofs are the common case and the easiest, as long as the mount can be weighted or fixed without compromising the waterproofing. A non-penetrating ballasted mount is usually preferred for exactly that reason: no holes in the membrane means no argument with the building about who pays when water appears.

Parapet and wall mounts are the next option and often better on a tower, because they get the dish above the plant without crossing the roof. They need a wall that can carry the load and an installer willing to think about wind.

Balconies and window ledges come up a lot and rarely work for an office. The arc of sky from a balcony on a low floor is narrow, and on a leased floor it is usually not yours to attach anything to. We have seen more disappointment from balcony installs than from any other decision in this job.

• A wide, unobstructed arc of sky, judged on site rather than from a photograph.
• A fixing point that does not require penetrating a waterproof membrane, where that can be avoided.
• Power within a sensible cable distance, or a route to bring it.
• A cable path inside that does not cross a fire compartment without proper sealing.
• Access for maintenance that does not involve a ladder over an edge.

Permission is the part that takes the longest

The install is a day. The permission can be weeks, and it is the single most common reason a satellite project stalls.

Anything fixed to a roof belongs to a conversation with the building owner, the facilities manager or the owners' association, and sometimes all three. Roof access usually needs to be booked and supervised. A cable penetration needs approval from whoever is responsible for the building fabric. Some buildings will ask for a method statement, some for insurance details, and some for a structural opinion on the mount, which is a cost worth knowing about before it appears.

None of that is ours to grant, and we are careful not to imply otherwise. What we can do is tell you precisely what the install needs, in the form the building will ask for it, so the request you make is specific rather than a general enquiry about putting something on the roof. Specific requests get answered; vague ones circulate.

It also helps to know what the building is actually worried about. Facilities managers are rarely obstructive about satellite equipment itself; they are protecting the waterproofing, the structure and the precedent. A request that already answers those three concerns, with a non-penetrating mount and a sealed route, tends to be approved. A request that asks to put a dish on the roof and leaves the detail open tends to be refused on principle.

Mounting, weatherproofing and earthing

A rooftop in this climate is a harsh place to leave equipment. Surface temperatures are high, there is dust in everything, and there are a small number of genuinely violent rain and wind events each year. A mount that would be fine in a temperate climate can work loose here.

So the bracket is specified for wind load rather than for convenience, fixings are chosen to survive thermal cycling, and every cable entry is sealed and dressed so water runs away from the penetration rather than along the cable into it. The cable itself is routed with a drip loop, which is a small detail that prevents a predictable problem.

Earthing matters and is frequently skipped. A metal structure on the highest point of a building, connected by cable to equipment inside, needs to be bonded properly. Doing it is cheap at install time and awkward afterwards.

There is also a dust consideration that does not apply in most climates. After a sandy spell the dish face accumulates a film that affects the link, and the mount should be sited where somebody can reach it safely to wipe it. An otherwise perfect position that requires leaning over a parapet to clean is the wrong position, because in practice it will never be cleaned.

Power at the mount point, which most quotes leave out

The dish needs power, and roofs often do not have a usable socket where the dish needs to be. This is the detail that turns a straightforward quote into a variation, and it is worth settling before anyone commits.

Sometimes there is a maintenance socket close enough. Sometimes a circuit has to be extended from a riser or a plant room, which brings an electrician into the job and means the building needs to approve that work too. Occasionally the cleanest answer is to run the data cable to the dish and keep the power supply inside, depending on the equipment and the distance.

We price the power as its own line rather than bundling it, because it is the part most likely to change after the survey, and a quote that hides it is a quote that will move.

Integration, which is what makes it a second path

A satellite connection terminated into its own router in the corner of the comms room is not redundancy. It is a second network that somebody has to notice and join manually, which during an outage is exactly when nobody has the attention to do it.

The install therefore ends at your firewall rather than at the dish. The satellite link becomes a second wide area interface, with routing, and with rules about what uses it when the primary is down. Your network separation carries across, so guest traffic, device traffic and office traffic keep their boundaries on the satellite path too. Without that, a failover quietly becomes a way around your own security rules.

That configuration work sits on the same equipment covered on the network and Wi-Fi page, and the scope of the install itself is set out on the satellite internet and Starlink page. The hardware and subscription are bought in your name directly from Starlink, so the account stays yours.

The other half of integration is deciding what should not use the satellite path. A backup link usually has less capacity than the primary, so during a failover something has to give. Large file synchronisation, backups and software updates are the usual candidates to pause, and deciding that in advance is better than discovering it when a sales call competes with a cloud backup. That decision belongs in the install document, not in the moment.

Configuring the failover is only half of it: the other half is proving it, which is the subject of failover that actually fails over. Whether satellite is the right second path for your building in the first place is covered in when it is a real second line.

What you should get at handover

A satellite install that is finished properly leaves a paper trail, because the next person to touch it will not be the person who fitted it.

• A photograph of the mount in position, with the sky arc it was sited for.
• Where the cable runs, where it enters the building, and how the penetration was sealed.
• The earthing arrangement.
• Which firewall interface the link lands on, and the failover rules as configured.
• Evidence that failover was tested by deliberately disconnecting the primary, and what happened to calls and sessions when it did.
• Who holds the Starlink account, and the process for raising a fault with the service itself.

Vessels and remote sites are a different job

An office roof does not move. A vessel does, and a maritime install has to deal with motion, a mount that will be in salt air permanently, and cable routes through a structure that was not designed for it. TDRA named maritime connectivity in the licence scope, and Starlink publishes a maritime service separately from its business offering.

Site offices and compounds sit in between. The mount is usually easier, because a container roof or a dedicated pole has none of the politics of a tower. The harder parts are power, which on a construction site is rarely stable, and physical security for equipment that is worth stealing. We wrote about the connectivity side of this in internet connectivity at sea, and the shore office version appears on the marine and shipping page.

Frequently asked questions

Written by Srinivasan Ramachandran, Founder, Listonics · Published Oct 11, 2026 · Last reviewed October 11, 2026 · 2,141 words