Your existing proxies. Now serving as the team egress.
Connect an existing SOCKS5 service as Cloud Pulse, keeping its provider and network. No Agent installation or new server deployment is needed.
Learn about BYOPNo need to redeploy a server.
Keep your existing proxy and network.
Keep your egress, connect new links.
If your work devices already use Relay, they can also keep using the proxy you select. The final Connector then hands the relevant public traffic to this SOCKS5 service.
One device keeps its original proxy.
A standard Relay’s WireGuard and RouterOS configurations can select a customer-provided Cloud Pulse. The relevant nodes must support endpoint egress binding and pass the associated Connector’s checks.
Selected services, routed to this egress.
Choose your own proxy in a client routing policy that supports Cloud Pulse. Matching traffic travels through Relay to the final Connector, then is forwarded to the SOCKS5 egress.
Target access, viewed in resource details.
Once traffic is generated, view the targets, protocols, ports, traffic, and most recent access time aggregated by Connector.
Protocol support
comes from the proxy itself.
After connecting, complete egress verification and review the check results for the associated Connector. For services that require UDP, the proxy must actually support SOCKS5 UDP forwarding; selecting "Supports UDP" will not enable the feature on the proxy's behalf.
If a proxy bound to a standalone terminal is unavailable or lacks the required UDP capability, the relevant public access will be blocked and will not automatically fall back to a direct connection.
Address and port
Enter the SOCKS5 server IP or domain name, and the service port.
Authentication information
Choose no authentication, or enter a username and password. After updating the connection information, run the check again.
Actual protocol capabilities
Record UDP support according to the proxy's existing capabilities, and confirm that the associated node can connect to the proxy.
Your team's own resources. Maintained by you.
AXVIA stores the proxy connection information, and the associated node checks and uses the egress. The proxy service, authentication credentials, service quota and provider network are maintained by you.
Service expiry or credential changes will affect connections that use it. After updating the resource, review the check results; if you need to change the terminal egress, explicitly select another verified Cloud Pulse, or clear the binding and restore the Connector's direct connection.
Frequently asked questions.
Do I need SSH access to the server or to install an Agent?
No. BYOP uses the connection details of an existing SOCKS5 service and does not install Connector firmware. Use BYOC when you want to connect the entire server and have AXVIA manage its Connector Agent.
If I select UDP support, does that mean UDP will be forwarded?
This option records the proxy's existing capabilities. The proxy service itself must provide SOCKS5 UDP and pass an actual connection check. A proxy that supports only TCP cannot handle UDP requests.
Will my proxy be offered to other customers?
No. BYOG Cloud Pulse is available only to the current team and does not enter the platform's public inventory. The proxy, credentials, quota and network remain maintained by you.