Compute in Orlando, because Orlando is where your users are

What "the edge" means here

Traditionally an enterprise put its data and computation in a handful of very large data centers and moved the results back and forth across the country. That works until latency starts to matter — for interactive applications, for streaming, for anything where a user is waiting. Processing closer to the user removes the round trip.

The usual alternative for edge deployments is a container data center at the base of a cell tower or on a factory floor. Those are genuinely hard to operate: getting reliable power to them is a project, and maintaining them means sending someone. A carrier-dense building in the center of the metro gives you the same latency profile with none of that — full facility power, cooling, security and hands, already there.

Why this building

Nine carriers have equipment in our meet-me room, so reaching your users is a cross-connect rather than a build. The building was the de facto telecom hotel at the intersection of multiple fiber routes; carriers and providers consolidated into the space over time. The facility runs N+1 across power, cooling and connectivity, on two utility feeds — one of them on the Priority 1 hospital grid.

Facility specifications →

What people use it for

• Content and application delivery — serving central Florida users from central Florida rather than from another region.
• Distributed processing — handling data from devices, sensors and meters locally, where shipping it across the country would cost more than processing it.
• Regional resilience — a second site for an organization whose primary compute is elsewhere, so a regional event does not take everything at once.
• Latency-sensitive workloads — anything interactive enough that a cross-country round trip is noticeable.