Versa Concerto is Versa’s cloud-based orchestration and lifecycle management platform: the portal where administrators configure, deploy, and monitor SD-WAN, Security Service Edge (SSE), and SASE services, policies, and profiles across tenants and Versa Cloud Gateways. It is the cloud-native counterpart to Versa Director, built for providers and enterprises rolling out SASE at scale.
Key takeaways
- Concerto is Versa’s cloud-native orchestration and lifecycle portal.
- Work is organized into lifecycles: Tenants, Configure, Deploy, Inventory, View.
- A tenant model supports MSP providers and their sub-tenants.
- Northbound REST APIs, exposed via a Swagger UI, mirror the GUI.
- Concerto configures cloud gateways; Director configures on-prem SD-WAN hubs.
On this page: Why it mattersHow it worksVersa Concerto deployment modelsVersa Concerto & the VersaONE platformFAQ
Why is Versa Concerto important?
SASE only works as a service if standing it up doesn’t require a project for every tenant. Concerto is Versa’s answer to that: a cloud-native portal that turns tenant onboarding, SSE gateway provisioning, and policy configuration into repeatable workflows instead of one-off engineering. That matters most for providers and enterprises rolling out SASE at scale, where dozens or hundreds of tenants each need isolated configuration, dashboards, and administrators without a separate management stack per customer.
It also carries the operational load once services are live: Concerto’s Deploy lifecycle publishes and commits configuration changes to gateways and devices, its Inventory lifecycle manages VOS software and security-pack (SPack) upgrades, and its View lifecycle surfaces security dashboards – alerts, risk scores, protection statistics – so administrators can see what the policies they configured are actually doing.
What is Versa Concerto?
Concerto organizes work into lifecycles visible in its navigation. Tenants lists and manages customer organizations, including MSP mode where a parent tenant provisions and propagates configuration to sub-tenants. Configure builds Secure SD-WAN and SSE configuration as reusable objects – profile elements, policies, and master profiles – arranged hierarchically so one design can apply to many devices. Deploy sets up topologies (regions, sites, devices) and pushes configuration through a two-step publish-and-commit process. Inventory manages the software lifecycle: VOS upgrades and SPack updates delivered to appliances. View surfaces Security dashboards for a tenant’s traffic, threats, and policy effectiveness.
Every capability is also exposed through northbound REST APIs, browsable and callable from a built-in Swagger UI, and Concerto includes Verbo, an in-portal chatbot that answers configuration questions and helps troubleshoot issues.
Versa Concerto deployment models
Concerto’s orchestrator node installs in two shapes. Standalone runs the full orchestration stack on one node, suited to labs and smaller estates. Cluster mode distributes the orchestrator across multiple nodes for scale and resilience – the shape referenced when a cluster node’s own disk needs resizing, for example. Alongside its own installation, Concerto is one of three headend components – with Director and Analytics – that can be deployed together as VMs, for example on VMware ESXi.
Concerto’s SSE service itself runs from Versa-hosted cloud gateways (VCGs) in Versa’s cloud, which Concerto’s Configure and Deploy lifecycles provision and manage directly – distinct from the orchestrator node’s own standalone-versus-cluster installation choice.
Versa Concerto & the VersaONE platform
Within the VersaONE platform, Concerto is the cloud-native front door: it is where administrators configure SaaS and IaaS connectors for API-based data protection – CASB and DLP scanning for applications like Box, Salesforce, and AWS – and where they provision the Versa Cloud Gateways that anchor SSE. For enterprises extending an existing SD-WAN, Concerto’s cloud-hosted SSE integrates with an on-premises Director-managed SD-WAN hub: Concerto configures BGP peering policies and site-to-site tunnels on the gateway side, while Director configures the corresponding tunnel interfaces and routing on the hub side, together forming a unified SD-WAN–SSE (SASE) solution.
Frequently asked questions
What is the difference between Versa Concerto and Versa Director?
Concerto is the cloud-native SaaS portal for provisioning SSE and SASE services and Versa Cloud Gateways. Director is the on-premises-oriented orchestration engine for SD-WAN hubs and branch devices. Many SASE deployments run both together, each managing its own side of the fabric.
What is a tenant in Versa Concerto?
A tenant is an isolated customer organization within Concerto – its own configuration, policies, dashboards, and administrators, scoped separately from every other tenant on the system. Concerto supports MSP mode, where a parent tenant provisions and propagates shared resources down to the sub-tenants it manages, with dedicated or shared Versa Cloud Gateway assignments per sub-tenant.
Does Versa Concerto have an API?
Yes. Every Concerto capability is mirrored by northbound REST APIs, browsable and testable through a built-in Swagger UI that supports authorization, spec navigation, and client code generation – the same interface administrators use to make their first API call, such as creating an Internet Protection Rule.
What is Verbo in Versa Concerto?
Verbo is Concerto’s built-in chatbot. Administrators ask it configuration questions, get step-by-step guidance, and use it to help troubleshoot network issues directly inside the portal, without leaving the GUI to search separate documentation, and can download session transcripts for later reference.
Can Versa Concerto run in a cluster?
Yes. The Concerto orchestrator node installs either standalone, for labs and smaller deployments, or in cluster mode, which distributes the orchestrator across multiple nodes for scale and resilience, alongside the Director and Analytics headend components it typically deploys with.
More on Versa Concerto
If you want to learn more, these are sources we trust.
| Versa Networks: platform | Versa Networks: secure SD-WAN | Versa Academy |
|---|---|---|
| The vendor’s product pages for the platform Concerto orchestrates – capabilities, editions, and architecture briefs. | How the SD-WAN service Concerto provisions and monitors is packaged and delivered, from the vendor. | Versa’s training portal: courses and labs that use Concerto hands-on, from tenant setup to SSE policy. |
Related terms
If you’re reading about Versa Concerto, these are worth looking at next.
| Versa Director | Tenant | Versa Analytics |
|---|---|---|
| The orchestration console for on-premises SD-WAN hubs and branch devices – Concerto’s counterpart for the fabric side. | The isolated customer organization every Concerto configuration, policy, and dashboard is scoped to. | The headend component that turns device telemetry into the dashboards Concerto’s View lifecycle surfaces. |