Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

ONOS

onosproject.org

  • Free plan
  • macOS
  • Linux
  • Web
  • API
  • Self-hosted
7.8 Club score Visit onosproject.org

What ONOS is

ONOS is an open-source software-defined networking platform that provides a control plane for managing network components and running modules that deliver communication services. Its µONOS architecture covers device configuration, monitoring and maintenance, forwarding-plane programming, topology validation, and collection of fine-grained performance metrics. A symmetric cluster of identical instances distributes work across servers and is designed to handle instance failures; the architecture is described as highly available and dynamically scalable. It supports interfaces and standards including P4/P4Runtime, gNMI/OpenConfig, and gNOI, with gRPC connecting modular microservices. OpenFlow is identified as the primary southbound protocol, alongside OVSDB, NETCONF, and SNMP for device configuration. The microservices are designed for Kubernetes deployment on cloud and data center infrastructure, with Docker images and Helm charts listed as deployment tools. A cloud-native web GUI uses Angular and gRPC Web to access backend modules. ONOS targets service-provider networks and can also be used for data-center or campus networks. It is free under the Apache License 2.0.

Who it suits

ONOS is aimed at teams controlling service-provider networks, with data-center and campus networks also identified as possible uses. Its Kubernetes-oriented microservices and network interfaces suit deployments built around those technologies.

Good to know, and what to watch

  • Distributed cluster design handles instance failures
  • Supports P4/P4Runtime, gNMI/OpenConfig, and gNOI
  • OpenFlow and other southbound configuration protocols
  • Free and distributed under Apache License 2.0
  • Production deployments are directed to release packages or Docker images
  • The latest listed LTS release is dated July 16, 2021

ONOS

Free

Open source

Getting started

  1. Open the ONOS website
  2. Choose a production release tar.gz package or Docker image
  3. Deploy the microservices on Kubernetes
  4. Use Helm charts or Docker images as deployment tools
  5. Connect network devices through supported southbound protocols

The Club's review

ONOS is an open-source software-defined networking platform for teams building and operating programmable networks. It is strongest for service-provider environments, with data-center and campus networks also in scope. Its distributed control architecture is compelling when availability and protocol flexibility matter; Kubernetes-based deployment makes it a specialist choice.

Overview

ONOS provides the control plane between network applications and the devices they manage. Its northbound abstractions let applications work with the network, while southbound abstractions support device control across protocols. That makes ONOS a foundation for network services, not a turnkey manager for routine small-network administration.

Identical instances form a symmetric cluster that distributes work and is designed to handle instance failures. The µONOS architecture describes high availability and dynamic scaling, useful properties for critical networks where a single controller is a weak point. The trade-off is operational commitment: µONOS microservices are designed for cloud and data-center infrastructure using Kubernetes, with Docker images and Helm charts among the deployment tools.

Key features

  • Network operations: µONOS supports device configuration, monitoring and maintenance, forwarding-plane programming, topology validation, and fine-grained performance metrics. That breadth helps teams combine control and visibility, but assumes they can work with a programmable-network platform.
  • Standards and protocols: P4/P4Runtime, gNMI/OpenConfig, and gNOI feature among its interfaces, with gRPC connecting modular microservices. OpenFlow is the primary southbound protocol for programming switch flow tables; OVSDB, NETCONF, and SNMP are also named for southbound configuration. This range suits heterogeneous network environments, though protocol support alone does not remove the work of integrating and operating the system.
  • External routing: The SDN-IP application lets an ONOS-controlled network exchange traffic with adjacent external networks using BGP, extending its role beyond isolated device control.
  • Web interface and access controls: The cloud-native ONOS GUI uses Angular and gRPC Web to access backend modules. Security Mode is intended to restrict application access to northbound APIs, a useful control when multiple applications interact with the platform.

Pricing

ONOS is free and open source: the ONOS plan costs nothing under the Apache License 2.0. There is no paid tier or seat-based price in this plan. Production deployments can use the release tar.gz package or Docker image; development can use the source repository.

The cost advantage comes with an infrastructure and operational trade-off rather than a cheaper feature tier: teams need to deploy and maintain the platform, including its Kubernetes-oriented µONOS services. The downloads page identifies X-Wing 2.7.0, dated July 16, 2021, as an LTS release.

Platforms

ONOS is listed for API, Linux, macOS, self-hosted, and web use. Its deployment model centers on Kubernetes for µONOS microservices, with Docker images and Helm charts as tools. The project also identifies P4Runtime, gNMI/OpenConfig, gNOI, and OpenFlow as supported platforms or interfaces.

Who it's for

ONOS is aimed first at teams controlling service-provider networks, and its architecture also identifies data-center and campus networks as possible uses. It makes sense for network engineers and platform teams building services around programmable devices, especially when distributed operation and multiple control interfaces are priorities. It is a poor match for buyers seeking a simple, ready-to-use network-management application or unwilling to operate Kubernetes-based infrastructure.

The project is community-backed; users can turn to its FAQ, mailing list, or Slack team for questions. That offers community channels, not a substitute for an organization’s own deployment and support plan.

Pros and cons

  • Pros: Free, Apache 2.0-licensed software avoids per-seat pricing and permits use of its published source code.
  • Pros: A symmetric, distributed architecture is designed to keep work running through instance failures and to scale dynamically.
  • Pros: A broad set of control and configuration interfaces, plus BGP integration, supports varied programmable-network use cases.
  • Cons: Kubernetes-oriented microservices make deployment and ongoing operations more involved than a conventional network-management app.
  • Cons: Its focus on SDN control and service-provider networks makes it unnecessarily specialized for straightforward network administration.

