Multi-Organization Control
Operate many customer organizations from one administrative surface instead of maintaining a separate management plane per customer.
Service-provider operations
MSP & Multi-Tenant Scale Customers, Not Operational Overhead.
Operate multiple organizations from one shared GLBSAAS control plane with server-enforced tenant isolation, authorization-aware experiences, delegated administration, and flexible edge placement across customer environments.
MSP Control PlaneTenantCustomer AIsolated scope
TenantCustomer BIsolated scope
TenantCustomer CIsolated scope
TenantCustomer DIsolated scope
Operational leverage
One operating surface for many customer organizations.
The MSP model is built for service providers that need to centralize operations without collapsing customer boundaries. Manage customers, Regions, Edge Nodes, policy, software, and traffic services from one platform while preserving server-enforced authorization and isolation.
Server-Enforced Boundaries
Tenant separation is enforced by the platform authorization model rather than relying on user-interface convention.
Operational Scale
Standardize traffic operations across customers while retaining deployment flexibility for different customer requirements.
Authorization-aware operations
Give the right operator the right view of the right customer.
GLBSAAS uses organization scope and role-aware authorization so Platform, MSP, and Tenant experiences remain distinct. MSP operators can manage eligible customer organizations while tenant users stay constrained to their authorized customer context.
- MSP-level administration
- Tenant-scoped experiences
- Server-enforced authorization
- Delegated operational workflows
- Region and Edge Node ownership boundaries
- Shared platform, isolated configuration
Multi-tenant control model
MSPService-provider administrators manage eligible customer organizationsShared operations
TENANT ACustomer-specific policy, DNS objects, Regions, and nodesIsolated scope
TENANT BIndependent configuration and authorization boundaryIsolated scope
TENANT C+Repeat the operating model without multiplying control planesScalable
Customer deployment flexibility
MANAGEDUse Cloud Global Edge for customers that want a SaaS operating modelGLBSAAS operated
DEDICATEDPlace dedicated Edge Nodes in customer public/private cloudCustomer aligned
HYBRID OPSStandardize policy and software operations across mixed customer modelsOne control plane
TRAFFICKeep the same DNS, health, persistence, Geo/IP, and failover foundationConsistent engine
Same traffic platform
Standardize the service you sell while flexing how each customer deploys.
The MSP operating model is not a reduced feature tier. Customers can consume the same traffic intelligence — authoritative DNS, global load balancing, persistence, Geo/IP policy, health checks, failover, TCP/UDP balancing, zones, views, and software lifecycle — through the deployment approach that best matches their needs.
◎Global DNS Load BalancingHealth-aware traffic distribution across customer services.
▣PersistenceOptional source affinity with peer synchronization.
⌖Geo/IP PolicyRule-based filtering and traffic steering per customer.
♥Health ChecksEndpoint monitoring and automatic failover.
⇄TCP/UDP BalancingL4 traffic distribution with optional Source NAT.
▤DNS Zones & ViewsStandard DNS services in the same tenant-aware platform.
Designed for service-provider economics
Increase customer reach without rebuilding the operating model every time.
A shared control plane gives MSPs a common place to manage customer lifecycle, traffic policy, deployment, and software operations. That reduces duplicated administration while keeping customer boundaries explicit.
Repeatable Operations
Apply a consistent service-delivery model across many customer organizations.
Flexible Edge Ownership
Support customers on managed global edge or dedicated infrastructure without changing control planes.
Central Software Control
Coordinate GLB Node software lifecycle through the platform instead of customer-by-customer manual maintenance.
Building a managed traffic service for multiple customers?
Tell us how your customers are structured, where their workloads run, and which operations you want to centralize. We’ll map the GLBSAAS MSP model to your service-delivery strategy.