What is an Appliance?

An appliance is a physical or virtual device running Versa Operating System (VOS) software – the fundamental building block of a Versa SD-WAN or SASE deployment. The same VOS software runs as a branch appliance, hub, gateway, or Controller node depending on where it’s placed, all managed centrally through Versa Director or Concerto.

Key takeaways

• An appliance is a physical or virtual device running VOS software.
• The same software runs as a branch, hub, gateway, or Controller node.
• Physical appliances span Versa’s CSG and CSX hardware families.
• Virtual appliances run as VMs or as instances in AWS and Azure.
• Analytics dashboards and reports commonly label appliances as sites.

On this page: Why it matters · How it works · Types · Appliances & Versa · FAQ

Why are appliances important?

Appliances are what actually forward, secure, and connect traffic – without a physical or virtual point of presence at each location, SD-WAN and SASE policy has nowhere to run. The same VOS software image has to behave identically whether it’s a compact desktop unit in a home office, a fanless box bolted into a retail branch, a rack-mounted hub aggregating a data center, or a virtual machine spun up in a cloud VPC. That consistency is what lets Versa apply one SD-WAN, security, and routing engine everywhere, and it’s what lets a Director or Concerto operator manage thousands of devices from a single console instead of learning a different model per hardware SKU.

Appliance-level reliability matters just as much as software consistency. High-availability pairing keeps a site online when one device fails, and Director’s per-appliance monitoring – polling interval, reachability, configuration sync status, service status – is how an operator learns a device needs attention before a site actually drops.

What is an appliance?

Every Versa appliance, physical or virtual, runs the same VOS software; the role it’s configured for determines what it does. A branch appliance sits at a customer site and connects over the internet or a private transport such as MPLS. A hub aggregates spoke connections in a hub-and-spoke topology. A gateway terminates client and site traffic as a SASE gateway. A Controller node handles overlay control-plane functions. All four are the same underlying device type wearing a different configuration.

On the hardware side, CSG700 series appliances integrate SD-WAN, next-generation security, unified threat management, on-premises ZTNA, and carrier-class routing “in a single appliance,” running VOS and managed through Director for configuration and provisioning and Analytics for device, network, and security telemetry. The smaller CSG300 series covers the same ground for small businesses and home offices. In Analytics dashboards and reports, these devices are commonly labeled sites rather than appliances – the two terms describe the same object from different parts of the platform.

Types of appliances

Appliances split along two independent axes: role and form factor. By role, an appliance is a branch (deployed at a remote or branch site), a hub (aggregating spokes in a hub-and-spoke design), a gateway (a SASE gateway terminating client and site traffic), or a Controller node (overlay control plane) – the same VOS image, configured differently for each.

By form factor, an appliance is either physical or virtual. Physical appliances are Versa-built hardware: the CSG300 series (CSG350, CSG355, CSG365) targets small branches and home offices, while the CSG700 series (CSG730 through CSG780R) targets small-to-larger enterprise branches needing higher SD-WAN and security throughput, with other CSG and CSX hardware families covering everything from compact edge units up through data-center-class switching. Virtual appliances run the same VOS software as a virtual machine on ESXi or KVM, as an instance in AWS or Azure, or on Versa-certified white-box hardware – the deployment model shifts, but the software, management, and policy model stay identical.

Appliances & Versa

Appliances are provisioned and configured through Versa Director, which also monitors them with configurable polling interval, concurrency, keep-alive timer, and hold-time multiplier settings that determine reachability, configuration sync status, and service status. Concerto layers orchestration on top – Appliance Discovery and Propagate SD-WAN Configuration are tenant-lifecycle actions that bring devices under management and push configuration out to them.

For resilience, cross-connect interfaces link an active and standby appliance pair in a high-availability deployment, so a single device failure doesn’t take a site offline. For SMB and cloud-managed deployments, the Versa Titan Portal and Titan Mobile app handle appliance activation – over Bluetooth, generic zero-touch provisioning (GZTP), or Wi-Fi – plus real-time health monitoring. Hardware appliances carry a two-year limited warranty with dead-on-arrival replacement and optional 24×7 return-to-factory support, and a defective unit follows an RMA process coordinated through Versa Support and the Titan Dashboard.

Frequently asked questions

What’s the difference between a physical and a virtual appliance?

A physical appliance is Versa-built hardware, such as the CSG or CSX series. A virtual appliance runs the same VOS software as a virtual machine on ESXi or KVM, or as an instance in a cloud environment such as AWS or Azure. Both are managed identically through Director or Concerto.

Can the same appliance act as both a branch and a hub?

Role is a matter of configuration, not hardware – any VOS device can be set up as a branch, hub, gateway, or Controller node depending on the network design. Larger CSG and CSX platforms are more commonly deployed as hubs, simply because of their higher port density and throughput.

Why do Analytics dashboards call appliances “sites”?

Analytics reports and dashboards are organized around physical or logical locations rather than device identity, so the same object Director manages as an “appliance” shows up in Analytics as a “site.” The two terms describe the same underlying VOS device from different parts of the platform.

How does Versa Director monitor appliance health?

Director polls each appliance on a configurable interval, tracking concurrency, a keep-alive timer, and a hold-time multiplier to determine reachability, configuration sync status, and service status – surfacing a problem at a site before it actually loses connectivity to the rest of the network.

What happens if a branch appliance fails?

In a high-availability deployment, a standby appliance takes over from the active one over a cross-connect interface, so branch connectivity continues without a technician on site. Non-HA sites instead rely on the RMA process and advance-replacement hardware support plans to recover from a device failure.

More on appliances

If you want to learn more, these are sources we trust.

Related terms

If you’re reading about appliances, these are worth looking at next.