Skip to content

11VEXO Ready

Software you install, or hardware that arrives ready.

VEXO runs on hardware you already own. Where a pre-configured node is easier, VEXO Ready profiles describe how a configuration is sized and what it is for.

These are sizing profiles, not a published bill of materials. Components are confirmed per deployment.

11VEXO Ready

Software you install, or hardware that arrives ready.

VEXO Ready profiles describe how a configuration is sized and what it is for. They are not a published bill of materials.

S

VEXO Ready S

Small Business / Branch

A single node sized for a branch site or a small production estate, where the priority is a footprint somebody can actually host on site.

  • Single node
  • Local storage
  • Branch footprint
M

VEXO Ready M

Mid-size Virtualization

A consolidated node for a mid-size estate, with headroom to absorb the workloads currently spread across single-purpose servers.

  • Consolidation node
  • Expanded storage
  • Production sizing
X

VEXO Ready X

Enterprise Cluster

A cluster-oriented configuration for estates that will need multi-host availability once VEXO Protect ships.

  • Cluster-ready
  • High capacity
  • Enterprise sizing

VEXO Ready profiles describe the intended sizing of each configuration. Component-level specifications are confirmed per deployment and are not published here.

VEXO Ready appliances

Delivery

Three ways to get there

The platform is the same in all three. What differs is how much of the assembly you want to own.

01

Software Only

Install VEXO on hardware you already own or specify yourself.

02

VEXO Ready Appliance

Hardware supplied pre-configured to a VEXO Ready profile.

03

Managed Deployment

Deployment carried out with VEXO involvement, including migration planning.

VEXO does not publish a hardware compatibility list yet. Confirm any specific server, storage controller or network adapter with the team before purchasing for a VEXO deployment.

Hardware

Tell us what the workloads look like.

Sizing follows the workloads, not the other way round. Machine count, memory footprint and storage growth are the useful inputs.