Enterprise, Secure, GeoAccess, Geo, and Base — module combinations matched to recurring deployment patterns, with predictable licensing.
Most enterprise deployments cluster around a handful of patterns: full-stack security, defense-focused, geographically distributed, or foundation-only. TR7 Solution Bundles map these patterns to validated module sets, removing weeks of license modeling and capacity planning from the procurement cycle.
This page opens five doors — one per bundle. Pick the bundle that maps to your deployment shape, or compare across them to see where the boundaries sit.
Five bundles. One platform. Predictable contracts.
Each bundle is a validated combination of modules, capacity envelopes, and licensing terms — chosen to fit a specific operational pattern without forcing point-by-point license assembly.
Each bundle page details one combination — included modules, common scenarios, capacity envelopes, and the contract shape that follows.
Full-stack: ADC + WAAP + AAM + GTM
All four modules under one contract — the complete platform for enterprises that need delivery, protection, identity-aware access, and global routing on a single operational language.
Defense-focused: ADC + WAAP + AAM
Application delivery paired with web protection and identity-aware access. Ideal for deployments where global routing isn't yet on the roadmap but security depth is mandatory.
Multi-region identity-aware: ADC + AAM + GTM
Identity-aware application delivery across multiple regions. Adds AAM identity to the Geo combination — pairs with a +25 ETM endpoint starter and 2-region Central Management, without WAAP.
Multi-region: ADC + GTM
Application delivery combined with DNS-based global traffic management. Designed for multi-datacenter and multi-cloud deployments where geographic routing is the primary requirement.
Foundation: ADC + AAM (+ 25 ETM endpoints)
Application delivery with identity-aware access — the foundational pattern for organizations modernizing how applications are published. Includes a 25-endpoint ETM allowance for device-trust signals.
Bundles are not marketing groupings; they are validated deployment shapes with contract language.
Each bundle is a deployment shape we've validated in the field — module combinations, capacity envelopes, and operational patterns proven against real enterprise scenarios.
Bundle scope is expressed in contract terms — what's included, what counts toward capacity, when add-ons apply. No interpretation gap between sales conversation and renewal.
Moving from Base to Secure, or Secure to Enterprise, is a contract conversion, not a re-deployment. The engine, console, and operational language stay the same.
Each bundle page details what's included and the operational patterns it suits. When you're ready to size capacity and pick a license term, the Licensing Wizard walks through the commercial choices.
Bundle composition, capacity envelopes, add-on availability, and licensing terms may vary by deployment model, appliance class, and contract scope. Refer to the individual bundle pages and the licensing guide for detailed coverage.