Infrastructure Choice
Deploy the software in your public cloud or private environment instead of moving application traffic into a mandatory hosted edge model.
Tenant-dedicated infrastructure
Dedicated Edge Your Cloud. Your Tenant. One Traffic Engine.
Run GLBSAAS software inside your public or private cloud when you want tenant-dedicated traffic infrastructure without giving up centralized policy, health, persistence, software lifecycle management, or operational visibility.
Dedicated EdgeYour CloudRegion ADedicated node
Your CloudRegion BDedicated node
Private CloudDatacenterDedicated node
ControlYour TenantScoped access
Infrastructure-aligned control
Put the traffic plane where your applications already live.
Dedicated Edge is designed for organizations that want their own infrastructure boundary, their own node footprint, or direct placement in public and private cloud environments — while keeping the same GLBSAAS control model and traffic intelligence.
Tenant-Dedicated Runtime
Keep the operational edge dedicated to your tenant space with scoped configuration access and local traffic-state handling.
Local Traffic Decisions
Health, Geo/IP policy, persistence, and DNS decisions execute close to the workload without a control-plane call in the DNS query path.
Operational architecture
Centralized control with local execution and continuity.
Dedicated Edge nodes receive authenticated desired state from the control plane, validate and activate configuration locally, and continue serving with last-known-good configuration when the control plane is unavailable. Health checks, persistence, Geo/IP evaluation, and traffic decisions remain local to the node.
- Authenticated node enrollment
- Scoped tenant configuration
- Atomic configuration activation
- Local last-known-good operation
- Automatic software upgrades
- Persistence continuity through upgrade
Dedicated operating path
01 DEPLOYInstall GLBSAAS software in your selected public/private cloudYour infrastructure
02 ENROLLNode establishes strong identity and tenant-scoped control accessAutomated
03 SYNCConfiguration and software desired state arrive from the control planeAuthenticated
04 EXECUTEHealth, policy, persistence, DNS, and L4 decisions execute locallyDedicated edge
State and availability model
HEALTHActive endpoint monitoring drives local routing stateContinuous
PERSISTENCEOptional DNS persistence keeps source affinity near the edgeLocal state
P2P SYNCPersistence records synchronize between eligible peersPublic/private IP
UPGRADESAutomatic software upgrades preserve persistence through handoffContinuity
CONTROL LOSSLast-known-good configuration remains available locallyResilient
Full platform capability
Dedicated does not mean disconnected.
The node placement is yours; the operating experience remains GLBSAAS. Use the same control plane to manage authoritative DNS, traffic policy, health checks, persistence, failover, and software lifecycle across your dedicated footprint.
◎Global DNS Load BalancingHealth-aware authoritative answers with failover and round robin.
▣PersistenceOptional source affinity with peer synchronization.
⌖Geo/IP RulesSource-aware filtering and load-balancing policy.
♥Health ChecksLocal endpoint monitoring and recovery logic.
⇄TCP/UDP BalancingL4 distribution with optional Source NAT.
▤Zones & ViewsStandard DNS server capabilities with source-aware views.
When Dedicated Edge fits best
Use your infrastructure strategy as an advantage, not a limitation.
Dedicated Edge is a strong fit when the traffic plane needs to live inside an existing cloud account, private network, customer-controlled security boundary, or workload-specific environment — while still benefiting from centralized policy and automated lifecycle management.
Public Cloud Workloads
Place GLB nodes close to applications already running in your cloud regions.
Private Infrastructure
Operate the traffic plane inside private cloud or datacenter environments where locality matters.
Isolation Requirements
Keep node infrastructure dedicated to one tenant while retaining centralized management and software control.
Want the GLBSAAS traffic engine inside your environment?
Tell us where you want nodes placed, how your applications are segmented, and what traffic behavior you need. We’ll map the Dedicated Edge model to your infrastructure.