Omada Controller

Omada Controller is a Docker image that runs TP-Link's Omada software-defined networking controller to manage Omada wireless access points in self-hosted…

  • Network Services
  • Other
  • Tools & Utilities
Omada Controller is a Docker image that runs TP-Link's Omada software-defined networking controller to manage Omada wireless access points in self-hosted deployments.

Platform availability

Available on 5 of 10 platforms

  • Unraid
  • TrueNAS
  • Umbrel
  • ZimaOS
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

74/100 Good

Maintained
100last commit 18 days ago
Popular
621,307 GitHub stars
Easy to install
755 install platforms, install notes, Docker image
Light to run
206 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 14 days ago

GitHub stars
1,307
Open issues
15
Last commit
2026-11-03
Latest release
v6.3.0.111
License
AGPL-3.0
Activity
declining

Checked 17 days ago - source: GitHub (mbentley/docker-omada-controller)

Resources & Compatibility

Minimum requirements: 6 GB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • API calls use port 8043 If you use the Omada API, its examples call https://localhost:8043, so replace localhost with your controller's address and make sure port 8043 is open, or API calls won't reach the controller. The examples also use curl's insecure flag, so you may see a certificate warning when testing. source

Fetched 54 days ago - each note links to its source

Alternatives (3)

  • OpenWISP - OpenWISP is a free and open-source platform for efficient IT network deployment, monitoring & management.
  • UniFi Network - The UniFi® Network application is a Software-Defined Networking (SDN) platform, which provides an end-to-end system of network devices acro…
  • omada - Omada is TP-Link's software controller for centrally managing its Omada routers, switches, and access points on a self-hosted network, with…

Checked 40 days ago - source: AlternativeTo

Common questions

Which port must be reachable for Omada API calls?

The Omada API examples target port 8043, so port 8043 must be open on the controller address. Testing with curl's insecure flag may show a certificate warning.

What network address setup should I consider when self-hosting the controller with a VPN?

A self-hosting example uses a nonstandard 10.132.x.x range to avoid conflicts with VPNs. It also keeps the controller on a server with a static IP.

Can one software Omada controller manage multiple independent sites?

One user manages two completely independent sites on Omada Cloud Essentials. The source describes it as a hardware-free/software controller rather than a physical OC controller.

How do I match Omada AP pre-release firmware to a controller/app version?

The pre-release firmware note lists minimum update firmware and recommended management controller/app versions by AP series. For EAP65x/EAP67x, the minimum update firmware is EAP65x and the recommended controller/app is EAP650.

Answers sourced from community.tp-link.com, community.tp-link.com, use1-omada-northbound.tplinkcloud.com, www.reddit.com

Community

Collected 48 days ago - public community threads