SONiC Capabilities: Empowering Networks with Open-Source Solutions

Download PDF

How to Build a NOS TCO Model for Access and Campus Switches

November 18, 2026

Key takeaways:

  • A NOS TCO model for access switches needs eight cost lines: hardware, license, support, engineering time, feature work, training, migration, and power.
  • In the worked example below, the license is less than a fifth of a proprietary option’s five-year cost, while hardware is close to half of it.
  • Enter an open NOS quote as a break-even: the highest yearly price per switch at which moving still beats renewing. That ceiling roughly halves when a 200-switch fleet shrinks to 40.
  • When your switches stay in service and no refresh is due, the break-even in that example drops below zero, so renewal wins at any NOS price on those inputs.

Your access refresh is due, the quote for 200 PoE switches came in above last year’s budget, and the proprietary NOS renewal sits on the same purchase request. Dell’Oro Group reported in September 2026 that campus switch average selling prices grew 19 percent in 2Q 2026, as component shortages pushed up list prices on nearly all campus switches.

A higher quote is the moment to compare NOS options on something firmer than the license line. A NOS TCO model prices hardware, software, people, and one-time project work over a full refresh cycle, then shows which option wins for your fleet and which input would flip the result.

This guide builds that model line by line, runs it on three fleet sizes, and shows where staying on a proprietary NOS is the better buy. It also shows how to enter SONiC Lite, built for access, campus, and edge switches.

What a NOS TCO Model Has to Answer for an Access Layer

Network operating system total cost of ownership is the full cost of running a switch fleet over a fixed period, including the labor and project work that never appear on a quote. Your model should answer three questions: which option costs less over one refresh cycle, how high the NOS quote can go before the result flips, and which inputs the result depends on most.

An access layer has its own math. A per-switch fee repeats across hundreds of boxes that each carry modest traffic, every closet needs the same few features, and a small team usually owns all of it. A savings percentage from a data center fabric study says little about a wiring closet, so build your access switch TCO from your own fleet.

Compare at least three options, because each one fails in a different way. Option A renews the proprietary NOS on a refreshed branded switch. Option B moves to a supported open NOS on white-box switches under a quoted contract. Option C runs Community SONiC with your own engineers and no commercial support. Keep all three in the sheet, because a rejected option with real numbers beside it answers the question your CFO will ask.

The Eight Cost Lines in a Campus Switch TCO Model

PLVision’s TCO white paper splits NOS ownership into hardware, annual license, NOS support, in-house engineering, new feature development, and team training. An access-layer model keeps those lines and adds two more: migration, because moving a NOS is a project with its own budget, and power, because finance will ask about it.

The table lists each line and where its number should come from, so nobody fills a cell from memory.

Cost line What it covers Where the number comes from How often it recurs
Hardware Switches, spares, and optics Dated supplier quotes Once per cycle
NOS license Subscription or perpetual right to run the NOS Renewal or supplier quote Yearly
Support NOS support, updates, and hardware replacement Contract or quote Yearly
Engineering time Release checks, upgrades, patching, automation, and incidents Change tickets and on-call logs Yearly
Feature work Development for a feature the NOS lacks Scoping estimate Per feature
Training Courses and ramp-up hours Course price and team size Once, plus new hires
Migration Pilot, template rewrite, tooling, and rollout Project plan Once
Power Electricity for the switch itself Datasheet and your tariff Yearly

Add one more column to your own sheet: the source of each input, marked as quote, ticket data, or planning estimate, so a reviewer can see which cells are facts and which are your judgment.

Run those lines through the worked example later in this guide, and the license turns out to be a small share of the total.

Stacked bar of a proprietary NOS renewal for 200 switches over five years: hardware $945,000, support $400,000, engineering and power $336,000, and the license $350,000, or 17% of the total.

Outage risk stays out of the table on purpose. Its cost depends on your sites and your incident history, so run it as a stress test once the base model works.

Considering a switch to open-source networking?

Explore the reasons to choose an open-source NOS like SONiC, along with a breakdown of the Total Cost of Ownership (TCO) for both proprietary and open-source solutions.

Define the Fleet, the Horizon, and the Feature Set First

