Understanding Secure Remote Connections: Mervis Proxy vs. Mervis CloudAccess

Connecting to your remote PLCs and facility networks shouldn't require exposing your hardware to the public internet. At Energocentrum plus, we offer two distinct, secure methods for bridging the gap between your edge devices and your centralized management stations: the Mervis Proxy Service and Mervis CloudAccess. Both eliminate the need for public IP addresses, but they serve different architectural needs.

Mervis Proxy vs CloudAccess Architecture Diagram

Mervis Proxy Service (The Lightweight Tunnel)

The Mervis Proxy is our streamlined, single-purpose infrastructure. When a Mervis PLC initiates a tunnel request, it establishes a direct SSCP (SoftPLC) tunnel through our Proxy Server straight to your Remote Engineering (IDE) station or SCADA/HMI environment.

  • Best For: Standard, everyday Mervis telemetry and IDE programming.
  • Architecture: Lightweight and highly optimized for single-protocol (SSCP) data streams.

Mervis CloudAccess (The Flexible Stream)

For more complex networking needs, Mervis CloudAccess provides a heavyweight, generic, and highly flexible architecture. Instead of just a single-protocol tunnel, the PLC initiates a secure TCP/WebSockets data stream to the CloudAccess Node. This allows you to tunnel multiple types of flexible protocols simultaneously.

  • Best For: Advanced remote management, including SSH access or securely bridging web access to third-party devices on the local network.
  • Architecture: Flexible stream capable of routing data to IDEs, SCADA interfaces, and Mobile Web HMIs concurrently.

Helpful Links & Resources