New
How are you controlling observability costs without losing visibility?
Sampling, tiered retention, OpenTelemetry pipelines, switching vendors? What cut the bill the most?
Evaluation guide
How to evaluate networking vendors
This guide is for network architects, infrastructure leads and IT managers refreshing campus, branch or data centre networks, or moving to SD-WAN and SASE. It assumes you are buying equipment with a long life and want to judge the years after installation as well as the purchase.
In short
Use this guide to compare networking vendors on what decides the outcome over the life of the equipment: interoperability and open APIs, operations at scale, security integration, how AI operations perform on your own network, hardware lifecycle, licensing and support. Then shortlist three to five companies on Techarda and run a pilot at a site that looks like the rest of your estate.
What’s changing in Networking
Before you compare anyone, it helps to know what has shifted in the market, because it changes which questions matter.
Networking and security are converging
SASE combines SD-WAN with security services delivered from the cloud. Vendors come to it from networking or from security, and their strengths usually show where they started.
Hardware now comes with subscriptions
Many vendors pair equipment with software subscriptions for features, management and support. If a subscription lapses, features may stop working, so licence terms decide much of the long-term cost.
AI operations feature in every pitch
Vendors offer assistants and analytics that find faults, explain issues and suggest fixes. The value depends on the telemetry they can see and how often they are right on your network.
AI clusters are changing data centre networks
Training clusters need high-bandwidth, low-loss fabrics between accelerators. That has reopened the choice of fabric technology and brought network teams into decisions that used to sit with compute.
What to judge vendors on
Those shifts shape the criteria below. Each one says why it matters and what to ask, so you can take it straight into a vendor call.
| Criterion | Why it matters | What to ask vendors |
|---|---|---|
| 1Interoperability and open standards | Networks outlive several generations of equipment. Proprietary protocols make every future purchase depend on the same vendor. | “Which features rely on proprietary protocols, how do you interoperate with our existing equipment, and which open APIs do you support for automation?” |
| 2Operations at scale | Configuring devices one by one does not scale, and many outages start with a change. How changes are made and checked matters. | “How do we push, validate and roll back configuration across all our sites, and can we drive it from our own automation tools?” |
| 3Security integration | Segmentation, access control and inspection now sit in the network. Gaps between network and security tools are where attackers move. | “How do you enforce segmentation and identity-based access, integrate with our security tools and send telemetry to our SIEM?” |
| 4AI operations on your network | Claims about fewer tickets and faster fixes are easy to make and hard to check. Your network is not the demo network. | “Can we run your analytics at our pilot site and record what it found, what it got wrong and what it missed?” |
| 5Hardware lifecycle and supply | Lead times, end-of-sale dates and support windows decide when you can deploy and how long the equipment stays useful. | “What are current lead times for the models we need, what are their end-of-sale and end-of-support dates, and how much notice do you give?” |
| 6Licensing and subscriptions | Subscriptions tied to hardware can make the second term dearer than the first, and a lapsed licence can switch features off. | “What stops working if a subscription lapses, can licences move between devices, and what price protection do you offer at renewal?” |
| 7SASE points of presence | Cloud-delivered security is only as good as the path to it. The distance to the nearest point of presence affects every user. | “Where are your points of presence relative to our sites and users, who operates them, and where is our traffic inspected and logged?” |
| 8Support and escalation | When a core switch or WAN link fails, the quality of support decides how long the outage lasts. | “Who answers a priority one call, how quickly do we reach an engineer who can change things, and how are replacement parts delivered to our sites?” |
Trade-offs to settle early
No vendor does well on every criterion, and some pull against each other. Decide where you stand on these before the demos start, or the demos will decide for you.
Single vendor or multi-vendor
One vendor across campus, branch and data centre means one management tool and one support line. Mixing vendors keeps pricing honest and avoids dependence, and needs stronger automation and skills.
Cloud-managed or locally managed
Cloud management is quick to deploy and easy to run across many sites. Local management keeps control and data on site and suits locations with strict security rules or poor connectivity.
Single-vendor SASE or networking plus a security specialist
One SASE supplier gives one policy and one console. Pairing a networking vendor with a security specialist may go deeper in each area, at the cost of integration work.
Vendor features or open automation
Vendor-specific features can save effort now. Open APIs and standards keep your automation portable and future purchases freer.
Refresh now or extend
Refreshing on schedule brings new features and full support. Extending the life of equipment saves capital and carries rising support and security risk as end-of-support dates approach.
Red flags
As the answers come back, watch for these. One on its own isn’t a deal breaker, but it deserves a follow-up question in writing.
- Features that stop working when a subscription lapses, without this being stated plainly.
- AI operations claims you cannot test on your own network.
- No open API, or automation limited to the vendor’s own tools.
- No clear end-of-sale and end-of-support dates for the models quoted.
- Lists of SASE points of presence that do not say which are owned and which are hosted by partners.
- No reference customer running the same models across a comparable number of sites.
Build your shortlist
Map the network you have and the one you need, then use Techarda to narrow the field to three to five companies.
- List the domains in scope (campus, branch, WAN, data centre, remote users) and the sites, users and applications each one serves.
- Keep companies that cover those domains in production today, and decide early whether you want one vendor or several.
- Compare like with like: SASE against SASE, campus switching against campus switching, data centre fabrics against each other.
- Read recent stories on Techarda for acquisitions, product retirements and licensing changes, and add questions about them.
- Run a pilot at one representative site, check the practitioner questions below, then compare side by side.
Companies to consider in Networking
Listed by recent activity on Techarda (what people are reading, following and discussing). The order says nothing about quality, market share or fit for your needs.
Latest Networking stories
Once you have names, recent news is where pricing changes, acquisitions and outages show up first. These are the five newest stories in this category.
What practitioners are asking
News tells you what vendors announced. These open questions show what teams are still trying to work out, with the least-answered first.
New
What is the one cloud architecture decision you would undo if you could?
Account structure, networking, region choice, managed-service lock-in: the lessons that cost the most are the most useful to others.
Techarda editors Editorial Answer this
New
How are you preparing the network for AI workloads?
East-west bandwidth, GPU cluster fabrics, data movement between sites: what has changed in your network plans?
Where evidence is thin
A shortlist is only as good as the evidence behind it, and ours is still growing category by category. Here is what’s missing in Networking right now.
20 of 20 companies have no published reviews
If you’ve run one of these in production, a short review helps the next team decide. Reviews are moderated before they appear.
3 questions with no answers yet
An answer from someone who has made the same decision is often more useful than any guide. Share what worked, what didn’t and what you’d check next time.
Answer a Networking questionFrequently asked questions
What should I ask Networking vendors about interoperability and open standards?
Networks outlive several generations of equipment. Proprietary protocols make every future purchase depend on the same vendor. Ask: Which features rely on proprietary protocols, how do you interoperate with our existing equipment, and which open APIs do you support for automation?
What should I ask Networking vendors about operations at scale?
Configuring devices one by one does not scale, and many outages start with a change. How changes are made and checked matters. Ask: How do we push, validate and roll back configuration across all our sites, and can we drive it from our own automation tools?
What should I ask Networking vendors about hardware lifecycle and supply?
Lead times, end-of-sale dates and support windows decide when you can deploy and how long the equipment stays useful. Ask: What are current lead times for the models we need, what are their end-of-sale and end-of-support dates, and how much notice do you give?
What should I ask Networking vendors about licensing and subscriptions?
Subscriptions tied to hardware can make the second term dearer than the first, and a lapsed licence can switch features off. Ask: What stops working if a subscription lapses, can licences move between devices, and what price protection do you offer at renewal?
New to some of the terms in this guide? The glossary explains Microsegmentation, SD-WAN and Secure access service edge (SASE).
This guide is written by Techarda editors to our editorial standards. No vendor paid to appear in it or saw it before publication. See our methodology, the trust dashboard or go back to the Networking hub.