How Spicer Group Modernized Branch Networking with VyOS

“With VyOS, I get the CLI I need and the Linux flexibility I want. That combination is rare, and once you’ve worked with it, it’s hard to go back to anything else.”
— Michael Doan, Network Administrator, Spicer Group

Customer Overview

Founded in 1944, Spicer Group is a US-based professional services firm providing engineering, land surveying, and community planning services across 26 states. With 380 employees across 16 office locations, the company relies on a distributed branch network to support day-to-day operations.

That network connects 13 sites to a central location over EPLAN circuits, making reliability and predictability core operational requirements.

Challenge

Spicer Group previously ran a Cisco-based branch networking stack, but three constraints became increasingly limiting as the branch footprint and operational expectations grew:

Licensing friction at scale: Site growth and capability expansion consistently triggered new license decisions and increased operational overhead.
Rigid operational model: Limited room for Linux-style scripting, native automation, or deep, transparent introspection.
Vendor dependence: Release cadence, roadmap, and operating constraints were defined externally, reducing long-term control over core infrastructure.

Why VyOS

VyOS wasn't selected through a formal bake-off. It was adopted because the engineer responsible for the network had already trusted it in production for years.

CLI-first, engineer-friendly operations: A structured CLI paired with Linux flexibility for scripting, automation, and troubleshooting.
Proven in production over multiple cycles: Michael’s experience spans from VyOS 1.1.7 to current releases, with consistent operational stability.
Operational ownership: The team gained control over how the network is built, observed, and evolved without vendor-gated constraints.
A platform that can evolve: Ongoing lab evaluation of VyOS 1.5 and VPP supports future throughput and next-generation dataplane needs.

Implementation

Spicer Group deployed VyOS on bare-metal x86 white-box hardware across 13 branch sites, using a consistent model across the footprint:

Branch routing across 13 sites over EPLAN circuits to a central hub
OSPF is the routing backbone for reliable dynamic path selection
Scaled without architectural rework, expanding from early deployments to a 13-site footprint without redesign
Low-touch operations after initial configuration, with attention required mainly for intentional changes
Active lab work on VyOS 1.5 + VPP to evaluate higher throughput and future branch requirements

Results

With VyOS in place, Spicer Group achieved measurable operational outcomes:

Scaled the branch network without redesign: Growth to 13 sites without changing the deployment model
Operational simplicity: Faster, more transparent day-to-day management with CLI-first workflows and Linux-native tooling
Stability across multiple release cycles: Long-term production confidence, validated through years of real-world use
Successful in-house migration from Cisco: Manageable transition executed by the internal team without unexpected blockers
Freedom to evolve: 1.5 + VPP testing and cloud expansion planning underway on the same platform

Operational and Cost Impact

VyOS reduced platform-driven friction and increased operational control:

Fewer vendor constraints are shaping daily operations
More predictable upgrades with a clear path from 1.4 to 1.5 focused on stability and performance
A partnership model through architecture reviews and senior engineering access, not just ticket handling

Looking Ahead

Spicer Group is planning the next phase of its deployment:

Upgrade to VyOS 1.5 with a straightforward 1.4-to-1.5 transition expected
Evaluate VPP dataplane acceleration to support higher throughput requirements
Extend into public cloud using VyOS availability across AWS, Azure, GCP, Oracle, and Equinix Network Edge, including marketplace private-offer options