PEPLINK UNIVERSITY  •  A WEST NETWORKS TRAINING RESOURCE (352) 316-7701  ·  SHOP PEPLINK →

West Networks White Paper

The New Enterprise

Why the modern business network needs less hardware, more resilience, and a different definition of “enterprise-grade.”


A note before we begin: what this paper is not.

This paper is not a dismissal of carrier-grade or data-center networking. Some organizations genuinely need the full depth of traditional enterprise infrastructure, and they need every bit of it. A company that runs its own theme parks, studios, and resorts does not simply operate a large network; it functions as its own internet service provider, a carrier serving every one of those properties and business units. A Fortune 50 manufacturer running private global infrastructure, a hyperscaler operating a data-center fabric, a hospital system with massive on-site real-time compute, these are real, demanding, carrier-grade and data-center-grade networks. They require the capacity, the feature depth, and the engineering that the traditional enterprise vendors do so well. We are not arguing against any of that.

We are arguing that the word “enterprise” got stretched to cover two completely different things. One is that genuine carrier-and-data-center tier, perhaps five percent of businesses. The other is what the remaining ninety-five percent actually mean when they ask for “enterprise”: they want the reliability and the scalability that the label promises, not a checklist of features they will never use. This paper is about that ninety-five percent. It honors the five percent rather than pretending they do not exist, and it argues that the other ninety-five percent have quietly entered a new era, one their network architecture has not yet caught up to.


The full white paper, in ten short sections. Read straight through, or jump to any part.

Executive Summary

For three decades, "enterprise-grade" meant feature depth. The biggest routing tables, the deepest packet inspection, the most line cards in the core switch. That definition made sense when…

Read →

Part One: What "Enterprise" Used to Mean

The traditional enterprise network was built around a central assumption: most of what mattered happened inside one building, or a small number of large buildings.

Read →

Part Two: What Broke the Old Model

Two forces dismantled the assumptions underneath the traditional enterprise. Both are now well documented.

Read →

Part Three: The Four Pillars of the New Enterprise

If feature depth at the core is no longer the differentiator, what is? Four requirements define the New Enterprise network. None of them is about how many features the hardware has. All of…

Read →

Part Four: Reliability Is the Real Enterprise Line

Here is the cleanest test of whether a network is truly enterprise-grade, and it has nothing to do with feature count.

Read →

Part Five: What You Actually Need Now

If the on-premise Layer 3 core is overkill for most sites, what replaces it? Not nothing, the requirements are real, they just moved. Here is what the New Enterprise edge actually requires.

Read →

Part Six: SD-WAN as the New Core

The technology that delivers these behaviors is SD-WAN, software-defined wide-area networking. It is worth being precise about what that means, because the term gets used loosely.

Read →

Part Seven: The Economic Case

For the financial buyer, the New Enterprise is not primarily a technology story. It is a story about getting more resilience for less money, and reducing the cost of the thing that actually…

Read →

Part Eight: The Honest Boundary

A credible argument names its own limits. The New Enterprise model does not fit everything, and pretending it did would undermine everywhere it does fit.

Read →

Conclusion: A Different Definition

The enterprise did not get smaller. It got more distributed, and in getting more distributed it changed what "enterprise-grade" should mean.

Read →

Take it with you: The New Enterprise Checklist → Ten questions to test your own network.

Watch: the New Enterprise in five lessons

Five short video lessons on why rollouts stall, what downtime really costs, and how the bonded model fixes both.

Lesson 1: Rollout Shouldn't Take Months
Lesson 2: 5G Coverage Isn't the Problem
Lesson 3: Downtime Is a Design Flaw
Lesson 4: You're Overpaying for Complexity
Lesson 5: Your Network Should Be Flexible

Watch: related training videos