Skip to content
SPECIFICTION
Get listed

ONOS

onosproject.org

Free plan WebmacOSLinuxAPISelf-hosted

What it is

ONOS is an open-source software-defined networking platform that provides a control plane for managing network components and running communication-service modules. Its µONOS architecture supports device configuration, monitoring and maintenance, forwarding-plane programming, topology validation, and 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. Control and configuration interfaces include P4/P4Runtime, gNMI/OpenConfig, and gNOI, with gRPC connecting modular microservices. OpenFlow is the primary southbound protocol, and OVSDB, NETCONF, and SNMP are also named for device configuration. The microservices are designed for cloud and data center infrastructure using Kubernetes, 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 is free and published under the Apache License 2.0. It is aimed mainly at service-provider networks, with data-center and campus networks also identified as possible uses. Production downloads are recommended as a release tar.gz package or Docker image; the listed LTS release is X-Wing 2.7.0, dated July 16, 2021.

Spec sheet

Purpose
ONOS provides the control plane for software-defined networks, managing network components and running software modules that provide communication services.Read 8 Oct 2026 · wiki.onosproject.org
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.Read 7 Oct 2026 · wiki.onosproject.org
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.Read 8 Oct 2026 · docs.onosproject.org
Security
The project wiki describes a Security Mode feature intended to restrict application access to northbound APIs.Read 8 Oct 2026 · wiki.onosproject.org
License
The ONOS wiki says the project is distributed under the Apache 2.0 license.Read 7 Oct 2026 · wiki.onosproject.org
Availability and scalability
The µONOS documentation describes the architecture as highly available and dynamically scalable.Read 7 Oct 2026 · docs.onosproject.org
BGP integration
The SDN-IP application lets an ONOS-controlled SDN network exchange traffic with adjacent external networks using BGP.Read 8 Oct 2026 · wiki.onosproject.org
Distributed design
ONOS uses a symmetric cluster of identical instances designed to distribute work and handle instance failures.Read 8 Oct 2026 · wiki.onosproject.org
Distributed operation
ONOS can run across multiple servers to use their resources and provide fault tolerance when a server fails.Read 7 Oct 2026 · wiki.onosproject.org
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.Read 8 Oct 2026 · wiki.onosproject.org
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.Read 8 Oct 2026 · docs.onosproject.org
Interfaces and standards
µONOS is based on interfaces and standards including P4/P4Runtime, gNMI/OpenConfig, and gNOI, and uses gRPC between modular microservices.Read 7 Oct 2026 · docs.onosproject.org
Latest listed LTS
The downloads page lists X-Wing 2.7.0, dated July 16, 2021, as an LTS release.Read 8 Oct 2026 · wiki.onosproject.org
Network control
The ONOS architecture describes robust north-facing abstractions for applications and south-facing abstractions for controlling and managing devices across protocols.Read 8 Oct 2026 · wiki.onosproject.org
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.Read 8 Oct 2026 · docs.onosproject.org
Open source
The ONOS source code is published under the Apache License 2.0.Read 8 Oct 2026 · github.com
OpenFlow
The ONOS wiki identifies OpenFlow as its primary southbound protocol for programming switch flow tables.Read 8 Oct 2026 · wiki.onosproject.org
Protocol support
The ONOS documentation describes OpenFlow as its primary southbound protocol and names OVSDB, NETCONF, and SNMP as other southbound configuration protocols.Read 7 Oct 2026 · wiki.onosproject.org
Support and community
The project wiki directs users with questions to its mailing list or Slack team and lists a help email address.Read 8 Oct 2026 · wiki.onosproject.org
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.Read 8 Oct 2026 · wiki.onosproject.org
Web interface
The ONOS GUI is a cloud-native application for Kubernetes that uses Angular and gRPC Web to access backend modules.Read 7 Oct 2026 · docs.onosproject.org

Plans and prices

ONOS Free Open-source software · Apache License 2.0 Read 8 Oct 2026 · github.com

Every ONOS plan and price →

Strong points and limits

Strong points

  • Free and distributed under Apache License 2.0
  • Designed for clustered operation and fault tolerance
  • Supports P4Runtime and gNMI/OpenConfig
  • Kubernetes deployment tools include Docker images and Helm charts
  • Includes a cloud-native web GUI

Limits

  • Latest listed LTS is dated July 16, 2021
  • Production deployments are directed to tar.gz or Docker downloads

Who it suits

ONOS suits teams building or operating software-defined networks, especially service providers. Its documentation also identifies data-center and campus networks as possible settings.

ONOS in depth

Read the full write-up

ONOS is a software-defined networking control platform for teams building and operating large managed networks. It is strongest where distributed control and programmable interfaces matter; teams seeking a ready-made tool for routine network administration should look elsewhere.

Overview

ONOS gives network applications a way to control devices across different protocols, with abstractions facing both the applications and the network. Its symmetric cluster of identical instances distributes work and is designed to keep operating when an instance fails. For service-provider networks, where controller resilience matters, that architecture is a meaningful advantage. Data-center and campus networks are also possible uses.

