TR7 licensing splits into two main lines: Enterprise for your own organization, and Service Provider for offering managed services to your customers.
TR7 licensing is not just a price list. It defines which products you use, which capacity you choose, which operational rights you receive, and how the license renews — all in a clear commercial model.
Every TR7 deployment fits into one of two licensing lines. Enterprise is for organizations that run TR7 for their own applications on their own infrastructure. Service Provider is for data centers, MSPs, MSSPs, ISPs, and cloud providers that deliver TR7 capabilities to downstream customers as a managed service.
Read the Licensing Guide for the full picture, or step directly into the line that matches how your organization uses TR7.
Running TR7 for yourself? Enterprise. Offering it as a service to others? Service Provider.
Both licensing lines share the same TR7 platform, the same product family, and the same operational management experience. What differs is the commercial usage model: your own infrastructure need versus a managed service delivered to customers.
Read the Licensing Guide to see the full licensing model, or step directly into the line that matches how you use TR7.
Comprehensive reference for the TR7 licensing model
License models, bandwidth measurement, capacity tiers, clustering, vService limits, bundles, support, RMA, and frequently asked questions — explained in one place. Start here if you are not yet sure which line fits.
For organizations running TR7 on their own infrastructure
If you use TR7 to publish, protect, and manage your own applications, the right line is Enterprise. Pick CapEx, OpEx, or flexible usage with the Perpetual, Fixed-Term, and PAYG models.
For organizations offering TR7 capabilities as a service to customers
If you are a data center, MSP, MSSP, ISP, or cloud provider delivering ADC, WAAP, AAM, GTM, DDoS, or related security services to your customers, the right line is Service Provider. Customer service licenses layer on top of a Platform License.
Licensing decisions should follow how the organization uses TR7 — the organization should not have to bend its architecture to fit a licensing model.
Each model is explicitly defined in terms of product coverage, capacity, ActiveOps, support, renewal, and usage rights. The goal is to show clearly which right comes with which license — with no grey area after the sale.
When you move between Perpetual, Fixed-Term, PAYG, or Service Provider models, the underlying platform logic and operational language are preserved. What changes is the commercial shape of the contract, not the deployment itself.
Enterprise and Service Provider lines run on the same TR7 product family. The difference is not in technical capability but in usage shape, billing surface, multi-tenant needs, and customer service model.
If you run TR7 for your own organization, look at the Enterprise line; if you deliver it as a service to customers, look at Service Provider. To compare all the details, start with the Licensing Guide.
Licensing coverage, commercial models, capacity tiers, and migration mechanics on this page may vary by deployment model, appliance class, region, and contract scope. For exact scope, refer to the Licensing Guide and the relevant model pages.