A model breaks when its inputs describe an imaginary fleet, so settle the scope before you type in a single price:

  1. Export every switch and group them by class: 48-port PoE access, 24-port access, aggregation, and out-of-band management.
  2. Record how many switches of each class sit at each site, because spares and travel depend on the site count.
  3. Mark which switches reach end of support inside the horizon, since those need new hardware under any option.
  4. List what each class uses today: PoE budget, 802.1X, MACsec, VLAN count, and uplink speed.
  5. Strike any feature nobody uses, so you don’t pay to replicate it.
  6. Write the end date of your current NOS contract beside each class.

Set the horizon to one refresh cycle and use the same horizon for every option. Five years is a sensible default for an access layer, because it covers the hardware life and at least one renewal.

Feature lists drive this step more than port counts do. A reference campus design needs PoE for access points and cameras, DHCP relay across subnets, and 802.1X for desktops, and each of those has to work on the exact release and switch you’d buy. Run the model once per class and add up the results.

How to Price Hardware, Spares, and Refresh Timing

Hardware is the largest line in the worked example below, and it’s the line most likely to be out of date. Dell’Oro expects memory shortages to shape the campus switch market well into 2027. TrendForce’s September 2026 outlook puts 4Q26 conventional DRAM contract prices up 10–15% and NAND Flash up 15–20% quarter over quarter.

Date every quote, record its validity period, and refresh it before the model goes to review. A quote from before the latest price rises understates this line, a pressure PLVision traced through switch bills of materials in its look at memory costs.

Compare Equivalent Configurations

Quote each option on the same port count, PoE budget, uplink speed, and warranty term. The Edgecore ECS4650-54P is a useful reference point for a white-box access switch: 48 1GbE PoE ports, six SFP28 uplinks, up to 90 W per port, and a 740 W PoE budget. A US reseller, Provantage, showed it at a $2,550 manufacturer list price on November 2, 2026, which gives you a dated sanity check on any quote.

Transforming OpenLAN Switching with SONiC Lite & Edgecore ECS4650-54P

Ask every supplier for the volume price on your whole fleet. The gap between branded and white-box hardware depends on your order size and on the discount you already hold, so a list price only tells you where to start.

Size Spares and Enter Reused Switches at Zero

An advance-replacement contract lets you hold fewer spares, and without one you keep more stock on hand, so the example below carries a smaller spare pool on the proprietary option. A long chain of branches pushes both figures up.

Switches that stay in service cost nothing in this line, and the last row of the stress test below shows how far that moves the result. Check every installed model against the hardware list of each NOS you’re considering, because a branded switch that can’t run another NOS has to be replaced under Options B and C.

How to Price the NOS License, Support, and Renewal Terms

A NOS quote has more moving parts than a price per switch, and the gaps between quotes usually sit in the terms. Ask every supplier the same questions and record the answers beside the number:

  • Is the license priced per switch, per port, or per feature tier?
  • Do PoE, 802.1X, and MACsec sit in the base tier?
  • Does the term start at shipment or at activation?
  • What stops working if a subscription lapses?
  • Is there a cap on the uplift at renewal?
  • Does support cover software updates, hardware replacement, or both?
  • Which response time does the contract commit to?

Enter license and support as separate cells, and apply any renewal uplift to the years it covers.

Open options need the same discipline. Community SONiC has no license fee, so its cost moves into engineering time. A supported distribution has a quote, and PLVision publishes no list prices, so a SONiC Lite cell comes from a quote for your fleet.

A feature gap is a cost too, because someone pays to close it or your users live without it. That’s why a functional comparison belongs beside the quote when you review the numbers.

How to Put a Number on Engineering Time

This line decides most close calls, and it’s the one most models guess. Start with a loaded hourly rate. The US Bureau of Labor Statistics puts the median annual wage at $99,130 for network and computer systems administrators and $134,050 for computer network architects, as of May 2025.

Wages made up 68.5% of compensation for full-time private-industry workers in June 2026, per BLS employer cost data. Divide by that share to get the full cost of each role, then blend them. The example below assumes 1,800 productive hours a year and two administrators for each architect, both planning figures:

Administrator:  $99,130 / 0.685 = $144,700 a year
 Architect:     $134,050 / 0.685 = $195,700 a year
 Blended rate:  (2 × $144,700 + $195,700) / 3 / 1,800 = about $90 an hour

Outside the US, use your own payroll numbers.

Measure Current Hours From Your Tickets

Pull a full year of change tickets and incident tickets for the access layer and sort them by activity. If your team doesn’t log time, sample ten tickets per activity and ask the engineers who closed them. A rough measurement of your real work beats a precise estimate of somebody else’s.