Alternatives

For other options, browse Software-Defined Networking Software and Network Automation Software.

  • .NET is a free, open-source option across Windows, Mac, Linux, iOS, and Android, with a free plan capped at 1,000 nodes; choose it if that platform and node limit fit your needs.
  • TP-Link Omada Cloud-Based Controller offers a lifetime-free plan with unlimited devices and sites and core management features; consider it for compatible Omada access points and managed switches.
  • Cilium is a free, open-source Linux and self-hosted option requiring Linux kernel 5.10 or equivalent and AMD64 or AArch64; choose it when those requirements and platform fit.
  • Kube-OVN is a free, Apache-2.0 Kubernetes networking project; it is an alternative for teams seeking that focus.
  • VMware Workstation Pro is free without a subscription or license key for 64-bit Intel or AMD Windows or Linux hosts; choose it when desktop-host virtualization is the need.
  • Antrea is free under Apache 2.0 and requires a Kubernetes cluster and Open vSwitch kernel module on every Kubernetes node; consider it if those prerequisites suit your environment.
  • Open Virtual Network is a free, open-source Apache 2-licensed option for Linux and self-hosted use.
  • OpenDaylight is a free, open-source SDN platform for API, Linux, macOS, self-hosted, and Windows use, downloadable as a tar or zip or through Docker images; consider it if those distribution options and platforms fit better.

Verdict

Choose ONOS if you are building programmable service-provider, data-center, or campus networks and can support its Kubernetes-oriented deployment. Its strongest case is the combination of distributed control and broad network interfaces at no software cost. Look elsewhere for a simpler management tool or a platform that does not require this operational commitment.

The verdict

ONOS offers a broad control-plane architecture for teams building software-defined networks. Review its deployment approach and the listed release information when assessing fit.

Questions people ask

Is ONOS free?

Yes. The ONOS plan is free, and the project is open source under the Apache License 2.0.

Which platforms does ONOS support?

Its listed platforms are API, Linux, macOS, self-hosted, and web.

Which network protocols are supported?

Supported interfaces and protocols include P4Runtime, gNMI/OpenConfig, gNOI, OpenFlow, OVSDB, NETCONF, and SNMP.

Can ONOS run across multiple servers?

Yes. Identical instances form a symmetric cluster that distributes work and handles instance failures.

How is ONOS deployed?

The microservices are designed for Kubernetes on cloud and data-center infrastructure, with Docker images and Helm charts listed for deployment.

What the maker publishes

Audience
ONOS is designed as an SDN platform for controlling service provider networks, with the architecture documentation also identifying data center and campus networks as possible uses. source
Availability and scalability
The µONOS documentation describes the architecture as highly available and dynamically scalable. source
BGP integration
The SDN-IP application lets an ONOS-controlled SDN network exchange traffic with adjacent external networks using BGP. source
Deployment
µONOS microservices are designed for deployment on cloud and data center infrastructure using Kubernetes, with Docker images and Helm charts listed as deployment tools. source
Deployment
µONOS is composed of microservices deployable on cloud and data-center infrastructure using Kubernetes, with Docker images and Helm charts listed as deployment tools. source
Distributed design
ONOS uses a symmetric cluster of identical instances designed to distribute work and handle instance failures. source
Distributed operation
ONOS can run across multiple servers to use their resources and provide fault tolerance when a server fails. source
Download options
The ONOS downloads page says production deployments should use the release tar.gz package or Docker image, while development can use the source repository. source
Interfaces
The µONOS architecture lists P4/P4Runtime, gNMI/OpenConfig, and gNOI as control and configuration interfaces or standards, and uses gRPC for its polyglot interfaces. source
Interfaces and standards
µONOS is based on interfaces and standards including P4/P4Runtime, gNMI/OpenConfig, and gNOI, and uses gRPC between modular microservices. source
Latest listed LTS
The downloads page lists X-Wing 2.7.0, dated July 16, 2021, as an LTS release. source
License
The ONOS wiki says the project is distributed under the Apache 2.0 license. source
Network control
The ONOS architecture describes robust north-facing abstractions for applications and south-facing abstractions for controlling and managing devices across protocols. source
Network operations
The µONOS architecture supports network device configuration, monitoring and maintenance, forwarding plane programming, topology validation, and fine-grained performance metric collection. source
Network operations
The µONOS architecture supports device configuration, monitoring and maintenance, P4 forwarding-pipeline programming, topology and forwarding-behavior validation, and collection of fine-grained network metrics. source
OpenFlow
The ONOS wiki identifies OpenFlow as its primary southbound protocol for programming switch flow tables. source
Open source
The ONOS source code is published under the Apache License 2.0. source
Protocol support
The ONOS documentation describes OpenFlow as its primary southbound protocol and names OVSDB, NETCONF, and SNMP as other southbound configuration protocols. source
Purpose
ONOS provides the control plane for software-defined networks, managing network components and running programs or modules that provide communication services. source
Purpose
ONOS provides the control plane for software-defined networks, managing network components and running software modules that provide communication services. source
Security
The project wiki describes a Security Mode feature intended to restrict application access to northbound APIs. source
Support and community
The ONOS wiki directs users with questions to its FAQ, mailing list, or Slack team and describes the project as community-backed. source
Support and community
The project wiki directs users with questions to its mailing list or Slack team and lists a help email address. source
Target networks
ONOS aims to serve as an SDN system platform for service-provider networks and can also be used for data-center or campus networks. source

Checked against the maker's pages on 8 Oct 2026.