Cloud controller vs local hardware controller

A network controller can exist in one of two forms: cloud-based or as a local hardware controller on the physical site. Regardless of which setup your network uses, MyPlace requires an API connection or similar access to integrate seamlessly and perform its functions, whether it’s onboarding guests or gathering data.

For cloud-based controllers, integration is straightforward. These controllers typically have a host name or endpoint that can be accessed over the internet, along with user credentials or API keys that allow MyPlace to establish a secure connection. This setup simplifies the process and makes it easy to manage your Wi-Fi network remotely while enabling MyPlace to capture customer data efficiently.

Local hardware controllers, on the other hand, require a bit more setup for remote access. To connect MyPlace to a local controller, we will need API access or similar, which is enabled by setting up a port forwarding rule on the local firewall or router. This rule allows MyPlace to communicate with the controller remotely. For added security, the port forwarding rule can be locked down by restricting access to specific IP addresses that MyPlace provides, ensuring only authorized systems can access the controller.