Estimate the Open NOS Hours by Activity

The table shows planning inputs for a 200-switch fleet, in hours per year. None of them comes from a study, so replace each one with your own figure.

Activity (planning hours per year) A: Proprietary NOS B: Supported open NOS C: Self-run Community SONiC
Release review and lab qualification 60 160 600
Upgrade rollout 100 100 200
Security advisory triage and patching 60 100 400
Automation and template upkeep 120 200 300
Incidents and escalation 200 240 600
Monitoring and tooling upkeep 60 100 300
Total hours per year 600 900 2,400

Option B carries more hours than Option A here because your tooling and habits are newer, and those hours should fall as the team settles in. Option C carries the most because your team owns the image build, the release choice, the backports, and the root cause on every incident.

PLVision’s lifecycle management guide breaks that work into team roles, testbeds, CI/CD, and regression runs, which makes it a useful checklist for this column. A team that already runs SONiC in the data center has much of that pipeline paid for, so its hours land well below these.

Budget Migration and Training as a One-Time Project

Migration belongs in its own line, because spreading it across yearly engineering hours hides the cash you need in year one. Plan the lab pilot, the rewrite of automation templates, the monitoring changes, and the rollout as separate tasks, then add training on top.

PLVision ran this move on its own office network, a mix of switches from several vendors and eras. The team started at the access layer and spent real effort on hardware compatibility checks and on the learning curve of a new environment. The post reports cost reductions without a figure, so use it as a checklist of the work and take your numbers from your own plan.

Count training by person, including time away from project work. Option C also calls for build and debugging skills, so its budget per person runs higher.

Power Belongs in the Model, but It Rarely Decides It

Run the number once so nobody has to argue about it. Edgecore’s datasheet lists a 52 W maximum for the non-PoE ECS4650-54T and 835 W for the ECS4650-54P, whose PoE budget accounts for most of that. The US Energy Information Administration puts the commercial average at 14.47 cents per kWh for August 2026, and Eurostat puts the EU non-household average at €0.18 per kWh for the first half of 2026.

Switch electronics:  52 W × 8,760 hours / 1,000 = 456 kWh a year
 US cost:             456 kWh × $0.1447 = $66 a year
 EU cost:             456 kWh × €0.18   = €82 a year
 Full PoE budget:     740 W × 8,760 hours / 1,000 = 6,482 kWh, or $938 a year

The PoE figure looks like the bigger number, but that power goes to your access points, cameras, and phones, and they draw the same watts under any NOS. Leave it out of the comparison unless the hardware options differ in power supply efficiency.

The switch’s own draw is the part an option can change, and a datasheet maximum overstates it. Add a cooling uplift if your closets are mechanically cooled, then move on.

Worked Example: A 200-Switch Refresh Over Five Years

This example uses one class of 48-port PoE access switches with a refresh already due. The labor rate comes from the BLS figures above. The power cost uses the 52 W maximum of the ECS4650-54T at the EIA rate for every option, because the gap between switch classes is too small to matter. Every other input, in dollars or in hours, is an illustrative planning figure, so replace it with your quotes and ticket data.

Illustrative input A: Proprietary NOS B: Supported open NOS C: Self-run Community SONiC
Switch price $4,500 $2,500 $3,200
Spares 5% 10% 10%
NOS license, per switch per year $350 N $0
Support, per switch per year $400 Included in N $0
Engineering hours per year 600 900 2,400
Feature work hours 0 0 1,000
Migration hours 0 1,000 1,400
Training $0 $18,000 $30,000

N is the yearly price per switch in Option B’s quote, and it includes support. The white-box price sits 44% below the branded one, inside the 30–50% lower hardware costs PLVision cites on its SONiC Lite page, and it’s still an input for you to replace. Option C uses a higher-spec switch, for reasons covered further down.

Cost line (illustrative) A: Proprietary NOS B: Supported open NOS C: Self-run Community SONiC
Hardware and spares $945,000 $550,000 $704,000
NOS license $350,000 N × 1,000 $0
Support $400,000 Included in N $0
Engineering time $270,000 $405,000 $1,080,000
Feature work $0 $0 $90,000
Training $0 $18,000 $30,000
Migration $0 $90,000 $126,000
Power $66,000 $66,000 $66,000
Five-year total $2,031,000 $1,129,000 + (N × 1,000) $2,096,000
Per switch per year $2,031 $1,129 + N $2,096

