System overview

How the hybrid local-cloud model fits together.

DunhuConnect keeps the local network meaningful on its own, then layers cloud services on top for continuity rather than dependency.

1. Local infrastructure

A Raspberry Pi Supernode and ESP32 root/node devices provide the on-site network foundation, local control, and hardware-aware access flow.

2. User entry points

People can join through the mobile SuperApp, the lightweight captive portal, or the desktop portal depending on device and context.

3. Local-first services

Data Wallet, fair usage, notices, device mapping, and local communication continue to prioritize the nearby Supernode.

4. Cloud continuity later

Cloudflare Pages and Workers can support the public site, DunhuConsole, future sync, and future Jose AI routing when internet is available.

Cloud can help, but local control reduces fragility.

On-site connectivity should not disappear just because a backhaul link fails.

Community access control decisions should stay understandable and close to the network.

Local portals and the SuperApp should still make sense in offline or low-backhaul conditions.

Cloud sync and AI should arrive as optional capabilities with clear consent and boundaries.