Less setup for customers
Provision an individual device identity, then let customers approve access at a supported site without entering a Wi-Fi password.
- DEVICE
Enrolled IoT device
Individual certificate. Its private key stays on the device.
EAP-TLS → HotSpotVU gateway - CUSTOMER SITE
HotSpotVU gateway
Admit approved devices. Apply isolation and local capacity controls.
Site uplink → Your Internet servicesIdentity + policy → Verify and authorize - APPLICATION TRAFFIC
Your Internet services
Use the site’s existing uplink to reach the device application.
- IDENTITY & POLICY
Verify and authorize
EAP-TLS identity checks and the business’s per-device permission.
Scoped events → Dashboard and API - SCOPED OPERATIONS
Dashboard and API
Fleet observations, connection events and freshness timestamps.
Read the diagram description
- DEVICE — Enrolled IoT device. Individual certificate. Its private key stays on the device.EAP-TLS → HotSpotVU gateway.
- CUSTOMER SITE — HotSpotVU gateway. Admit approved devices. Apply isolation and local capacity controls.Site uplink → Your Internet services.Identity + policy → Verify and authorize.
- APPLICATION TRAFFIC — Your Internet services. Use the site’s existing uplink to reach the device application.
- IDENTITY & POLICY — Verify and authorize. EAP-TLS identity checks and the business’s per-device permission.Scoped events → Dashboard and API.
- SCOPED OPERATIONS — Dashboard and API. Fleet observations, connection events and freshness timestamps.
How it works
Automatic connectivity applies to compatible, enrolled devices on explicitly enabled, supported sites with working Internet service. Local business permission is required.
- 01
Manufacturer
Provision identity
Give each device an individual identity and credentials during provisioning.
- 02
Device
Discover the network
Find a supported HotSpotVU network and present the enrolled identity.
- 03
Local business
Approve access
Review the individual request and allow or deny that device.
Only allowed devices continue.
- 04
Device and support teams
Connect and observe
An allowed device reconnects automatically. Each party sees its relevant connection state.
A service built for the whole deployment
Manufacturers receive enrollment APIs, fleet views, and integration guidance. Solution providers receive explicitly delegated, read-only visibility into customer fleets. Businesses retain local admission and capacity controls.
HotSpotVU satellites use the same identity and connection foundation, with additional backhaul and access-point management. Existing guest Wi-Fi remains a separate service.
Start in a sandbox
Self-service sandbox enrollment supports ten devices and one explicitly authorized test site. Hardware and an upstream Internet connection are separate. Production activation requires a HotSpotVU review.
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.
Standards and interoperability
HotSpotVU’s IoT architecture uses certificate-based Wi-Fi authentication, with a roadmap toward Passpoint and OpenRoaming interoperability. External roaming remains subject to qualification and partner arrangements.
Public compatibility information will identify validated platforms and coverage. OpenRoaming certification and global service availability are future qualification milestones.