Two hundred field devices, zero mesh clients

Two hundred kiosks in the field need to phone home. The mesh-network answer is an agent on every device: enrollment, key rotation, a client binary that must build for your embedded platform and survive its updates.

The Hoody answer is that the fleet already speaks the only protocol required. Each device POSTs its readings over plain HTTPS to its container's pipe URL, carrying a bearer token that a token group validates at the proxy. Outbound HTTPS works on any SIM, any NAT, any hotel-grade network a device finds itself behind. Enrollment is minting a token; revocation is deleting it.

Nothing installs on the device, because HTTPS was already there.

The fleet needs HTTPS and a token, which is to say it needs nothing new.