Home/Products/OcNOS for OEMs
For OEMs · Flex + CP · Your Silicon

Make it your NOS.

Put a carrier-grade routing stack in your product without building one. License OcNOS as a complete binary NOS image, or as control-plane source code you compile into your own software. Both build on the ZebOS lineage: carrier-grade since 1999, with 300+ OEMs. OcNOS is in production with 900+ operators across 60+ countries.

Talk to the OEM team Compare Flex and CP Get the OcNOS CP brief

Ship a binary image, or license the source

Every OEM starts from a different point: some want a finished NOS on their hardware, others need routing built into their own operating system. OcNOS meets both, so you embed exactly as much as your product needs.

FLEX

OcNOS Flex

Binary NOS for your hardware

A complete, ready-to-install OcNOS image for your custom or open hardware. IP Infusion handles the platform port, board support, and hardware abstraction, so you ship a finished box without touching source code.

Full NOS delivered as an installable image: ONIE or custom boot
Ported and qualified by IP Infusion on the merchant silicon you build on
IP Infusion manages board support, hardware abstraction, and release updates
Custom CLI branding and management interface options
Licensed as a one-time porting fee, a per-box license, and support
Best for Hardware vendors shipping a finished, branded box.
Talk to the OEM team
CP

OcNOS CP

Control-plane source, formerly ZebOS

Source-code access to the OcNOS control plane: the routing protocols, the management layer, and programmability for network management and orchestration, as modular source code. Compile it into your own operating system, hypervisor, or appliance software for the deepest integration.

Source-code licensing: BGP, OSPF, IS-IS, MPLS, EVPN, VXLAN
Hardware and platform abstraction layers: silicon-agnostic, on any platform
Carries forward the ZebOS control plane, first shipped to telecom OEMs in 1999
Industry-standard CLI, standard MIBs, NETCONF and SNMP
Licensed upfront, perpetual or annual, plus a per-unit royalty and optional support
Best for Vendors embedding routing in their own OS or appliance, on any platform.
Talk to the OEM team

Two integration paths, one routing stack

Flex runs as a complete image on your hardware. CP compiles into your own software. Either way, your product ships with the same carrier-grade OcNOS routing.

Two ways to embed OcNOS in an OEM product: OcNOS Flex is a complete binary NOS image ported onto your hardware, and OcNOS CP is control-plane source code compiled into your own operating system or appliance software.
Two integration paths, one routing stack: OcNOS Flex ships as a binary NOS image on your hardware, and OcNOS CP compiles into your own software.

Not sure which path fits your product? Talk to an OEM engineer about scoping the port.

Carrier-grade protocols, shipping since 1999

OcNOS CP is the control-plane source code of OcNOS: carrier-grade, hardened protocols built as independent multi-tasking modules, tightly integrated for scale and performance.

The protocol set

Routing protocols, first hop security, traffic protection and service assurance tools. MPLS, SR, VXLAN and multicast transport, with VPWS, VPLS, L3VPN and EVPN services.

BGPIS-ISMPLSEVPNSR

Hardware and platform abstraction

Hardware and platform abstraction layers connect the protocol stack to your platform. OcNOS CP is silicon-agnostic, and for OcNOS Flex, IP Infusion ports and qualifies OcNOS on your hardware.

HW ABSTRACTIONPLATFORM ABSTRACTION

Data-model driven management

Industry-standard CLI and standard MIBs, NETCONF and SNMP, with a data-model driven layer for transaction-based configuration, device feature modelling and orchestration.

CLINETCONFSNMPMIBs
Where products built on OcNOS CP run
AccessAggregationTransportData centerFirewallsLoad balancingVPNSecuritySwitchingRouting

OcNOS CP is silicon-agnostic, and IP Infusion ports OcNOS Flex onto the merchant silicon you build on. See the qualified platforms in the OcNOS Hardware Compatibility List.

Skip the years it takes to build a NOS

Building a carrier-grade routing stack takes years and a large protocol team, and the work continues after the first release. Licensing OcNOS cuts development time from years to months.

Build a NOS from scratch
Years of protocol development before the first release
A large team for the protocol stack and hardware abstraction
Interoperability testing for every protocol you ship
Every new silicon generation needs fresh abstraction work
Standards tracking and security patching become a permanent cost
License OcNOS
Development time cut from years to months
A carrier-grade, hardened protocol stack, shipping since 1999
Hardware and platform abstraction layers connect the stack to your platform
IP Infusion maintains the protocol stack, with support on both models
Your engineers focus on differentiation, not protocol code

