SD-WAN vs MPLS: India Branch Office Guide (2026)

The MPLS bill that's quietly ruining your IT budget

I have sat across from finance directors who go pale when they see the annual MPLS renewal. One hospitality group in Whitefield—I won't name them—was paying ₹18 lakh per year for 10 Mbps point-to-point links across 14 locations. Upload speeds were 2 Mbps. The head office in Bangalore connected to a Chennai branch with 45 ms latency, which is acceptable, but the cloud applications they ran—Salesforce, Office 365, a custom ERP—all lived outside the MPLS cloud. So every request hairpinned: branch → MPLS POP → head office → internet → SaaS. That's 80-120 ms added on top of the base latency, and their staff just accepted the spinning cursor.

That setup cost them ₹1.5 lakh per site per month for 10 Mbps. Today, we deploy 100 Mbps broadband at each site for ₹3,000-₹6,000 per month, plus a 4G/5G LTE backup for ₹1,000-₹1,500. Even after adding SD-WAN hardware and management fees, the annual cost drops to ₹4-6 lakh for all 14 sites. Performance? Their ERP transactions went from 8 seconds to 1.5 seconds. The CFO now asks why we didn't do this two years earlier.

This is the pattern I see across Indian enterprises, from 20-user offices in Pune to 500-user factories in Coimbatore. They don't have an MPLS problem, they have a networking architecture problem—they bought MPLS when it made sense, but the cloud has moved the goalposts.

SD-WAN explained without the vendor fluff

Software-Defined WAN (SD-WAN) is a way to build a wide-area network that runs over ordinary internet connections instead of expensive private circuits. It's not a single product, but a set of capabilities—centralized control, application-based routing, and automatic failover—that turn a bunch of cheap broadband links into something that performs like MPLS for most purposes.

The control plane is software, which means you manage all sites from one dashboard. The data plane is shared across multiple links—typically a mix of broadband, LTE, and sometimes still MPLS as a backup. The magic is in how SD-WAN decides which link carries which traffic.

Example: A branch office in Hyderabad has a 100 Mbps fiber from Airtel and a 50 Mbps LTE from Jio. The SD-WAN appliance at the site—say a FortiGate 90G or a Cisco Catalyst 8300—continuously measures both links. When an engineer opens a video call on Microsoft Teams, the SD-WAN steers that traffic over the link with the least jitter. Meanwhile, bulk backups to AWS go over the cheaper or less utilized link. If either link drops, traffic moves in milliseconds—not the 30-60 seconds you'd wait for BGP to converge on an MPLS router.

This is fundamentally different from MPLS, where all traffic—video, backup, ERP—travels the same path, and you pay a premium for quality that only some applications actually need.

MPLS in India: what you're actually paying for

MPLS (Multiprotocol Label Switching) is a carrier-grade private network. Your traffic enters the provider's cloud via an access circuit—often a leased line—and is label-switched through their backbone to a hub, usually your head office or data center. It's reliable and private, but it's expensive and architecturally wrong for cloud-centric traffic.

Typical MPLS costs in India (2026 pricing)

The table below shows realistic monthly costs from tier-1 providers like Airtel, Tata, and Reliance Jio. Quotes vary by city and the provider's existing fiber coverage, so take these as planning numbers, not final quotes.

Notice the jump: a 10 Mbps MPLS circuit costs ₹4.5-6 lakh per year, while a 100 Mbps broadband line costs a fraction of that. Even a 100 Mbps ILL is ₹1.2-1.5 lakh—still one-fourth the MPLS price for ten times the bandwidth.

Why MPLS prices are so high

MPLS providers don't charge for bandwidth alone. They charge for the guarantee. The provider commits to quality of service (QoS) across their backbone—no packet loss, minimal jitter, and a 99.95% uptime SLA. That guarantee comes with engineering overhead and redundancies, which you pay for whether you use them fully or not.

In India, MPLS also has a last-mile monopoly problem. If your factory three blocks from Chennai is only served by one fiber provider, that quote will be 30-50% higher than in a dense metro. I've seen 2 Mbps MPLS to a Chennai suburb quoted at ₹30,000 per month because they knew the customer had no alternative.

The real problem: MPLS breaks with cloud

Let me lay out the architectural flaw. Your MPLS network typically looks like this:

• Branch offices connect to a hub (your head office or data center).
• All internet-bound traffic—SaaS, web, email—goes from branch to hub, then out to the internet via a shared gateway.
• This creates a bottleneck and adds latency because traffic travels an extra leg.

When your CRM is in Salesforce, your branch users are hitting the MPLS cloud, then the internet, then Salesforce's servers. That's three hops too many. It's no wonder that opening a Salesforce record takes 5-15 seconds on MPLS.

I measured a client's network last year. Their Chennai branch, using MPLS to a Bangalore hub, saw 85 ms latency to Microsoft 365. Direct broadband from the same branch gave 35 ms. The MPLS path was adding 50 ms—about 60% more—because of the hairpin. That's the latency you feel when video stalls or a CRM screen takes forever.

SD-WAN costs in India: what a real deployment runs

Now let's talk numbers. SD-WAN is not a single box; it's a solution with hardware, software, and ongoing management. Here's a breakdown for a typical 25-site enterprise (2026 pricing, in INR):

For a 25-site setup, total first-year cost (hardware + installation + 12 months of connectivity) is around ₹18-25 lakh. Ongoing annual cost (licenses amortized + connectivity) is ₹15-20 lakh. Compare that to MPLS: 25 sites at an average of ₹5 lakh per site per year is ₹1.25 crore annually. SD-WAN saves you ₹1 crore in the first year, and you get 10-50x more bandwidth.

Vendor options in India

You have choices. The big three are Cisco (Catalyst 8300, viptela), Fortinet (FortiGate SD-WAN), and VMware (VeloCloud, now part of Broadcom). I'll give you my honest take:

• Fortinet: Their FortiGate 60F/90G series is a workhorse. It does firewall + SD-WAN in one box. Great if you need both. License is per device, around ₹50,000 for 3 years.
• Cisco: The Catalyst 8300 line is solid but pricey. You'll pay ₹2-3 lakh per unit. For enterprises already standardized on Cisco, the management integration is worth it.
• VMware VeloCloud: Excellent for multi-cloud and SaaS optimization, but hardware costs ₹1.5-2 lakh per site. Overkill for most Indian SMEs.
• Cheaper alternatives: Prisma SD-WAN (Palo Alto) and Aruba EdgeConnect SD-WAN are also present, but their India support can be thin.

Honestly, for a 50-user branch, Fortinet is the sweet spot. A FortiGate 90G costs around ₹40,000, and you can run two WAN links plus LTE failover. It's also fine as a firewall, so you might even retire an old standalone firewall.

No, SD-WAN won't fix everything

I need to temper the enthusiasm. SD-WAN is not a silver bullet. Here are three things it does not do:

1. It cannot fix a bad last-mile. If your site only gets 10 Mbps broadband, SD-WAN won't create bandwidth. You need to upgrade the underlay.
2. It cannot guarantee latency to SaaS. It can only choose the best link at the moment. If both links have 50 ms to AWS, you're stuck with 50 ms.
3. It will not reduce your need for a secure gateway. SD-WAN has built-in encryption, but you still need a proper firewall for deep inspection.

The biggest misconception is that SD-WAN replaces MPLS entirely. In some cases, keeping a small MPLS circuit for critical voice or legacy systems is wise, and SD-WAN can use it as one of the underlay links. That hybrid approach is often the most cost-effective.

A real failure story: the ₹12 lakh outage

In 2024, a logistics company in Bangalore with 22 branches signed up for an SD-WAN deployment from a vendor who shall remain nameless. They bought cheap broadband from a local ISP, skipped LTE backup, and set zero QoS policies.

Three months in, during the southwest monsoon, one of their branch links went down because a fiber cut in a rain-drenched trench. The SD-WAN failed over to the other broadband link, which was the same ISP—so that also died because the cut was in the same physical cable run.

No secondary path meant the branch was offline for 22 hours. On an average day, they process 1,200 delivery scans per branch. At ₹200 per scan in lost revenue and detention penalties, that branch alone cost them ₹5.28 lakh. The company had no failover, and their 'SD-WAN' was just an expensive router.

They called us after the fact. We replaced the ISP with dual carriers—Airtel and Jio—and added a 4G LTE backup. Total cost: ₹35,000 per site. That's nothing compared to the previous single outage.

