SD-WAN cost has five parts: edge devices or licenses per site, bandwidth, the controller or management service, security add-ons, and the staff time to run it. We do not quote prices here. Prices change by vendor and term, so compare quotes using the same site list and the same assumptions.
Why is there no single price?
Vendors package SD-WAN differently. One quote bundles hardware, a subscription and support. Another sells a license for software you run on your own appliance. A third folds in a cloud security service. A headline per-site number tells you little until you know what it includes.
We have not fetched any vendor price list for this post and will not guess at figures. If you see a number quoted in a blog without a date and a source, treat it with care.
What are the cost drivers?
Sites and their size. Cost scales with the number of sites and the throughput each needs. A 10-person office and a warehouse with 200 scanners are different sizing problems.
Links. SD-WAN often lets you swap one expensive circuit for two cheaper ones. The saving, if any, shows up on the carrier bill, not the SD-WAN quote.
Subscription term and tier. Longer terms usually lower the monthly rate and raise your lock-in. Features such as application-aware routing or advanced analytics may sit in a higher tier.
Security. NIST SP 800-215 treats secure web gateways, firewalls and zero trust access as separate functions in the enterprise network. If they are not in the SD-WAN quote, they are somewhere else in your budget.
Operations. Who runs it? A managed service has a monthly fee. Running it yourself costs training, on-call time and the risk of a bad policy push.
Lifecycle. Edge hardware reaches end of support. CISA's directive on end-of-support edge devices is aimed at federal agencies, but its logic applies to everyone: plan replacement before support ends, and budget for it.
How do you make quotes comparable?
Constructed example: you have 25 sites, and 5 of them are large. Ask every vendor to quote the same three lines.
- 20 small sites, each with one broadband and one cellular link
- 5 large sites, each with two broadband links and a need for more throughput
- The same security functions in every quote, or an explicit "not included" line
Then ask each to state the contract term, the support hours, and what happens to your devices at the end of the term.
What should you ask about contract terms?
Ask what happens if you add or remove a site mid-term, and whether per-site pricing changes with bandwidth tiers. Ask how upgrades are handled: do new software versions arrive within the subscription, or cost extra? Ask what exit looks like. If you leave, can you keep the devices, export your configuration and policies in a usable format, and how long do you have to migrate?
Also ask for the response time on support tickets in writing. A cheap quote with business-hours support can cost more than a dearer one if a branch outage hits a Sunday trading day.
How to check or apply this
- Count sites, group them by size, and list the links each has now.
- Decide which security functions must be in scope, and ask each vendor to price them separately.
- Ask whether hardware is bought, leased or bundled, and who owns it at the end.
- Ask for the end-of-support date for every device model quoted.
- Add your own cost: engineer time, training, and the carrier bill changes.
- Request a pilot, then price from the pilot's real throughput rather than the datasheet.
Quick check
Is SD-WAN cheaper than MPLS?
Sometimes, mainly because broadband and cellular links can cost less than private circuits. The result depends on your sites, your carrier prices and the performance you need, so model your own numbers.
What is the most common hidden cost?
Security and operations. If inspection, segmentation and admin time are left out of the quote, you pay for them later.
Sources
- NIST SP 800-215, Guide to a Secure Enterprise Network
- CISA BOD 26-02, Mitigating Risk From End-of-Support Edge Devices
Last reviewed: 18 October 2026.
