Ingress and egress. Each chosen for its purpose.
Gateway connects devices, Relay connects nodes, and the final Connector accesses your services. Choose Cloud Pulse when you need a separate SOCKS5 egress.
Understand how the components work togetherFour roles, combined into your connection.
Gateway
Device ingress. Connect employee computers and branch devices, choose the access region, and manage source admission and supported ingress traffic routing.
Learn about device ingress →Relay
Connections between nodes. Reuse existing ingress and egress, combining single-hop, dual-hop or dedicated port forwarding; no separate subscription.
Learn about connection methods →Connector
Business final egress. Access target services by region and view access logs; another Connector can also be dedicated to transit.
Learn about business egress →Cloud Pulse
Optional standalone SOCKS5 egress. Choose the proxy for supported device profiles or business rules; other devices keep their own egress settings.
Learn about independent egress →Keep using your existing resources.
BYOG · Bring your own ingress
Use the provider and location of your existing server, connect it as a Gateway, and manage device ingress from the same console.
Learn about BYOG →BYOC · Bring your own egress
Connect an existing server as a Connector, choose final egress or dedicated transit use, and plan business paths accordingly.
Learn about BYOC →BYOP · Bring your own proxy
Enter the SOCKS5 address, port, and authentication details to use it as a private Cloud Pulse for your team, with no Agent installation or SSH access required.
Learn about BYOP →BYOG and BYOC currently support RFCHOST and KFCHOST. They require a dedicated public IPv4 address and a root SSH account with a password that can log in directly. Installation checks the Linux environment, CPU architecture, and dependencies.
Traffic between AXVIA-hosted and AXVIA-owned nodes runs over dedicated lines. Customer-provided servers and proxies continue to use the customer’s provider network.