The lesson? Always use two different physical ISPs, and don't rely on a single last-mile. SD-WAN works only as well as the underlays you give it.

Migrating from MPLS: a phased plan that works

You don't have to rip out MPLS overnight. Here's a phased migration approach that minimizes risk:

Phase 1: Assessment and design (weeks 1-4)

• Audit every branch: current MPLS bandwidth, application portfolio, latency tolerance.
• Map your applications: which are cloud, which are in-house? Use a tool like Auvik or even a spreadsheet.
• Identify critical links: sites where you need 99.99% uptime (e.g., manufacturing) vs. those that can tolerate brief outages.
• Choose a pilot branch. Pick a mid-complexity site, not the most critical, not the simplest.

Phase 2: Pilot deployment (weeks 5-8)

• Install SD-WAN at the pilot site in parallel with MPLS. Run both for 2 weeks, comparing performance.
• Test failover scenarios: kill the broadband, measure recovery time.
• Validate QoS: make sure your ERP traffic gets priority over Netflix.
• Based on results, adjust policies.

Phase 3: Roll out in batches (weeks 9-16)

• Roll out to 5-10 sites per week, depending on your team's bandwidth.
• Use zero-touch provisioning: ship the box, have the local admin plug it in, and the controller configures it remotely. This works with Fortinet and Cisco.
• Keep MPLS active for another month as a safety net, but gradually route more traffic over SD-WAN.

Phase 4: Cut over and decommission MPLS (weeks 17-20)

• Once you're confident, downgrade MPLS to lower bandwidth or disconnect entirely.
• Repurpose the MPLS port for something else, or cancel the contract after the notice period.
• Document everything: link providers, credentials, fallback procedures.

Important: Your ISP diversity

In India, the biggest risk is that two 'different' broadband providers share the same underlying fiber pit or pole. Always verify physically different paths. Ask the ISPs for their route maps; if both come from the same exchange, find another provider.

Also, don't forget the monsoon. Bangalore's notorious flooding can knock out hard-wired links if they run through waterlogged areas. 4G/5G backup is essential during June-October.

SD-WAN for Indian-specific challenges

Let me get practical about India:

• GST and bills: SD-WAN hardware is an asset, so you'll pay GST @18% which is input-creditable if you're registered. Broadband bills also include 18% GST, which you can offset. Keep a separate cost-category for 'network infrastructure' to track ROI.
• CERT-In compliance: If you handle government or critical-sector data, you're subject to CERT-In directives. SD-WAN doesn't exempt you from security monitoring. In fact, you might need to log traffic centrally—which SD-WAN controllers do by default.
• DPDP Act 2023: Having a multi-branch network means you control personal data across sites. SD-WAN encryption in transit helps with data security obligations. Just ensure your controller doesn't send sensitive data to a cloud outside India; choose a controller location or on-premises option if needed.
• ISP lead times: In Bangalore, getting a new broadband line via Airtel or ACT can take 5-15 working days. Plan around that. For remote locations, it might be 4-6 weeks. Order your primary and backup links early.
• Power reliability: Indian power cuts are unpredictable. Install a UPS at each branch that can power the SD-WAN box and router for at least 30 minutes. Otherwise, your failover is useless.

Application steering: a quick guide

One of the most underutilized SD-WAN features is application steering. This lets you define which link each application uses based on business need.

• Real-time (voice, video): Use the link with lowest jitter and packet loss. Usually the premium broadband.
• Business critical (ERP, CRM): Use the most stable link, but allow failover.
• Bulk (backups, data transfer): Use the cheapest link, even if it's slow, because latency doesn't matter.
• Default (web browsing): Any link.

In FortiGate, you set up SD-WAN rules based on application signatures. For example, you can match Skype for Business or Microsoft Teams and bind it to the 'primary' link. For backup traffic, match 'Amazon S3' and set it to the 'secondary' link.

I've seen a manufacturing client cut their backup completion time from 9 hours to 3 hours by steering it to a cheaper high-bandwidth connection, while keeping their critical MES (manufacturing execution system) on the low-latency link.

Managed SD-WAN: when you should consider it

The hardware cost isn't the only expense. You need someone to design policies, monitor the network, and handle firmware updates. If your IT team has fewer than five people, you're likely stretched. That's where managed SD-WAN comes in.

We at SynergyScape offer managed SD-WAN services, but honestly, not everyone needs it. Here's a rule of thumb:

