Tell us your sites, the speed you need to fill, and how much you move — we’ll recommend the right configuration from the same architecture, from a compact Mini Appliance at the edge to a datacenter scale-out cluster, and how many you need.
No sign-up to download. Want it sized and quoted exactly for your sites? Share your details and our team will follow up.
The tier follows the speed you want to fill — it is the same co-designed stack at every scale. The count is a starting footprint; final sizing depends on your storage, links, and targets. Get an exact configuration for your environment →
Zettar — Suggested deploymentHow sizing works: it is one co-designed stack at every scale — a compact Mini Appliance for edge links (1–10 Gbps), the HPE DL380 core node for 100 Gbps, and multi-node scale-out for 400 Gbps and beyond. One unit per site sends and receives; high availability adds a redundant unit, and zx clusters self-heal.
Next step: zettar.com — schedule a demo for an exact configuration and quote.
One co-designed stack scales from a compact Mini Appliance at the edge (1–10 Gbps), to the HPE DL380 core node at 100 Gbps, to multi-node scale-out at 400 Gbps and beyond — so the tier follows the speed you need to fill. Each unit is symmetric, sending and receiving, so one per site covers a location; high availability adds a redundant unit, and because zx clusters self-organize and self-heal, throughput grows linearly as you add nodes with no software ceiling.
The tier follows the speed you want to fill, from one co-designed architecture: a compact Mini Appliance for edge links (1–10 Gbps), the HPE ProLiant DL380 Gen 11 core node for up to 100 Gbps, and multi-node scale-out (roughly one node per 100 Gbps) for 400 Gbps and beyond. For count, start with one unit per site — each is symmetric, sending and receiving — plus a redundant unit per site for high availability. The tool gives a starting footprint; a demo sizes it exactly.
Moving data between locations needs an endpoint at each one. Because each appliance handles both directions, you don't need separate send and receive boxes — one per site covers it, plus a redundant unit per site if you want high availability.
Both. One appliance runs at line rate for the link it drives; to go beyond that, zx scales out — clusters are peer-to-peer, self-organizing, and self-healing, with no software ceiling, so aggregate throughput grows as you add nodes (about one per 100 Gbps).
Tell us your sites, links, and targets — we’ll size the deployment and quote it as one supported solution.