Cloud Pulse
Every device. Its own egress.
Choose a dedicated SOCKS5 egress for WireGuard and RouterOS devices. Static residential IPs, with Verizon, AT&T and T-Mobile available.
Learn about dedicated egress
If you already have a SOCKS5 proxy, you can also join the team egress through BYOP.
Work computers use Cloud Pulse. Test computers go direct.
Both devices use the same Relay. Select the verified Cloud Pulse for the work computer's terminal configuration; once the final Connector confirms the application, its public internet access uses the chosen proxy.
Test devices still access the public internet directly through the Connector. Terminals that are already configured for internal network connectivity continue to use their existing routing and access settings.
Learn about terminal egress settings →TCP and UDP,tested separately.
Test the proxy connection to see whether the egress supports the TCP or UDP that your business requires.
Every switch has an application status. Whether it has taken effect, is switching, or failed to be delivered, the console shows it directly.
Your existing proxy,
keep using it.
Provide the SOCKS5 address, port, and authentication details to connect. No Agent installation required.
The resource is available only to the current team. You continue to maintain the proxy service, quota, and provider network.
Learn about bringing your own Cloud Pulse →Choose per device. Or per service.
Give one configuration its own egress.
Bind Cloud Pulse to a standard Relay’s WireGuard or RouterOS configuration. The device keeps its original tunnel; no tunnel configuration needs to be imported again.
Send selected services through Cloud Pulse.
Traffic matching domains, IPv4 addresses or rule sets can be sent through Cloud Pulse; other traffic continues to follow the default policy.
Access records, viewed from the egress.
In Cloud Pulse details, view target records aggregated by Connector to learn about targets, protocols, ports, traffic, and the most recent access time.
Frequently asked questions.
Which terminals can have an independent Cloud Pulse egress?
Supports WireGuard and RouterOS configurations on standard Relays. Both the Gateway and final Connector must have firmware supporting configuration-level SOCKS5 binding. RouterOS uses the selected egress only for public internet traffic sent into this tunnel. An individual endpoint binding cannot be used together with a node routing policy; clear the individual binding before switching to a policy.
Does Cloud Pulse support UDP?
UDP capability depends on the selected proxy. For services that require UDP, you must select an egress that supports SOCKS5 UDP forwarding and check the actual detection results. Proxies that support only TCP cannot handle UDP requests; UDP traffic under a binding configuration will be blocked.
If the selected egress is unavailable, will it automatically switch to a direct connection?
No. The relevant public traffic under a binding configuration will be blocked. Only after you explicitly switch to a verified Cloud Pulse, or clear the binding and select a direct connection, and wait for the final Connector to confirm, will the new egress be used.