← Back to Mesh

ProgreTech Mesh

How your device reaches your agent

Mesh is direct-first. Your device and your agent are the normal data endpoints. ProgreTech helps establish trust and connectivity, but it does not need to sit in the middle of every conversation.

Same network

Your browser or installed PWA connects directly to the agent over the local network. Supporting browsers ask for local-network permission. Once paired, this path can continue when the internet is unavailable.

Owner device → Agent

Different networks

Mesh uses encrypted peer-to-peer networking. Temporary signaling introduces the endpoints and STUN helps discover a usable route. The session then travels directly between owner and agent when the network permits it.

Owner device ⇄ encrypted P2P ⇄ Agent

Restrictive networks

Some corporate, carrier, or home networks block peer-to-peer traffic. If the owner allows it, Mesh can use an encrypted TURN relay as a fallback. Direct remains preferred.

Owner device → encrypted relay → Agent

You control the routing policy

Direct preferred tries direct first. Direct only never permits a TURN relay. Relay allowed still prefers direct but allows an encrypted fallback when needed.

Offline PWA behavior

The installed PWA caches its interface, not your operational history. It remembers encrypted local connection credentials in the owner browser. If internet access disappears but the owner device and agent still share a LAN, the PWA can signal the agent locally and rebuild the direct WebRTC connection.

What ProgreTech handles

ProgreTech may provide sign-in, trust, package distribution, revocation, discovery, and temporary signaling. These functions are separate from carrying the live owner-agent session. Relay traffic is optional and policy-controlled.