Edge node—Single-tenant
Your hardware, your cycles: single-tenant bare metal with no noisy neighbors, so every request performs the same.

If you had the time, the partners and the capital: bare metal next to your users, with every millisecond yours to tune.

Your hardware, your cycles: single-tenant bare metal with no noisy neighbors, so every request performs the same.
CPU pinning, NUMA tuning and kernel bypass with XDP and DPDK, with no hypervisor in the way.
Custom kernels and drivers built for high packet rates and stateful packet processing.
350+ interconnection-dense data centers, so compute sits next to your users, not a region away.
Compute-centric pricing: data-intensive workloads are welcome, so design for performance, not for less traffic.
The usual way: a region far from your users, where every request pays the distance there and back.
Every abstraction adds delay, every shared resource adds variance, and distance adds both. The same requests, answered two ways.
Edge nodeBare metal in your users’ metroCloud region2,000 km away · a shared VM
An illustration: made-up requests shaped to the live page’s figures. Light in fiber covers about 200 km a millisecond, so a region 2,000 km away spends 20 ms on the distance alone.
Teams that need every request on time switch from shared, virtualized hardware to their own.
Edgevana bare metalMulti-tenant cloud
Virtualized, shared infrastructure brings spikes you can’t predict: every noisy neighbor costs you users, every abstraction layer adds latency.
Proven running distributed infrastructure at extreme scale, with millions of transactions in real time.
Insight for routing decisions others can’t make, from coordinating large-scale internet traffic every day.
Long relationships with networks and interconnection partners, in data centers chosen for network density.
One operator from the physical connection (EdgeLink) to compute to orchestration.
Deploy