The license is less than a fifth of Option A’s total, while hardware is close to half. A comparison built on the license alone reads a small part of the bill.

Read the Result as a Break-Even

Find the value of N at which Options A and B cost the same:

Break-even N = (Option A total - Option B total before N) / (switches × years)
              = ($2,031,000 - $1,129,000) / (200 × 5)
              = $902 a year per switch
 
Check:  $750  license and support you stop paying
       + $395  hardware gap, per switch per year
       - $243  added labor, migration, and training, per switch per year
       = $902

That figure is a ceiling for your negotiation, and it says nothing about what any product costs. A quote below it means Option B wins on these inputs, and a quote above it means Option A wins.

Read the ceiling the other way round: the open option can carry a yearly quote about a fifth above the license and support it replaces and still come out ahead, because the hardware gap pays for the difference.

Reconcile the Output With Your Invoices

Before you trust anything else, compare Option A’s per-switch figure with what you actually paid over the last cycle, because your invoices are the one check nobody can dispute. If your license and support totals sit far from the model, fix the inputs first, since the same assumptions feed the other columns.

Stress-Test the Inputs That Move the Result

A single total invites an argument about the inputs, and a range ends it. Change one input at a time, and rescale the labor lines for fleet size, because they don’t move in step with the switch count. These are planning figures too:

Planning input 40 switches, one site 200 switches 800 switches, several sites
Option A hours per year 240 600 1,800
Option B hours per year 420 900 2,600
Option C hours per year 2,000 2,400 4,000
Option B migration hours 500 1,000 2,400
Option C migration hours 800 1,400 3,000
Option B training $9,000 $18,000 $36,000
Option C training $15,000 $30,000 $48,000

Each scenario below goes through the same formula, and the last column is the break-even against Option A.

Scenario (illustrative) Option A Option B before N Option C Break-even N
Base: 200 switches, five years $2,031,000 $1,129,000 $2,096,000 $902
40 switches $460,200 $366,200 $1,231,000 $470
800 switches $7,854,000 $3,886,000 $5,288,000 $992
All hardware quotes rise 19% $2,210,550 $1,233,500 $2,229,760 $977
White-box quote rises to $3,500 $2,031,000 $1,349,000 $2,096,000 $682
Option B hours rise 50% $2,031,000 $1,331,500 $2,096,000 $700
Seven-year horizon $2,465,400 $1,317,400 $2,554,400 $820
Loaded rate rises to $130 an hour $2,151,000 $1,349,000 $2,672,000 $802
No refresh due, current switches stay $1,086,000 $1,129,000 $2,096,000 Below zero

Fleet size and refresh timing move the result most. Smaller fleets lower the ceiling because labor and migration shrink more slowly than the switch count does, and rising hardware prices actually raise it, because the dollar gap between the two switches grows.

The last row is the one to show your finance team. When your switches have years of supported life left, Option A buys no hardware while Option B still buys a full fleet, so on these inputs no NOS price closes the gap. That margin is thin in this example, and a steeper renewal fee could reverse it, so run your own numbers and let the refresh date decide the timing of any move.

Set side by side, the scenarios show how much of the ceiling depends on fleet size and timing.

Bar chart ranking the break-even NOS price in nine scenarios of a NOS TCO model, from $992 for 800 switches down to $470 for 40 switches and below zero when no refresh is due.

To price outage risk, add one more scenario: take the cost of an hour of downtime at your busiest site, multiply it by the outage you’d expect from one failed upgrade, and see whether it moves the break-even past your quote.

When the Model Says Stay on a Proprietary NOS

A model that can only return one answer is a sales tool, so check whether yours has a real way to say stay. Renewal is the right call in several common cases:

  • Your switches have supported life left and no refresh falls inside the horizon.
  • Your fleet is small enough that migration hours outweigh the per-switch difference.
  • A multi-year subscription is already paid and has no exit.
  • Your team has no Linux or automation experience and no budget to build it.
  • A feature you rely on isn’t available on the open NOS for your switch model.
  • Wired and wireless share one license, and splitting them raises the wireless price.

Team readiness deserves an honest look. PLVision’s own ten reasons to hold off on SONiC start with in-house expertise, DevOps habits, and quality assurance infrastructure, and each of those shows up in your engineering hours. Renewing after this analysis is a good result, because you now hold a documented break-even to negotiate with.

