Services / Connectivity
SD-WAN
SD-WAN is used where an organisation needs application-aware paths between sites and to cloud services, rather than a single static default route. Overlays are designed on top of the underlay connectivity that each site actually has.
- Overlay
- Policy and path selection
- Underlay
- Circuits the site already has
- Edge
- Appliance or virtual
- Operations
- Documented policy changes
How a typical SD-WAN engagement runs
01
Assess the estate
Site list, applications, underlays and whether an overlay is justified versus simpler routing.
02
Design and cut over
Platform selected to the brief — Verico does not present a single vendor as the default. Existing circuits remain a fallback until the overlay is proven.
03
Operate
Path quality, edge health and policy changes can be included in managed operations, with incidents logged in Verico Clientzone.
Overlay design on a real underlay
Fitness assessment
Whether SD-WAN is appropriate for the estate, given site count, applications and the circuits already in place.
Overlay and breakout model
Path policy, local or central breakout, and how the overlay meets the existing firewall and LAN.
Site edges
Appliance or virtual-edge deployment at each in-scope site, with a cutover that keeps existing circuits as fallback until proven.
Dual underlays
Application and path policy across more than one circuit where the site has them.
Secure breakout
Site-to-site and internet breakout aligned to the security brief, not a second undocumented path.
Inventory and logging
Edges, policy versions and change history that operations can use after handover.
Multi-site environments
SD-WAN is intended for estates with more than one site. Policy can be templated so that a new branch inherits the same path and security posture.
Relationship to connectivity
The overlay does not replace the need for working underlay circuits. Internet and last-mile work is scoped on the Internet & Connectivity page.
Related capabilities
These are quoted separately unless the brief asks for a combined design. They sit on the same ICT estate.
- Internet & ConnectivityBusiness internet and site connectivity engineered around availability, routing and the rest of the ICT estate.Connectivity — read more
- Enterprise LAN & WLANSwitching, VLANs and enterprise wireless designed for coverage, capacity, security and operations.Wireless — read more
- CybersecurityNetwork-centric security controls aligned to the LAN, WAN, identity and the organisation’s operating constraints.Security — read more
- Network MonitoringVisibility of links, devices and services so faults are found before users open a ticket — where the contract includes it.Operations — read more
- Servers, Infrastructure & Managed ICTOn-premises servers, switching and storage, with managed operations and a written service agreement where required.Infrastructure — read more
- Network Infrastructure & Structured CablingCopper and fibre plant designed, labelled, tested and documented for enterprise buildings and campuses.Infrastructure — read more
Common questions
Scope, handover and what is not implied by this page.
Is SD-WAN required for every multi-site estate?
No. Some estates are better served by conventional routing and documented failover. SD-WAN is recommended where application-aware paths and a templated overlay are actually required.
Do you standardise on one SD-WAN vendor?
No. Platforms are selected to the brief. Verico does not present a single vendor as the default.
Discuss an SD-WAN overlay
Request a consultation where multi-site path policy needs to sit on top of the circuits you already have.