← All guidesDEPLOYMENT CHOICES

Cloud vs on-site guest WiFi management

Understand where authentication runs, what needs connectivity and who keeps the system operating.

Separate management from internet access

“Cloud-managed WiFi” can describe several different architectures. The dashboard, login page, authentication service and traffic gateway do not necessarily run in the same place. Before choosing a deployment, ask which service makes the decision to let a guest online.

Your internet uplink is separate again. Keeping a local dashboard running does not create an internet connection when broadband is down.

Cloud hosting: central operation

In a cloud-hosted setup, management and authentication services run outside the venue. This can simplify application hosting and give operators a central view across locations. The venue still needs correctly configured network equipment and a working connection to the services it uses.

Agree who handles updates, backups, account access and connectivity monitoring. A static public IP is not always necessary, but the connection method must be suitable for the controller or gateway and validated during configuration.

On-site hosting: keep local workflows close

With management and authentication on-site, staff can use local services while the cloud connection is unavailable. In WiFiMitra’s on-site model, previously provisioned staff can sign in and issue new vouchers while those services remain operational; records can sync when connectivity returns.

The local computer becomes an operational dependency. It needs power, storage, updates, backups and a recovery plan. On-site does not mean “always available”, and cloud independence does not remove dependencies on external services such as message delivery.

Walk through three failure scenarios

Questions to resolve before installation
InterruptionWhat to verify
Cloud service unreachableCan the local system issue and validate new vouchers? Cloud authentication needs its service connection.
Internet uplink downLocal management may remain available, but browsing needs a working uplink or a configured backup connection.
Local box or gateway downServices on that device stop. The traffic impact depends on its role and the configured network design.

Also test whether existing sessions continue. That behaviour depends on the gateway, controller and enforcement configuration; it should not be assumed from the hosting label.

Know what stays at the venue

When using WiFiMitra Gateway, guest traffic enforcement remains at the venue even if management is cloud-hosted. Compatible access points provide coverage; the gateway applies the configured guest access policies.

With an existing-network integration, responsibilities vary by controller and gateway. Ask for a simple diagram showing the guest device, access point, gateway, portal and authentication service. Mark which connections must work for a new guest to sign in.

Choose an operating model your team can support

  • Consider cloud hosting when central administration is important and the venue has dependable connectivity.
  • Consider on-site hosting when continued local staff workflows during cloud outages are important and someone can maintain the local equipment.
  • In either case, agree monitoring, backups, update ownership and an escalation path with your team or SI partner.

Before handover, test a new login, pass extension, revocation and recovery from the agreed outage scenarios. Record the results for the actual hardware and software versions at your site.