Connection schemes
Typical ways to connect sites to Qarvix. These schemes help quickly explain where the router sits, how WireGuard traffic flows, which LAN subnets are reachable over the tunnel, and what the service team gets.
A site with a regular SIM card
The router sits behind a mobile carrier, with no public IP and no port forwarding. The agent brings up its own WSS management channel to the Qarvix Control Plane, while user traffic runs over WireGuard.
Benefit: the site can be connected without a public IP, without changing the carrier's plan, and without manual port forwarding.
Cameras and devices behind a router
Qarvix opens access not just to the router itself, but to the LAN subnet behind it: cameras, controllers, POS terminals, PLCs, or local servers. The route to the subnet is turned on in the dashboard.
Benefit: the service team gets access to the subnet and device APIs it needs, without configuring a VPN on every camera or workstation.
Data from sensors and devices behind a router
Qarvix lets you pull readings from meters, sensors, PLCs, and local servers over an encrypted tunnel, even when the site sits behind a SIM card, carrier NAT, or a closed network.
Benefit: sensor and meter data is available over an encrypted tunnel without a public IP, port forwarding, or a site visit.
Multiple sites in one mesh
Branches, retail locations, or industrial sites connect to one managed mesh. Access rights stay separated, while a manager sees the site network as a single system.
Benefit: instead of scattered VPN files, passwords, and manual spreadsheets, you get a centralized map of access, sites, and events.