Why does my network always need to be connected to the Plume Cloud?

Most Plume features are cloud-controlled and require a continuous connection to the Plume Cloud to function properly. There are two main reasons for communication between the Cloud and a network. The first is to get information from the network to be analysed by the Cloud. The second, to make changes on the network based on the information received.

Adapt features are controlled by the Cloud and rely on data collected from the network to function. Optimizations need information about the WiFi environment and network performance. Device Typing needs descriptions of connected devices. Steering needs information about device performance and connection strength. This information is collected continuously and sent to the Cloud instead of being stored on the pods.

Settings for other Plume features are also stored on the cloud instead of on the local network. This means that without a connection to the cloud, settings will not be applied to devices when they need to be changed. For example, a device that has an internet freeze applied will not be unfrozen until the cloud tells the network to unfreeze the device.

Some Plume features also rely on other services that connect with the Cloud. These include Sense, Content Filtering and Guard features. A connection to the Cloud must be maintained so that information collected by the network can be passed on to these other services.