Home/Products/OcNOS for OEMs
300+ OEMs Shipping  ·  Binary NOS  ·  Source Code CP  ·  ZebOS Evolution

OcNOS for OEMs

Building a carrier-grade NOS from scratch takes 5–10 years and hundreds of engineers. OcNOS gives you 26 years of production-hardened BGP, MPLS, EVPN, and 750+ features — shipping in months, not years.

Talk to OEM Team OcNOS Flex ↓ OcNOS CP ↓
Build from scratch vs. license OcNOS

Skip 5–10 years of NOS engineering

Building a carrier-grade routing stack is a decade-long commitment. OcNOS lets you ship production-ready BGP, MPLS, and EVPN in months — so your team focuses on differentiation, not protocol code.

Build from scratch
✗5–10 years to production-grade routing protocols
✗Hundreds of engineers for protocol stack + hardware abstraction
✗BGP/OSPF/IS-IS/MPLS interop testing alone takes years
✗Each new silicon generation requires fresh HAL work
✗Ongoing CVE patches, standards tracking, feature parity — forever
License OcNOS
✓Ship in months — 750+ features production-ready on day one
✓26 years of Tier-1 operator validation and interop testing included
✓Broadcom, Marvell, Intel silicon — HAL already done
✓IPI manages standards tracking, CVE patches, and feature updates
✓Your engineers focus on differentiation, not protocol code
Two licensing models

Ship faster. Build on 26 years of carrier-grade NOS.

FLEX

OcNOS Flex

Binary NOS for custom hardware

A complete, ready-to-install network operating system image. Deploy OcNOS on your own hardware platform without touching the source code. IP Infusion handles platform onboarding, BSP integration, and ongoing validation.

Full NOS delivered as installable image — ONIE or custom boot
Broadcom, Marvell, and Intel/Tofino merchant silicon support
Per-device licensing — annual or perpetual
IP Infusion manages BSP, HAL integration, and release updates
Custom CLI branding and management interface options
Contact OEM Sales →
CP

OcNOS CP

Control plane source code

Source-code access to the OcNOS control plane — routing protocols, management stack, and programmability APIs. Compile into your own platform software. Ideal for security appliances, NFV platforms, and OEMs requiring deep OS-level integration.

Source-code licensing — BGP, OSPF, IS-IS, MPLS, EVPN, VXLAN
Integrate into proprietary OS, hypervisor, or container runtime
Per-unit royalty model with source-code agreement
NETCONF/YANG, gNMI, REST API, Ansible integration
Used by security, wireless backhaul, and NFV appliance vendors
Contact OEM Sales →
0
OEMs shipping on OcNOS
0
Carrier-grade heritage
0
Validated HW platforms
0
Protocol features
OEM Deployments

Who ships on OcNOS

OcNOS Flex

Ceragon Networks

Ceragon integrates OcNOS Flex into their wireless backhaul platforms, delivering carrier-grade L2/L3 routing on purpose-built microwave transport hardware deployed at Tier 1 mobile operators worldwide.

OcNOS Flex

North Atlantic Industries

NAI embeds OcNOS Flex in rugged military-grade networking platforms for defense and aerospace applications — where carrier-grade protocol support meets MIL-SPEC environmental requirements.

OcNOS CP

Security & NFV Appliance Vendors

Leading security vendors — including firewall, ADC, and DDoS mitigation platforms — license OcNOS CP source code for BGP, OSPF, and policy routing integration into their proprietary appliance software.

Get Started

Skip 5–10 years of NOS development

Building routing protocols from scratch costs millions and takes years. OcNOS delivers production-hardened BGP, IS-IS, MPLS, EVPN, and 750+ features — validated across 600+ operators.

Talk to OEM Engineering View Hardware Compatibility →
Frequently Asked Questions

OEM NOS licensing, explained

What is the difference between OcNOS Flex and OcNOS CP?
OcNOS Flex is a complete binary NOS delivered as a ready-to-install image for custom or whitebox hardware. OcNOS CP is a source-code licensing of the OcNOS control plane (routing protocols, management interfaces) that OEMs compile into their own platform software. Flex is faster to deploy; CP gives deeper integration control.
How does OcNOS compare to building a NOS from scratch?
Building a carrier-grade NOS from scratch takes 5–10 years and hundreds of engineers. OcNOS provides 26 years of validated routing protocols (BGP, OSPF, IS-IS, MPLS, EVPN), hardware abstraction, and operator-proven production hardening — so OEMs ship in months, not years.
Is OcNOS a ZebOS alternative?
Yes. OcNOS is the commercial evolution of the ZebOS routing stack, with full carrier-grade hardening, merchant silicon support, and 26 years of production deployment. OEMs migrating from ZebOS or evaluating alternatives benefit from a familiar architecture with modern feature parity.
What hardware platforms does OcNOS Flex support?
OcNOS Flex runs on Broadcom (Memory, Memory+, Jericho2, Tomahawk, Trident), Marvell (Prestera, Teralynx), and Intel/Barefoot Tofino-based platforms. Our HAL (Hardware Abstraction Layer) supports 50+ validated platforms. Custom platform onboarding is available for OEM-specific hardware.
How do OEMs license OcNOS?
OcNOS Flex is licensed per-device with annual or perpetual options. OcNOS CP is licensed as a source-code agreement with per-unit royalties. Both include access to IP Infusion engineering support, platform validation, and release updates. Contact our OEM partnerships team for custom terms.
Resource

OcNOS CP Product Brief

Complete a short form and the PDF is delivered instantly by our resource centre.

Download PDF