GLBSAAS›Deployment Models›Cloud Global Edge
Fully managed SaaS delivery

Cloud Global Edge Traffic Control Without Infrastructure Overhead.

Deploy production-ready global DNS load balancing from the GLBSAAS control plane while we operate the software, edge infrastructure, and platform redundancy. Your team defines applications, health checks, persistence, Geo/IP policy, failover, and DNS behavior — without owning the edge fleet underneath it.

Fully ManagedDashboard DeployedHealth-AwareOptional PersistenceGeo/IP Policy
Managed Global Edge
RegionNorth AmericaManaged edge
RegionEuropeManaged edge
RegionAsia PacificManaged edge
RegionAdditional POPsManaged edge
Operational outcome

Get the traffic platform. Leave the edge operations to us.

Cloud Global Edge is for teams that want sophisticated global traffic steering without adding another infrastructure estate to patch, upgrade, monitor, and recover. GLBSAAS owns the platform operations; you own the application intent.

↗

Fastest Path to Production

Deploy from the dashboard instead of first designing and maintaining an edge-node hosting model.

◎

Managed Redundancy

Customer traffic redundancy is delivered as part of the managed operating model rather than left to customer-operated edge infrastructure.

⚙

Lower Operational Burden

Software lifecycle and platform infrastructure are managed for you so your team can focus on traffic policy and application availability.

How it operates

Define service intent centrally. Execute traffic decisions at the edge.

The control plane distributes configuration to the managed edge fleet. Edge nodes make DNS decisions locally using health state, source context, Geo/IP policy, persistence, and routing rules — keeping the DNS query path independent from real-time control-plane availability.

  • Dashboard-driven service deployment
  • Local health-check execution
  • Local Geo/IP policy evaluation
  • Optional persistence at the edge
  • Automatic failover decisions
  • Authoritative DNS zones and views
Managed operating path
01 CONTROLConfigure services, policy, pools, health checks, and DNSGLBSAAS console
02 DISTRIBUTEAuthenticated desired state reaches managed edge nodesControl plane
03 DECIDEHealth + Geo/IP + persistence + routing evaluated locallyEdge runtime
04 RESPONDDNS or L4 traffic is sent to the selected healthy targetApplication path
Included traffic capabilities
DNSAuthoritative DNS load balancingHealth aware
STATEOptional persistence + peer synchronizationPublic/private IP
POLICYSource IP and geographic filtering / steeringRule based
L4TCP/UDP load balancing with optional Source NATWhere configured
LIFECYCLEAutomatic software upgrades with persistence continuityManaged
Same traffic engine

Managed delivery does not mean simplified capability.

Cloud Global Edge uses the same core GLBSAAS traffic model as dedicated deployments. The operating model changes; the traffic-control foundation does not.

◎Global DNS Load BalancingFailover, round robin, and health-aware selection.
▣PersistenceOptional source affinity and synchronized state.
⌖Geo/IP PolicyRule-based filtering and traffic steering.
♥Health ChecksContinuous endpoint evaluation and recovery.
⇄TCP/UDP BalancingL4 distribution with optional Source NAT.
▤Zones & ViewsStandard DNS services with source-aware views.

Want global traffic control without operating the edge fleet?

Tell us where your applications run, how you handle failover today, and what traffic behavior you need. We’ll map the Cloud Global Edge model to your environment.

Plan My Deployment →