Businesses with multiple locations face a recurring infrastructure problem: how do you manage IT resources at branch offices, warehouses, retail stores, or remote sites without maintaining VPN connections to each one?
Traditional Approaches and Their Problems
Traditional approaches include site-to-site VPNs (expensive, complex, fragile), dedicated management networks (even more expensive), or dispatching IT staff to each location (slow, costly, unscalable). Each approach has its own maintenance burden and failure modes.
The ProxyPass Model
ProxyPass provides an alternative. One node per site, installed in under two minutes. Every site connects to your ProxyPass dashboard through an outbound tunnel. From your central IT team's perspective, every site is one hop away — regardless of its physical location, ISP, or network configuration.
Through CONNECT mode, your team can SSH into Linux servers, RDP into Windows workstations, and access databases at any site. Through the REST Bridge, they can manage IoT devices, network equipment with web interfaces, and local services. Through File Mount, they can access files, pull logs, and push configuration updates.
Scenario: Growing from 3 Offices to 15
A consulting firm starts with 3 offices — Vienna, Munich, and Zurich. The IT team maintains a site-to-site VPN between all three. It works, but it requires VPN hardware at each site, static IPs, and periodic certificate renewals.
The firm grows. Over two years, they open 12 more offices across Europe. With VPNs, the network topology becomes a mesh nightmare — 15 sites means managing dozens of VPN tunnels, each with its own configuration and failure mode. Every new office takes a week to set up because of hardware procurement, ISP coordination, and VPN configuration.
With ProxyPass, each new office takes two minutes to set up. The IT team sends an install command to the local office manager. The node connects. The office is immediately accessible from the central IT dashboard.
Security by Group
Each site can be its own node group with its own security settings. A headquarters group might use shared API keys for convenience. A customer-facing group might require individual keys and protected registration. Different security levels for different trust levels.
Resilience
If a site's network changes — new ISP, new router, new firewall — nothing breaks, because the node makes only outbound connections and does not depend on any inbound configuration. If a site closes, you block its nodes. If a new site opens, you send an install command.
For growing businesses, this model scales with you. One site or a hundred sites — the dashboard and API work the same way. No VPN topology to redesign. No firewall rule matrix to maintain. Just nodes connecting outward and access flowing through the tunnel.