Skip to main content
APPLIANCES

One Platform · Six Form Factors · Same Software

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 six doors — virtual and five 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.

Licensing Wizard
SIX FORM FACTORS · ONE PLATFORM

Which Appliance Fits Your Deployment?

Each appliance page details one model — throughput, port options, deployment scenarios, and operational envelope. Software is identical across all.

APPLIANCE PHILOSOPHY

Four Principles Across All Six Form Factors

Hardware decisions should be about scale and topology — never about which features you get to use.

Feature Parity, Not Feature Tiers

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.

Migration Without Reconfiguration

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.

Operational Resilience Built In

Active-active clustering, automatic failover, RMA programs, and proactive health monitoring are platform capabilities — not features tied to specific hardware classes.

An Image That Cannot Drift

The appliance is an immutable system image, not an application installed onto a general-purpose OS. Nothing is patched file by file, so two devices on the same version are the same device. Updating means writing the next image into the second slot and booting into it; if the post-boot health check fails, the appliance returns to the previous slot by itself. A bad update cannot leave you with a box that will not come back.

Which Appliance Matches Your Scale?

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.

Licensing Wizard

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.