rdMesh

A site behind a firewall that only allows outbound connections cannot be reached: someone travels, or negotiates an opening with the client's IT. And you learn a station is down when the operator calls.

rdMesh establishes a peer-to-peer network between the stations of one portfolio. Each station knows the state of the others, and a request can cross the mesh to reach a remote station — including one sitting behind a firewall that only allows outbound connections: the remote station itself opens and maintains the link. The portfolio's other uses (remote access, settings, charts) rely on this same path.

• A portfolio that sees itself: presence, latency and version of every station, from any of them.
• The firewall stops being a wall: no inbound opening to request from the client's IT.
• A station with no direct link is reached through another, without you needing to know the topology.
• Trust is withdrawn without a site visit: cutting access does not require travel.
• The topology is readable in Workbench, like the rest of the station.

• Supervising a multi-site portfolio without a dedicated VPN.
• Onboarding a constrained site without a network exemption.
• Displaying remote data as if it were local.
• Removing a site from the portfolio without travelling.

Niagara ≥ 4.13.x

0.73.4

on request

Reach the portfolio

See the rangerdTunnelCore