The distributed design is not a shortcut around infrastructure work. µONOS microservices are intended for cloud and data-center environments and use Kubernetes; teams need the skills and operational capacity to deploy and maintain that environment. ONOS is a network control platform, not a general-purpose configuration dashboard.

Key features

Network operations: µONOS covers device configuration, monitoring and maintenance, forwarding-plane programming, topology validation, and detailed performance metrics. That breadth suits operators who need to program and observe the network, not just change device settings.

Interfaces and protocols: µONOS uses P4/P4Runtime, gNMI/OpenConfig, and gNOI, with gRPC connecting modular microservices. The ONOS documentation also identifies OpenFlow as its primary southbound protocol, with OVSDB, NETCONF, and SNMP among the other configuration protocols. This range is useful for mixed environments, though teams still need to match their devices and workflows to the relevant interfaces.

External routing: The SDN-IP application lets an ONOS-controlled network exchange traffic with adjacent external networks using BGP, extending its reach beyond the controlled network.

Deployment and interface: Docker images and Helm charts support Kubernetes deployment. The cloud-native GUI uses Angular and gRPC Web to reach backend modules. Production downloads are offered as a release tar.gz package or Docker image; development can use the source repository.

Application security: Security Mode is intended to restrict applications' access to northbound APIs. That is relevant when multiple applications interact with the controller, though the feature's stated purpose alone does not establish a complete security model.

Pricing

ONOS costs free. The ONOS plan is open-source software under the Apache License 2.0, so it suits teams that want to deploy and adapt the platform without a software license charge. The trade-off is that deployment and operation remain the team's responsibility; the community points users to its FAQ, mailing list, and Slack team for questions.

Platforms

ONOS supports API, Linux, macOS, self-hosted, and web environments. Its network-control standards include P4Runtime, gNMI/OpenConfig, gNOI, and OpenFlow. Kubernetes is central to the µONOS deployment approach, with Docker images and Helm charts among the deployment tools. The downloads page identifies X-Wing 2.7.0, dated July 16, 2021, as the latest listed long-term-support release. That release date is a reason for teams with current deployment requirements to check compatibility before committing.

Who it's for

ONOS is best for network engineering teams building programmable control systems for service-provider networks, with data-center and campus operators also in scope. Its distributed architecture, protocol interfaces, and operations capabilities are most valuable when teams can invest in Kubernetes-based infrastructure and need control across network devices. It is a poor fit for organizations looking for a simple, preconfigured management product or lacking the capacity to operate a distributed platform.

Pros and cons

Pro — resilient distributed design: Identical cluster instances distribute work and are designed to handle instance failures, a useful foundation for critical network control.

Pro — broad control coverage: Multiple device protocols and interfaces pair with configuration, monitoring, topology validation, and forwarding-plane programming.

Pro — no license charge: The Apache 2.0 open-source plan gives teams room to use and adapt the software without a paid tier.

Con — infrastructure demands: Kubernetes-oriented microservices make ONOS a substantial operational commitment compared with a conventional network management tool.

Con — release currency: The latest listed LTS date is in 2021, which may complicate decisions for teams that require a recent long-term-support release.

Alternatives

Choose ManageEngine Network Configuration Manager instead if conventional network configuration management and a capped free edition are a better match: its free plan covers two devices, while its professional edition is priced at $238 a year.

Containerlab is a free alternative for teams focused on network labs; it requires a Linux server or VM, Docker, and sudo privileges for some operations, rather than serving as ONOS's distributed control platform.

Nautobot offers a self-managed open-source Community plan for exploring, initial workflows, and limited production deployments. Pick it when that scope fits better than ONOS's network-control focus.

NetBrain is another network operations option, with a paid subscription license and a free trial; its license is based on network components and seats.

Arista NG Firewall is a web-based alternative with a free tier for basic security and connectivity features, suited to readers seeking those capabilities rather than an SDN control plane.

Cisco pyATS is a free, Apache 2.0-licensed option for teams whose need is network testing rather than distributed device control.

Gluware offers a community edition with up to 20 devices for one renewable year, full application suite except Topology, community support, and on-demand training. It may fit teams looking for that bounded free entry point.

Infoblox Cloud Network Automation is another option for cloud network automation, with token-based licensing priced by agreement.

For category browsing, see Network Automation Software and Software-Defined Networking Software.

Verdict

Choose ONOS if your team needs a programmable, distributed control plane for a service-provider, data-center, or campus network and can operate Kubernetes-based infrastructure. Its broad interfaces and failure-aware cluster design are the main reasons to choose it. Look elsewhere if you need a simpler network administration product or a more recent listed LTS release.

Verdict

ONOS offers a distributed SDN control plane with a broad set of network interfaces and deployment tools. The listed long-term-support release is from 2021, so the stated release information is not recent.

Where Specifiction places it

Alternatives to ONOSAll alternatives →