OpenWiFi is an open-source Wi-Fi software system that combines access point firmware with a cloud controller software development kit (SDK). It runs within the Telecom Infra Project (TIP) OpenLAN group, and its access points (APs) communicate with the controller through the uCentral protocol.
It applies the disaggregated model of open networking to Wi-Fi, so access point hardware and management services can come from different vendors. For a deployment, the important question is whether the exact access point, firmware and controller combination supports the features your network needs.
How the OpenWiFi Stack Works
APNOS, the access point network operating system, is built on OpenWrt. The wlan-ap project provides the firmware build system, hardware profiles and packages that implement uCentral on the device.
Within the controller, the OpenWiFi Gateway (OWGW) manages access points that implement that protocol. Management and telemetry pass through a WebSocket connection between each AP and the gateway, while applications integrate through a northbound REST API defined with OpenAPI.
| Component | What it does | Where it runs |
|---|---|---|
| APNOS and uCentral packages | Run the AP software and implement the device side of the management protocol | Access point |
| OWGW | Manages AP connections and provides a management API | Controller infrastructure |
| OpenWiFi Security (OWSEC) | Provides the security service used for northbound API integration | Controller infrastructure |
| Database and message bus | Support the minimum controller deployment alongside OWGW and OWSEC | Controller infrastructure |
| Firmware, provisioning, analytics and user interface services | Add software management and operational functions | Controller infrastructure |
The SDK is a collection of services, rather than one mandatory controller application. Operators and software vendors can use the full stack, extend it or integrate selected components with an existing management platform.
OWGW can deliver a built-in default configuration or use an operator-supplied configuration. Its user interface can also apply configuration by device type, so verify that newly connected APs receive the intended settings.
This management connection is separate from the choice of how client traffic is forwarded. OpenWiFi AP software supports local breakout and bridging, as well as overlay options, so controller connectivity alone does not describe the client data path.
Discovery and Certificates
Cloud discovery and secure certificate-based onboarding are part of OpenWiFi. Bringing an AP under management requires the firmware, device identity and controller trust configuration to agree.
OWGW uses certificates for the AP connection and separate certificates for its REST API. Device certificates are also part of the configuration, so a reachable gateway is only one part of successful onboarding.
In its Q2 2026 update, TIP described public key infrastructure (PKI) 2.0 as a rebuild of the trust infrastructure. That work covers device identity, controller trust, zero-touch provisioning, cloud discovery, migration and recovery.
Confirm the PKI requirements for the firmware and controller releases you intend to pair. Assign responsibility for certificate provisioning, renewal and recovery alongside software updates.
OpenWiFi Releases Today
On 12 June 2025, TIP announced OpenWiFi 4.0 with Wi-Fi 7 support. It included APNOS and SDK compatibility for Wi-Fi 7 access points from CIG, Edgecore and Cybertan, together with multiple pre-shared key (MPSK) support in the 6 GHz band.
Development has continued beyond that announcement. The AP firmware reached 5.1.1 on 6 November 2026, while the older 4.2 line also continued receiving releases.
| Milestone or AP firmware tag | Date | Status or announced change |
|---|---|---|
| OpenWiFi 4.0 announcement | 12 June 2025 | Wi-Fi 7 support in APNOS and SDK, plus 6 GHz MPSK |
| AP firmware 4.1.0 | 8 September 2025 | General availability release |
| AP firmware 4.2.0 | 25 December 2025 | Published release |
| AP firmware 5.0.0 | 18 May 2026 | Tag marked as a pre-release |
| OpenWiFi LTS v4.2 | June 2026 | Long-term support release |
| AP firmware 5.1.0 | 1 September 2026 | General availability release |
| AP firmware 4.2.8 | 30 October 2026 | Published release in the 4.2 line |
| AP firmware 5.1.1 | 6 November 2026 | Published release |
Firmware dates refer to the wlan-ap repository, rather than every component of the controller SDK. TIP says the long-term support release, OpenWiFi LTS v4.2, came out in June 2026, after the original 4.2.0 firmware tag.
AP firmware and the gateway have separate repositories and release histories. A firmware tag does not identify the compatible versions of every controller service, so confirm the complete combination.
The 5.x firmware release entries give version labels and release status, without a feature list or hardware compatibility matrix. The documentation home is still labeled 4.0.0, so it should not be treated as a release-specific guide to 5.1.
TIP described LTS v4.2 work covering interoperability across Wi-Fi generations, security, roaming, capacity, telemetry and resiliency. Before selecting a branch, confirm its maintenance policy, supported APs and compatible controller versions with whoever will support your deployment.
Hardware and Wi-Fi Generations
Wi-Fi 5, Wi-Fi 6 and Wi-Fi 6E access points are part of the OpenWiFi hardware portfolio in indoor and outdoor formats. OpenWiFi 4.0 also includes Wi-Fi 7 support, as TIP announced in June 2025.
OpenWiFi 4.0 hardware coverage includes Edgecore, CIG, Cybertan, HFCL, Inventum, Andrena and Senao. That vendor list does not mean every AP from each company supports OpenWiFi or the same set of features.
Hardware additions for 4.0 include the Edgecore EAP-105. Check the exact hardware variant, firmware image and controller compatibility before ordering, including the features required on each radio.
A supported Wi-Fi generation is only a starting point for choosing an AP. Confirm radio capabilities, regulatory requirements, authentication, roaming and traffic forwarding for the exact equipment and software you will use.
Wi-Fi 7 support alone is not a feature checklist for a particular AP. Confirm multi-link operation (MLO) and preamble puncturing on the hardware and firmware you intend to deploy.
Managed Wi-Fi and Hospitality
OpenWiFi serves enterprises, service providers delivering managed Wi-Fi, hardware vendors and integrators. Its open interfaces let those organizations combine AP hardware with management services and applications that suit their operations.
Hospitality is one area of current work. In its HiTec 2026 recap, TIP described managed service providers (MSPs) evaluating OpenWiFi for hotels and resorts, with requirements including guest onboarding, captive portals, roaming, segmentation, monitoring and analytics.
TIP also said OpenLAN members were working toward recognition of OpenWiFi as a hospitality brand standard. That work is ongoing and does not establish adoption by any particular hotel brand.
For an engineer, those use cases become requirements to test on the proposed system. Guest access, authentication, client isolation, roaming and visibility need to work together across the APs and management services you choose.
What to Check Before Choosing OpenWiFi
Decide whether your team will operate the SDK or use a provider that manages it. The project supports controller deployment through Docker Compose or Helm, but someone still needs to maintain the services, certificates and software lifecycle.
Your controller choice also affects integration work. Confirm which northbound API functions your applications require, how access will be secured and who will diagnose a failure that spans the AP and management platform.
| Check | What to confirm |
|---|---|
| AP hardware | Exact device variant and a firmware image intended for it |
| Firmware and controller | A supported combination, including any vendor-specific changes |
| Required features | Authentication, guest access, roaming, segmentation and telemetry on that combination |
| Onboarding | Device certificates, controller trust and cloud discovery requirements |
| Operations | Responsibility for hosting, monitoring, updates and recovery |
| Maintenance | Release branch, support period and upgrade or migration procedure |
Test the complete combination before replacing a working wireless network. Include onboarding, configuration changes, client authentication, roaming, firmware upgrades and recovery from a lost management connection.
Before deployment, record the AP hardware revision, firmware image, controller release and the tests that passed. Keep the configuration and a recovery procedure with those records.
Hardware Nation is a partner of Accton/Edgecore.
Alex Cronin
Co-Founder and Solutions Architect
LinkedIn | GitHub
Alex Cronin is the founder of Hardware Nation and Nanites AI. He is a graduate of Georgia Tech with 20 years of experience in networking and data center infrastructure across enterprises, service providers and hyperscalers. His work spans traditional and open networking, production SONiC deployments, multivendor integration and direct collaboration with manufacturers and engineering teams. Hardware Nation has served organizations including NASA, Lockheed Martin, Accenture, Stanford University and Georgia Tech.
Alex leads engineering teams and contributes directly to architecture, code, integration and evaluation. At Nanites AI, he has led nearly two years of development of an agentic NetOps platform for network troubleshooting. He also develops AI automation for product research and leads business operations at Hardware Nation.
Nanites AI has been cited in Gartner’s Market Guide for Agentic NetOps Software, covered by InformationWeek and discussed by Cisco DevNet. It was selected as one of 12 finalists from more than 400 applicants in the 2025 T Challenge, organized by T-Mobile and Deutsche Telekom. Alex has presented his work at Deutsche Telekom in Bonn, CableLabs and Network X Americas.
References: TIP OpenLAN | OpenWiFi documentation | AP firmware releases | OpenWiFi Gateway
Alex Cronin
Co-Founder and Solutions Architect
LinkedIn | GitHub
Alex Cronin is the founder of Hardware Nation and Nanites AI. He is a graduate of Georgia Tech with 20 years of experience in networking and data center infrastructure across enterprises, service providers and hyperscalers. His work spans traditional and open networking, production SONiC deployments, multivendor integration and direct collaboration with manufacturers and engineering teams. Hardware Nation has served organizations including NASA, Lockheed Martin, Accenture, Stanford University and Georgia Tech.
Alex leads engineering teams and contributes directly to architecture, code, integration and evaluation. At Nanites AI, he has led nearly two years of development of an agentic NetOps platform for network troubleshooting. He also develops AI automation for product research and leads business operations at Hardware Nation.
Nanites AI has been cited in Gartner’s Market Guide for Agentic NetOps Software, covered by InformationWeek and discussed by Cisco DevNet. It was selected as one of 12 finalists from more than 400 applicants in the 2025 T Challenge, organized by T-Mobile and Deutsche Telekom. Alex has presented his work at Deutsche Telekom in Bonn, CableLabs and Network X Americas.