Integration Scenarios:

Remote Binding, TLS, and Network ACLs

Non-loopback binding should ONLY be considered if the customer platform cannot utilize SSH tunneling AND both the robot and platform reside within the same trusted private LAN. During startup, the exact acknowledgment variable REALBOT_ALLOW_REMOTE_BIND=I_ACKNOWLEDGE_PRIVATE_LAN_ONLY MUST be set simultaneously, and firewalls/ACLs MUST be configured to allow traffic exclusively from designated platform IP addresses.

The bridge itself does NOT perform TLS termination. Bearer tokens do not provide transport confidentiality over plain HTTP. Any deployment spanning untrusted networks, Wi-Fi, campus interconnects, VPN boundaries, or the public Internet MUST deploy an external TLS termination proxy in front of the bridge, validate server certificates, and configure network ACLs, rate limiting, and access auditing. This manual does NOT treat "having a Bearer token" as "ready for direct public Internet exposure."