HotSpotVU is currently available to businesses in Canada only.
Managed coverage extension

Implementation candidate · managed-site validation required

Make coverage easier to deploy and support.

Extend a supported site with an enrolled satellite, a clear business-approval step and visible installation states. Give your team a defined workflow from first power-on to confirmed backhaul and client Wi-Fi.

Explore the business caseExplore developer tools
MANAGED COVERAGEGatewayExisting Internet uplinkSatelliteApproved backhaulDevicesExtended local coverageLocal control. Shared visibility.Identity · permission · fresh connection evidence
GatewayExisting Internet uplink
SatelliteApproved backhaul
DevicesExtended local coverage
Local control. Shared visibility.Identity · permission · fresh evidence
Illustrative flow · supported sites require validation and activation

Minimal installation steps

The normal installation flow needs no Wi-Fi password entry, mandatory QR scan, manual BSSID setting, or SSH session.

Visible installation state

See approval, backhaul connectivity, access-point activation, Internet reachability, and recent reporting separately.

Control stays with the business

Each business decides which individual devices may use its site. Network permission does not transfer ownership.

Why this belongs in your solution

Treat coverage as a managed part of the service.

Adding coverage also adds equipment to install and support. The managed-satellite workflow gives a supported unit its own identity, a clear approval step and separate evidence for backhaul, client Wi-Fi and Internet reachability.

Aim for fewer installation decisions and a clearer handoff to support.

Existing gateway

Supplies the managed network and upstream Internet connection.

Approved satellite

Joins with an individual identity and restricted encrypted backhaul.

Visible operation

Check applied configuration, AP activation and recent observations.

Satellite request, individual site approval, secure backhaul configuration, and activation of the client-facing access point.
Satellite request, individual site approval, secure backhaul configuration, and activation of the client-facing access point.
  • EXISTING SITE

    Gateway and uplink

    The gateway provides the managed network and upstream Internet service.

    Encrypted link → Managed satellite
  • ENROLLED INFRASTRUCTURE

    Managed satellite

    Authenticate the unit and apply its approved backhaul configuration.

    Approved AP → Client-facing Wi-FiConfig + health → Check each function
  • LOCAL COVERAGE

    Client-facing Wi-Fi

    Activate the approved access point. Keep traffic classes separated.

  • BUSINESS CONTROL

    Approve this satellite

    Grant this infrastructure identity permission at this location.

    Allow this unit → Gateway and uplink
  • INSTALLATION EVIDENCE

    Check each function

    Backhaul, AP activation, Internet reachability and reporting freshness.

Open full-size SVG ↗Download SVGMermaid source
Read the diagram description
  • EXISTING SITE — Gateway and uplink. The gateway provides the managed network and upstream Internet service.Encrypted link → Managed satellite.
  • ENROLLED INFRASTRUCTURE — Managed satellite. Authenticate the unit and apply its approved backhaul configuration.Approved AP → Client-facing Wi-Fi.Config + health → Check each function.
  • LOCAL COVERAGE — Client-facing Wi-Fi. Activate the approved access point. Keep traffic classes separated.
  • BUSINESS CONTROL — Approve this satellite. Grant this infrastructure identity permission at this location.Allow this unit → Gateway and uplink.
  • INSTALLATION EVIDENCE — Check each function. Backhaul, AP activation, Internet reachability and reporting freshness.

Installation flow

Newly managed satellites need an enrolled infrastructure identity and compatible signed software. An existing legacy satellite is not silently converted.

  1. Power on the satellite near the gateway.
  2. Open the site dashboard and review the identified satellite request.
  3. Allow that satellite for the location.
  4. Wait for secure backhaul and access-point activation to be confirmed.
  5. Position it where the dashboard still reports an adequate backhaul signal.

A connection light is not the whole story

A satellite may have a working backhaul while the site’s Internet connection is down. It may also be connected but not yet applying the expected access-point configuration.

The dashboard reports each observed state with a freshness timestamp. Missing reports become unknown instead of remaining green indefinitely.

Compatibility and qualification

The first implementation targets single-hop GL-MT6000 gateway-to-satellite deployments. Encrypted backhaul, enterprise authentication, network separation, and recovery require physical qualification before production availability.

Multi-hop mesh and arbitrary third-party range extenders are outside the initial release. A satellite requires a functioning gateway and upstream Internet service.

Availability

Software implementation candidate. Physical router and device qualification is pending. IoT network features are disabled by default, and production activation is reviewed by HotSpotVU. Authorized sandbox trials use a bounded service-admin test window; this does not establish production qualification.

Existing guest connectivity remains separate. New IoT and managed-satellite network features are enabled deliberately per qualified site.

Connect with a clear path to production.

Start on supported Linux/OpenWrt hardware at an authorized HotSpotVU site. The business keeps control of network access. Production activation follows review; external OpenRoaming availability follows separate validation.

Developer resourcesManaged satellites