Four Enterprise Modules · One Engine · One Operational Language
ADC, WAAP, AAM, and GTM — application delivery, protection, identity-aware access, and global traffic management, all on the same engine.
TR7 products are not isolated point solutions stitched together; they are four capabilities of a single platform. The same engine carries each module, the same visual flow configures it, and the same operational language governs behavior in production.
This page opens four doors. Pick the one that maps to the decision in front of you — delivery, protection, access, or global routing — and explore the module on its own terms.
Four modules. One engine.
ADC carries the application, WAAP defends it, AAM governs who reaches it, GTM routes traffic across regions — all sharing the same data plane and the same control plane.
Which Module Would You Like to Explore?
Each product page examines one module in depth. The four modules share the same operational language, so what you learn in one transfers to the others.
ADC — Application Delivery Controller
Application traffic distribution with engineering depth
Layer 4–7 routing, intelligent health monitoring, SSL/TLS acceleration, content rules, and per-application traffic shaping. The foundation under every TR7 deployment.
WAAP — Web App & API Protection
OWASP coverage with API-aware enforcement
Web application firewall, API security, bot management, virtual patching, and client-side script protection — applied per-application with engine-level integration.
AAM — App Access Management
Identity-aware access for every application
SSO, MFA, conditional access, SAML/OIDC federation, SSL VPN, and clientless portal. Modernize legacy applications without touching their code.
GTM — Global Traffic Manager
DNS-based global routing with disaster recovery
Multi-datacenter GSLB, intelligent geographic routing, datacenter failover, and latency-based traffic steering — operate globally from one console.
Three Principles Binding the Four Modules
The same engineering decisions sit beneath every module — the difference between four products and four capabilities.
Capabilities, Not Point Solutions
Each module is a face of the same engine. A backend pool, a certificate, a health check, or a policy is defined once and consumed by every module that needs it. No integration layer, no synchronization risk.
Engineering Visibility
A traffic decision, a security verdict, an access policy result, or a routing change — every step is traceable, recorded, and explainable through the same audit trail.
One Operational Language
What an operator learns configuring ADC transfers to WAAP, AAM, and GTM. The visual flow, the policy syntax, and the API are the same across modules.
Which Module Would You Like to Walk Through?
Each product page covers one module on its own terms — capabilities, deployment topologies, performance envelopes, and operational considerations. When you are ready to scope a deployment, the Solution Bundles map common scenarios to pre-validated module combinations.
Capabilities, integration scenarios, and performance envelopes summarized on this page may vary by deployment model, appliance class, and selected license bundle. Refer to each product page and the licensing guide for detailed coverage.