Your server. The egress for your services.
Keep the region and network of your server from RFCHOST or KFCHOST, and connect to the team’s Gateway. AXVIA manages the Agent and egress services.
Learn about egress usesYour server stays with its existing provider.
Manage the egress with your team’s connections.
From your server, access your services.
Devices connect to a Gateway and reach your own Connector through Relay, then access the public internet from this server.
As the final egress, the Connector handles public internet access and target access auditing. Once the relevant firmware has the capability and passes egress verification, it can also be configured to forward traffic from supported terminals to Cloud Pulse.
Target access, viewed by egress.
View the target domain or IP, protocol, port, and upstream/downstream traffic to see which services the connection accessed.
Specific services, a different egress.
Use firmware that supports traffic routing and enable Connector routing mode to select, by domain or IPv4, either a direct local connection or the next-hop Connector with an established link.
Need transit? Build a two-hop path.
Switch your own Connector to relay-only mode, then pair it with another final Connector to form a double-hop Relay.
A stop in between, dedicated to forwarding.
Your own Connector can also act as a relay, handing the Gateway's traffic over to another final Connector.
A relay-only node forwards only to the next tunnel segment and does not handle public internet NAT, Cloud Pulse egress, or access auditing. Those responsibilities belong to the final Connector.
Before connecting, confirm the requirements.
Supported providers
Currently supports servers from RFCHOST and KFCHOST.
network and SSH
A dedicated public IPv4 address, SSH port, and a root account with password for direct login.
System environment
Before installation, verify the Linux environment, CPU architecture, and required dependencies.
AXVIA verifies SSH, installs and validates the firmware, then waits for the first health report. If installation fails, diagnose and recover from the original task. Installation and updates use the selected firmware download source.
Maintenance, shared responsibilities.
AXVIA manages the Agent and egress service configuration. You maintain the server operating system, SSH credentials, and provider network.
BYOC connection capacity depends on the customer’s server and network. Dedicated lines connect AXVIA-hosted and AXVIA-owned nodes; customer-provided nodes use the network you supply.
Frequently asked questions.
Can the final egress and relay roles be switched directly?
Before switching, first remove the Relay associated with this Connector. A relay-only node cannot serve simultaneously as the final egress; only after restoring its standard use can you select it to handle public-network egress again.
Once the firmware installation is complete, can I start connecting right away?
The installation task must still wait for the first heartbeat report. Once the node is confirmed ready, select it to establish a Relay, then import and activate the connection configuration on the device.
Will removing BYOC delete the server?
No. Remove associated Relays first, then remove the node from AXVIA. The platform revokes the Agent credentials and ends management; the customer’s server is retained and is neither deleted nor reinstalled.