The overlapping subnet problem
Consumer and small-business routers ship with the same defaults, so clients A, B and C often all use 192.168.1.0/24. A normal VPN can only route one copy of that network at a time. Typical workarounds:
- Re-numbering client networks (risky, disruptive, and printers break).
- Separate VPN profiles per client, switched by hand.
- Jump boxes or remote-control tools for every task.
- Port forwarding to RDP or SSH (an open invitation to brute-force attacks).
How 1:1 address translation solves it
Instead of routing the real subnet, each client site gets its own unique translated range. For example, client A's 192.168.1.0/24 becomes 100.64.1.0/24 and client B's becomes 100.64.2.0/24. The last number stays the same, so 192.168.1.20 at client B is simply 100.64.2.20. Techs can reach both at once, and nothing changes on the client network.
How Arx Cloud does it
- Outbound-only LAN connector: a small connector runs on any always-on machine at the client site. It only makes outgoing connections, so you never open a port on the client's router, and it works behind CGNAT.
- Automatic 1:1 mapping of overlapping RFC1918 subnets into unique
100.64.<site>.0/24ranges. - Arx Private Access for app-by-app access: when client staff, vendors, or techs only need a specific internal app or port (web portal, RDP, SSH, or database) instead of the whole LAN, publish just that app with device checks and zero open inbound ports.
- One console, many tenants: manage each client as its own organization with separate users, policies and logs.
- Web filtering, 1-click AI proxy packs and AI Agent Gateway for client staff in the same app, so you can sell a security service, not just access.
- Transparent pricing: Business Team from $10/user/mo (5-user minimum) with 5 branch connectors included, or Enterprise Hybrid ($20/user/mo, 25+ seats) with 25 branch/VPC connectors.