From virtual appliances on any hypervisor to data-center-class physical hardware — the same TR7 software, the same operational language, sized to fit your deployment.
Appliance selection is a capacity and topology decision, not a software decision. The same TR7 platform runs across virtual environments and five hardware classes; what changes between models is throughput, port density, and the engineering envelope underneath — not what you can do with it.
This page opens five doors — virtual and four hardware tiers. Pick the model that fits your deployment scale, knowing the configuration, console, and operational language stay the same as you move up.
Same software. Different sizes.
V7000 runs on any hypervisor; H700 through H27000 span entry deployments to data-center-class density. Capacity scales; the engineering experience does not change.
Each appliance page details one model — throughput, port options, deployment scenarios, and operational envelope. Software is identical across all.
Any hypervisor, any cloud
Full TR7 platform delivered as a virtual appliance — VMware, KVM, Hyper-V, AWS, Azure, GCP, or on-premises virtualization. Scales from lab deployments to production multi-Gbps workloads.
Entry hardware for small to mid deployments
Compact physical appliance for branch, remote site, and entry-level enterprise deployments. Up to 40 Gbps throughput with integrated network modules.
Mid-range with expandable network modules
Mid-tier hardware with module-based network expansion. 40–100 Gbps throughput, multiple NIC options, and headroom for growing application portfolios.
High-performance for large organizations
High-throughput hardware for large enterprises and service-provider tenants. 80–200 Gbps throughput, dense port options, and expanded slot capacity.
Data-center class for service providers
Top-tier hardware for service providers and ultra-high-capacity enterprise data centers. 200–800 Gbps throughput, maximum slot density, and carrier-grade resilience.
Hardware decisions should be about scale and topology — never about which features you get to use.
Every appliance class runs the full TR7 platform. The same modules, the same flow engine, the same API. Hardware selection is a capacity decision; you never trade features for cost.
Configuration moves between models without rewrite. Growing from H700 to H7000, or from virtual to physical, is a deployment swap — not a re-engineering project.
Active-active clustering, automatic failover, RMA programs, and proactive health monitoring are platform capabilities — not features tied to specific hardware classes.
Each appliance page covers throughput envelopes, port options, deployment scenarios, and capacity considerations. When you're ready to size a deployment and pick a license model, the Licensing Wizard walks through the commercial choices.
Throughput envelopes, port density, network module compatibility, and deployment scenarios summarized on this page may vary by software version, configuration, and workload pattern. Refer to each appliance page and the licensing guide for detailed coverage.