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 are backed by 26 years of production routing in 600+ operator networks, and by 300+ OEM products already shipping on OcNOS.

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

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 onto your merchant silicon, with 40+ platforms validated out of the box
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 routing control plane, including the routing protocols, management stack, and programmability APIs. 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
Integrate into a proprietary OS, hypervisor, or container runtime
The proven successor to ZebOS, embedded in vendor products since 1999
NETCONF and YANG, gNMI, REST API, and Ansible integration
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
How it embeds

Two integration paths, one routing stack

Flex installs as a complete image on your hardware. CP compiles into your own software. Either way, your product ships with the same field-proven 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 and we will scope the port.

What you embed

A field-proven stack, hardened over 26 years in production

OcNOS is not a reference implementation. It is the same software running in Tier-1 carrier and data-center networks, hardened over 26 years and maintained release after release.

Routing

The full protocol set

Production BGP, OSPF, IS-IS, MPLS, and EVPN, with segment routing and 700+ features across the portfolio. The interop testing that takes new stacks years is already done.

BGPIS-ISMPLSEVPNSRv6
Silicon

Hardware abstraction, done

A mature hardware abstraction layer, with 40+ platforms already validated, so a new box does not mean a new forwarding integration from zero.

QUMRANJERICHO2C+TRIDENTTOMAHAWK
Manage

Modern management built in

NETCONF and YANG, gNMI streaming telemetry, a REST API, and Ansible support ship with the stack, so your product speaks the automation languages operators already run.

NETCONFgNMIYANGREST
Validated silicon families
QumranQumran2Jericho2C+Trident 3Trident 4Tomahawk 2Tomahawk 3Tomahawk 4Tomahawk 5Custom port on request

The current validated platforms are published in the OcNOS Hardware Compatibility List. Beyond that set, IP Infusion ports OcNOS onto the merchant silicon you build on, and OcNOS CP, the control-plane source, is silicon-agnostic.

Build from scratch vs license OcNOS

Skip the decade it takes to build a NOS

A carrier-grade routing stack is a 5 to 10 year commitment for a large protocol team, and the work never really ends. Licensing OcNOS turns that into a port measured in months.

Build a NOS from scratch
5 to 10 years to production-grade routing protocols
A large team for the protocol stack and hardware abstraction
BGP, IS-IS, and MPLS interop testing alone takes years
Every new silicon generation needs fresh abstraction work
Standards tracking and CVE patching become a permanent cost
License OcNOS
Ship in months, with 700+ features production-ready on day one
26 years of operator validation and interop testing included
Hardware abstraction already done across 40+ validated platforms
IP Infusion maintains standards, CVE patches, and feature updates
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, see OcNOS Systems. To browse the full protocol coverage, see the OcNOS Feature Matrix.

OEM Resources

The OcNOS CP control-plane brief

A short technical brief on licensing the OcNOS control plane as source code for security, NFV, and embedded networking products.

Product Brief

OcNOS-CP: Control-Plane Source Licensing

License the OcNOS control plane as source code: BGP, OSPF, IS-IS, MPLS, EVPN, and the management stack, compiled into your own platform software for security, NFV, and embedded networking appliances.

Get the brief
Who ships on OcNOS

Embedded in products operators already run

From cell-site routers to security and NFV appliances, OcNOS is the routing inside products from vendors that need carrier-grade protocols without owning a protocol team.

Wireless transport

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 & NFV

Security and NFV appliance vendors

Firewall, application-delivery, and DDoS-mitigation vendors license OcNOS CP source code to add BGP, OSPF, and policy routing to their appliance software without building a stack in-house.

Embedded routing

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

Building routing protocols from scratch costs years and millions. OcNOS delivers production-hardened BGP, IS-IS, MPLS, EVPN, and 700+ features, validated across 600+ operators. Tell us about your hardware and we will scope the port.

Talk to the OEM team View supported hardware
FAQ

OcNOS for OEMs: frequently asked questions

What is OcNOS for OEMs?
It is the way hardware vendors and ODMs put a carrier-grade network operating system inside their own product instead of 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 are built on 26 years of production routing in 600+ operator networks.
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. ZebOS, first shipped to telecom OEMs in 1999, was rebranded as OcNOS CP. It is the same source-code control plane, now carried forward with modern protocol support, merchant-silicon hardware abstraction, and ongoing maintenance. OEMs already embedding ZebOS have a direct migration path to OcNOS CP.
How do OEMs license OcNOS?
OcNOS Flex is licensed as a one-time engineering fee to port and validate 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 onto the merchant silicon you build on. More than 40 platforms are validated out of the box, Broadcom DNX and XGS among them, and the current set is 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 5 to 10 years and a large protocol engineering team, and then never stops needing standards tracking and CVE maintenance. Licensing OcNOS lets an OEM ship in months with 700+ features production-ready on day one, while IP Infusion maintains the protocols, silicon abstraction, and security patches.
Keep exploring

Related OcNOS resources

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