Embedding, not integrating open hardware. OcNOS for OEMs is about putting a NOS inside the product you build and sell. If you would rather buy complete OcNOS switches and routers, pre-integrated and shipped on one purchase order, OcNOS Systems is the path. See OcNOS Systems. Browse the protocol coverage in the OcNOS Feature Matrix.

The OcNOS CP control-plane brief

A short technical brief on licensing the OcNOS control plane as source code for virtual and physical networking products, from firewalls and VPN to switching and routing.

Product Brief

OcNOS-CP: Control-Plane Source Licensing

The OcNOS control plane as modular source code that you compile into your own operating system, hypervisor or appliance software.

Get the brief

Embedded in products operators already run

From cell-site routers to firewall and VPN appliances, OcNOS provides routing for vendors that need carrier-grade protocols without building their own protocol stack.

Ceragon Networks

Ceragon and IP Infusion partnered to deliver a radio-aware open cell-site router, embedding a customized OcNOS on Ceragon transport hardware for Tier-1 mobile operators.

Security and appliance vendors

Firewall, load-balancing, VPN and security vendors license OcNOS CP source code to add routing to their virtual and physical appliances without building a stack in-house.

Networking and edge OEMs

Networking and edge-hardware OEMs embed OcNOS to turn their platforms into carrier-grade routers, with custom branding and a management interface that matches their own product line.

Put OcNOS inside your next product

License a carrier-grade protocol stack instead of building one: BGP, IS-IS, MPLS and EVPN, in production with 900+ operators across 60+ countries. Tell us about your hardware and we will scope the port.

Talk to the OEM team View qualified hardware

OcNOS for OEMs: frequently asked questions

What is OcNOS for OEMs?
It lets hardware vendors and ODMs put a carrier-grade network operating system in their products without building one from scratch. IP Infusion offers two models: OcNOS Flex, a complete binary NOS image that runs on your hardware, and OcNOS CP, the OcNOS routing control plane licensed as source code that you compile into your own software. Both build on a control plane first shipped to telecom OEMs in 1999, and OcNOS is in production with 900+ operators across 60+ countries.
What is the difference between OcNOS Flex and OcNOS CP?
OcNOS Flex is a complete, ready-to-install NOS image for your custom or open hardware. IP Infusion handles the platform port, board support, and hardware abstraction, so you ship a finished box without touching source code. OcNOS CP licenses the control plane itself, including BGP, OSPF, IS-IS, MPLS, and EVPN, as source code that you compile into your own operating system or appliance. Flex is faster to ship; CP gives the deepest integration control.
Is OcNOS CP the successor to ZebOS?
Yes. OcNOS CP, formerly known as ZebOS, carries forward the ZebOS control plane, first shipped to telecom OEMs in 1999. OEMs already embedding ZebOS have a direct migration path to OcNOS CP. Contact the OEM team for the module mapping.
How do OEMs license OcNOS?
OcNOS Flex has a one-time engineering fee for porting and qualifying OcNOS on your hardware, plus a per-box license fee and support. OcNOS CP uses an upfront license fee, either perpetual or as an annual subscription, plus a per-unit royalty and optional support. Contact the OEM team for terms specific to your product and volume.
What hardware and silicon does OcNOS Flex support?
OcNOS Flex is a complete binary NOS that IP Infusion ports and qualifies on your hardware and the merchant silicon you build on. The platforms OcNOS is already qualified on are published in the OcNOS Hardware Compatibility List. For a control-plane-only path, OcNOS CP is silicon-agnostic: you compile it into your own software on any platform.
How long does it take to ship compared with building our own NOS?
Building a carrier-grade routing stack from scratch takes years and a large protocol engineering team, and the work continues with standards tracking and security maintenance. Licensing OcNOS cuts development time from years to months, so your engineers spend their time on what sets your product apart.

Related OcNOS resources

OcNOS overview The carrier-grade NOS behind every motion: service provider, data center, AI fabric, and OEM. OcNOS Systems Complete OcNOS switches and routers, pre-integrated and shipped by IP Infusion. Hardware Compatibility List Every qualified platform, by silicon family and port speed. Feature Matrix Features tracked per platform and per SKU across the OcNOS portfolio.