What SONiC Total Cost of Ownership Looks Like With No License Fee

The obvious question is why you shouldn’t run the community code and keep the fee. In the 200-switch example, Option C lands slightly above Option A: the license saving is real, and the pipeline work absorbs it.

Hardware adds to that. SONiC was designed for data centers, with the power and resources that implies, and Community SONiC can demand too many resources for access and edge switches, which is why the example prices a higher-spec box. SONiC’s containerized design brings real benefits for updates and fault isolation, and it also needs CPU and memory on each switch.

Per switch, the same pipeline looks very different at each fleet size.

Paired bars comparing yearly cost per switch for a proprietary renewal and self-run Community SONiC at 40, 200, and 800 switches, with self-run falling from $6,155 to $1,322.

Scale changes the result, because that pipeline is mostly a fixed cost. On an 800-switch fleet, Option C lands well below Option A, and the same formula against Option C gives Option B a much lower ceiling. A team with deep SONiC skills and a large fleet can make self-running pay, so give this column a fair hearing.

How to Enter SONiC Lite in the Model

SONiC Lite belongs in the Option B column. PLVision’s product brief scopes it to “cost-effective management and access platforms” in data center, edge, and campus deployments. The brief lists about 3 GB of storage, 2 GB of RAM, and 2 ARM cores, which is what lets it sit on the lower-priced switch class in your hardware line.

Fill the rest of the column from what ships with it. The brief’s feature set includes L2, L3, PoE++, and 802.1X, so check those against your list from the scoping step. The Edgecore ECS4650-54P ships with SONiC Lite pre-installed, which shortens the imaging work in your rollout hours. SONiC Lite is in production at OEM customers across data center, edge, and campus networks.

N comes from a PLVision quote for your fleet, which you then hold against your break-even. The hours in your Option B column are the softest inputs in the sheet, so measure them: run a lab pilot on a spare switch, time the upgrade and template work, and replace the planning figures with what you recorded.

SONiC Lite Free Demo

Implement SONiC on cost-effective platforms with SONiC Lite

A pilot also tests your training line, because you’ll see how quickly your engineers get comfortable with the CLI and the automation interfaces.

Take a Break-Even to the Renewal Meeting

Start the sheet at least two quarters before your contract ends, because hardware quotes, a lab pilot, and a finance review all take longer than a renewal window allows.

Walk into the renewal with one number. A break-even price per switch gives procurement a concrete target for the open option and a concrete alternative for the proprietary one. In most of this guide’s refresh scenarios, that number leaves room for an open NOS priced at or above today’s license and support.

Ready to explore how SONiC can enhance your business?

Book a call with our experts to discuss your use case and unlock the full potential of open, disaggregated networking.
Message:
Your message has been sent, thank you! We will contact you as soon as possible.
Filip Koscuk

Frequently Asked Questions

What is a NOS TCO model?

A NOS TCO model is a spreadsheet that works out network operating system total cost of ownership for each option you’re weighing, over one refresh cycle. It covers hardware, license, support, engineering time, feature work, training, migration, and power, so the result reflects what you’d actually spend. The license alone can be a small share of that total.

What should a campus switch TCO include?

Include switches and spares, the NOS license, support, your engineers’ time on upgrades and incidents, any feature development, training, the migration project, and the electricity for the switch itself. Leave PoE power out of the comparison when the same endpoints draw it under every option. Treat outage risk as a stress test built from your own incident history.

How long should the horizon be for an access switch TCO model?

Use one refresh cycle, with five years as a sensible default, and apply it to every option. A shorter horizon favors whichever option has the lowest upfront cost, and a longer one assumes the hardware stays supported. Keep the same horizon across the sheet, because the break-even moves when the horizon does.

Is SONiC free once you count total cost of ownership?

Community SONiC has no license fee, but SONiC total cost of ownership still includes building images, qualifying releases, backporting fixes, and working through incidents. In this guide’s 200-switch example, that work outweighs the license and support savings, and the total lands slightly above renewal. On a much larger fleet the balance reverses, because most of that pipeline is a fixed cost.

How do I compare a NOS quote with my proprietary renewal?

Calculate your break-even first: subtract the open option’s total before NOS costs from the proprietary total, then divide by switches multiplied by years. Compare each quote with that yearly figure per switch, and check that both quotes cover the same support terms and features. A quote below the break-even wins on your inputs.