Versa Director is the centralized management and orchestration platform of a Versa deployment: the console where administrators onboard devices, build configuration templates, define networking and security policy, and monitor every VOS device and service across branches, data centers, clouds, and remote users.
Key takeaways
- Single pane of glass for provisioning, policy, and monitoring of VOS estates.
- Template-driven configuration scales one design to thousands of devices.
- Full multi-tenancy: providers administer isolated customer organizations.
- Northbound REST APIs expose everything the GUI can do to automation.
- Pairs with Versa Analytics (visibility) and Versa Concerto (cloud portal).
On this page: Why it mattersHow it worksVersa Director deployment modelsVersa Director & the VersaONE platformFAQ
Why is Versa Director important?
A software-defined network is only as manageable as its control plane. Versa Director is that control plane for the management dimension: without it, every VOS device would be an island configured by hand. Director turns network and security design into reusable templates, pushes them to fleets of devices, and keeps the intended configuration and the running configuration in agreement – the property that makes hundred-site and thousand-site deployments operable by small teams.
It also carries the operational load after day one: real-time status of appliances, tunnels, and services; alarm handling; software upgrades; and license entitlement across the estate. For service providers and large enterprises, its multi-tenant model is the business enabler – one Director hierarchy can administer many isolated customer organizations, each with its own admins, templates, and policies, without standing up separate management stacks.
What is Versa Director?
Director is the management and orchestration member of the Versa headend, alongside the Controller (the SD-WAN control plane the devices connect through) and Versa Analytics (the telemetry and reporting engine). Administrators work in Director’s GUI or through its REST APIs; the Director GUI overview tours the console itself.
Its central abstraction is the template: device templates and service templates capture a design once – interfaces, routing, tunnels, security policy – with variables bound per device at deployment time. Workflow-driven onboarding stages a new branch from factory state to full production configuration without manual box-by-box work; the configuration templates overview explains the model. Organizations (tenants) scope everything: appliances, templates, policies, and administrator roles.
Versa Director deployment models
Director deploys in three main shapes. Standalone suits labs and small estates: one Director node carries the full management plane. High-availability pairs are the production norm – an active and a standby Director with synchronized state, so management survives a node failure. Provider hierarchies serve carriers and MSPs: a provider-level Director administers many customer organizations, optionally delegating scoped administration to each tenant – the same model VersaONE’s 256-tenants-per-system architecture builds on. In SASE deployments, Director runs behind Versa Concerto, which provides the cloud-native portal while Director continues to orchestrate the underlying estate.
Versa Director & the VersaONE platform
Within VersaONE, Director is the orchestration layer of the management infrastructure: Concerto provides the SaaS portal experience, Director executes orchestration against the devices, the Controller anchors the SD-WAN fabric, and Analytics turns device telemetry into dashboards and reports. Every capability in the console is mirrored by northbound REST APIs, which is how automation pipelines, provider OSS/BSS systems, and Versa’s own portals drive the platform programmatically.
Frequently asked questions
What is the difference between Versa Director and Versa Concerto?
Concerto is the cloud-native SaaS portal – the modern front door for SASE and SD-WAN services. Director is the orchestration engine beneath it: templates, device lifecycle, and policy execution. Concerto deployments still rely on Director orchestrating the estate underneath.
What is the difference between Versa Director and the Versa Controller?
Director is the management plane: configuration, templates, monitoring. The Controller is the SD-WAN control plane: devices establish secure tunnels to it and exchange routing over MP-BGP. Director tells devices what to be; Controllers keep the fabric connected.
Can Versa Director manage multiple customers on one system?
Yes. Director is multi-tenant by design: a provider organization administers isolated customer organizations, each with its own appliances, templates, policies, and administrators. Providers can delegate scoped administrative access per tenant.
Does Versa Director have an API?
Yes. Director exposes northbound REST APIs covering onboarding, configuration, monitoring, and administration – the same operations as the GUI – plus event and alarm notification streams for integration with external systems.
How do configuration templates work in Versa Director?
Templates capture a design once, with variables for the values that differ per site – addresses, circuit details, site IDs. Deploying a device binds its values to the template, and later template changes roll out to every bound device in a controlled push.
More on Versa Director
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 Director manages – capabilities, editions, and architecture briefs. | How the SD-WAN service Director orchestrates is packaged and delivered, from the vendor. | Versa’s training portal: courses and labs that use Director hands-on, from onboarding to advanced policy. |
Related terms
If you’re reading about Versa Director, these are worth looking at next.
| Versa Concerto | Controller | Device Template |
|---|---|---|
| The cloud-native SaaS portal that fronts Director in SASE deployments. | The SD-WAN control-plane node every VOS device connects to for routing and fabric membership. | The reusable configuration design Director binds to each device at deployment. |