Dan Bunyard
Networking Connoisseur

< Back to Case Studies

This report was submitted to us by one of our users on their views on the differences between the CT WiFi Dashboard and the UniFi Controller.

It was submitted on 10/Feb/2016, and so is a reflection of the feature-set at that time, as well as their own personal opinions. Changes may have been made to both the CT WiFi dashboard and UniFi controller since then.


CT WiFi Dashboard VS UniFi Controller

(NOTE: Using latest 4.8.x branch of Unifi, 4.8.12 as of the time of this writing)

First off let me start by saying if you are coming from UniFi you will find the interface somewhat familiar. The main navigation for needed functions are down the left side, while the "meat" of the content occupies the right 3/4 of the screen.

That being said let's take a look at some of the key differences.


From a Client View Perspective:

Not much to see here, both are very similar and offer great insights to the clients connected to your network:

UniFi Controller Client List
CT WiFi Dashboard Client List

CT WiFi does offer up a nice graph showing clients and throughput however with the throughput being bugged it's not overly useful.

Further breakdown of pros and cons of CT WiFi vs UniFi:

Pros:

  • + Better graphs and insights, able to see more details about signal levels
  • + WAY cleaner interface and graphing

Cons:

  • - No way to disconnect/block a client unless connected via a splash page
  • - As noted above usage statistics are bugged and need sorted out

Networks/SSIDs:

There is more gained here than lost.

The huge one is the ability to add/change/remove SSIDs without causing the entire network to reload (breaking connectivity for up to 5 minutes). UniFi is terrible from that perspective.

Pictures here don't really help compare as it's apples and oranges.

Pros:

  • + WAY better splash page options
  • + WAY better guest management and control over their usages
  • + Content filtering per SSID
  • + As mentioned above adding/changing/removing SSIDs doesn't break the network for 5 minutes

Cons:

  • - No time-based SSIDs, as in ability to disabled SSIDs during certain time periods. This is something UniFi does well:
  • UniFi Timed SSIDs
  • - Speed restrictions cannot be enforced SSID-wide, only controllable via splash pages. UniFi uses "groups" which can be applied to an SSID and restrict download/upload speeds.

    • General:

      As with the SSIDs noted above there is more to be gained here than lost. Let's just dive straight into the list:

      Pros:

      • + As eluded to above most changes require small blips AT MOST! UniFi will reload the APs for even the smallest of modifications
      • + WAY easier upgrades
      • + More advanced firewalling - UniFi is basic at best
      • + WAY more diagnostic capabilities
      • + WAY better reporting
      • + API has way more functionality than UniFi

      Cons:

      • - No SNMP
      • - No syslog without a paid plan
      • - No type of RSSI/floor plan maps to show estimated coverage. UniFi has at least basic capabilities:
      • UniFi Floorplan

        A general note, UniFi is local hosted while CT WiFi is cloud hosted. No real pro/con here, just something to keep in mind.


        Conclusion:

        CT WiFi is built around the guest access/splash model. While not a bad thing that does restrict some functionality if you aren't using those features.

        However at the end of the day the pros outweigh the cons in every instance. The only feature preventing me from a migrating is the time-based SSIDs as mentioned above.

        Overall CT WiFi is a very solid platform with amazing support.


        CT WiFi is a cloud based WiFi management platform for businesses. The firmware gives consumer-grade WiFi access points enterprise-like capabilities. Or you can utilise the captive portal solution with your existing infrastructure. Create a free account and check it here ct-networks.io

        Come join CT WiFi

        Sign Up

        Sign-up for CT WiFi, it's free for unlimited access points :)


        </div> </div>