A site with no fibre is not a site with no backhaul

Ask why a rural county has no data centre and the answer is usually given as fibre. It is rarely only fibre. It is a trench that has to be dug through somebody's land, a route that has to be surveyed, a provider who has to want the revenue, and a timeline nobody on the county side controls.

Satellite backhaul changes which of those are on the critical path. It does not remove the work — it moves it from civil engineering to siting, licensing and power, which are three things a campus developer is doing anyway.

What the pad has to offer the sky

A ground site that is designed to host a satellite gateway is a specific kind of pad, and most of the requirements are unglamorous.

It needs a clear view, low to the horizon, in the directions the constellation actually passes — which is a line-of-sight survey rather than an opinion about the landscape.

It needs stable power with the same redundancy as the compute hall, because a gateway that drops when the generation transfers has not solved anything.

It needs ground: a prepared, level, drained surface with the antenna foundations designed for local wind and frost, and a cable run short enough that the loss budget survives it.

And it needs the radio-licensing work started early. In the United States that is an earth-station filing, and it is a step in the deployment schedule rather than something Xalant holds. Describing it as a step is the honest version; describing it as a licence would not be.

Why this is sequenced before fibre, not instead of it

Nothing here is an argument against fibre. Fibre is cheaper per bit once the trench exists, and a mature campus is expected to have both.

The argument is about order. A satellite pad can be working while a trench is still being negotiated, which means the first tenant does not wait on the slowest party in the county. When the fibre does arrive, it becomes the primary path and the pad becomes the one that is there when the primary path is cut.

What we are not saying

Xalant does not have a gateway anywhere. No antenna is installed, no filing is held, and no agreement with any satellite operator is in place or implied by anything on this site. Where an operator's product is named elsewhere on these pages, it is named as the technology a pad is designed around, with that operator's own published material as the source.

The figures that belong in a post like this one — throughput, round-trip latency, the loss budget — are not in it, because each of them needs a named public source and a date it was read, and that work is not finished. The sentences above are written to read without them.

If you are the county

The conversation worth having is about the pad rather than about the technology. Where is the ground, what is the view, what power can reach it, and who locally wants capacity once it exists.