Understanding NebulaFlex-Mode

Many customers ask us about the differences between Nebula and NebulaFlex-Mode. As there is plenty of material and aspects to take into account, this article can only be a starting point to see the comparisons between both Nebula and NebulaFlex. Let's start with the question:

What is actually NebulaFlex? ( https://www.zyxel.com/solutions/NebulaFlex-20180115-002662.shtml )

NebulaFlex is a technology unique to Zyxel which allows devices, which usually are designed for standalone operation, to be integrated seemlessly into the Nebula platform. This gives you as a customer high flexibility and a variety of choices in regards of the way how you want to reach out to configure your devices. If you are having a small home-unit with just a single Access-Point, maybe the standalone deployment might be the right choice for you. 

Whatever it is, NebulaFlex gives you the flexibility to choose between both options!

How does NebulaFlex work?

Talking about the main concept of Nebula, this basically means that certain devices from certain firmware onwards first check, if they are registered to the Nebula cloud platform on booting. If they receive back a respective token, they enter the "Nebula"-Mode. The main configuration is now dealt via the Nebula Control Center via https://nebula.zyxel.com/ . If there is no feedback from the cloud, the unit will enter the standalone mode. 

Things to consider:

- In order to ensure your devices having NebulaFlex properly implemented, always be sure to have the latest firmware deployed to your NebulaFlex-capable devices! We often receive requests, claiming the NebulaFlex to not work, but instead the issue is being having the respective device on older firmware which yet did not have NebulaFlex implemented.