• If you have zero network engineers and a single site, skip SD-WAN; just get a good firewall and load balancer.
• If you have 5-20 sites and one IT admin, you'll benefit from a managed service. You'll save hours of troubleshooting, and the MSP can handle vendor coordination.
• If you have a seasoned network team, you can self-manage with tools like FortiManager (which costs extra) or Cisco vManage.

Managed service fees are typically ₹5,000-10,000 per site per month, which is a fraction of the cost of a full-time network engineer (₹18,000-25,000 per month). For a 10-site company, that's ₹50,000-1,00,000 per month for an MSP—you'd need that much in engineering salary to do it in-house.

Real ROI: a case example

Let me give you a concrete ROI calculation from a client in the pharmaceutical distribution space. They had 12 branches across tier-2 cities, each with a 4 Mbps MPLS at ₹45,000 per month. That's ₹5.4 lakh per year per site, total ₹64.8 lakh.

We deployed FortiGate 60F SD-WAN at each site, using two 100 Mbps broadband (one Airtel, one BSNL) at ₹4,000 per month each, plus a 4G LTE backup at ₹1,500 per month. Hardware cost ₹55,000 per site, one-time. Total first-year cost: hardware ₹6.6 lakh + connectivity ₹5.4 lakh = ₹12 lakh. In subsequent years, only ₹5.4 lakh connectivity.

Net savings in year one: ₹52.8 lakh. That's a 81% reduction. Application performance: their Tally ERP consolidated reports now load in 2 seconds instead of 8. They also got video surveillance at branches, which was impossible before due to low MPLS bandwidth.

What not to do

Here's a list of mistakes I've seen repeatedly:

1. Using the same ISP for both links. I already told you the horror story. Always use two distinct providers.
2. Buying expensive Cisco when Fortinet would do. Cisco is great if you have the budget and already use it. But for a 20-user office, the price difference isn't justified.
3. Ignoring security. SD-WAN is not a firewall. You still need UTM features like IPS, antivirus, and content filtering. With Fortinet, you get these in the same box.
4. Not testing failover. You must test failover every quarter. Simulate a link failure and see if traffic moves as expected.
5. Forgetting about DHCP and DNS. SD-WAN appliances often need to handle DHCP and DNS for branches. If you don't configure them properly, users will experience issues.

Conclusion: MPLS isn't wrong, just overpriced

MPLS served India well for two decades. But the cloud era has rendered it obsolete for most applications. SD-WAN gives you better performance at half the cost, with the added benefit of simpler management and faster failover.

If you're still on MPLS, you're leaving money on the table. Start with a pilot at one branch and measure the difference. The numbers speak for themselves.

For a deeper look at our network services, including SD-WAN design and deployment, visit our network solutions page. If you're ready to discuss your WAN, contact our team. We don't bite.

FAQ

What is SD-WAN and how does it differ from MPLS in India?

SD-WAN uses multiple internet connections (broadband, LTE) and software to intelligently route traffic, while MPLS relies on a private carrier network. SD-WAN is cheaper and more flexible, especially for cloud apps; MPLS provides guaranteed service quality but at a premium.

Is MPLS still relevant in 2026?

For industries with ultra-strict regulatory or reliability needs—like certain banking systems—MPLS might still be preferred. However, most retail, logistics, manufacturing, and IT companies can switch to SD-WAN or a hybrid without loss.

How much does SD-WAN cost for a 10-site company in India?

Hardware and setup run ₹4-7 lakh. Annual connectivity and licensing is ₹3-5 lakh, depending on bandwidth. Compare that with MPLS at ₹10-15 lakh per year.

Which SD-WAN vendor is best for a 50-user branch?

Fortinet FortiGate offers the best value, with integrated security. Cisco is excellent for enterprise scale, but you'll pay triple. Evaluate based on your existing ecosystem.

Can I use SD-WAN with my existing MPLS?

Yes. Many enterprises run SD-WAN alongside MPLS, using SD-WAN for internet-bound traffic and MPLS for critical legacy connections. This hybrid approach lets you migrate gradually.

What are the typical SD-WAN implementation pitfalls in India?

Underestimating ISP lead times, ignoring power backup, using single ISP, and not testing failover are common. Also, forget about GST and CERT-In compliance if relevant to your sector.