Your servers. Your team's entry point.
Keep your existing server provider and location. AXVIA installs and manages the Agent and ingress services; device access is managed in the same console.
Learn about bring your own ingressUse your existing server for ingress.
Choose the egress region separately.
Connect your devices, and manage them as usual.
Once the bring your own Gateway is ready, select a Connector to establish a Relay, generating separate connection profiles for employee devices and branches.
From your current network, request admission.
Employees authenticate on the device that needs access, and the Gateway identifies the current public IPv4, managing approval and expiry status for each source.
Let ingress route by service.
Use firmware that supports traffic routing and enable the corresponding mode, then publish domain and IPv4 policies on the Gateway to select an egress for the relevant traffic.
Each device, managed separately.
Name each terminal profile separately, and view connection status and traffic. When a device is deactivated, revoke the corresponding profile; other separate profiles continue to work.
Installation and upgrades,
handled by AXVIA.
After you submit the server information, the task verifies SSH access, installs and validates the Gateway firmware, then waits for the first health report. You can leave the page while the task continues running.
If installation fails, start diagnostics and recovery from the original task, reusing the saved access information. Installation and subsequent updates use the selected firmware download source, which can also be changed in the node details.
AXVIA installs, upgrades and maintains the Agent and service configuration. You are responsible for the server operating system, the provider network and SSH credentials; the capacity of your own node depends on the network you provide.
Before connecting, confirm the requirements.
Supported providers
Currently supports servers from RFCHOST and KFCHOST.
network and SSH
A dedicated public IPv4 address, an SSH port, and a root account and password that can be used to log in directly.
System environment
The installation task checks the Linux environment, CPU architecture and required dependencies, then installs the node firmware.
Frequently asked questions.
Can IPv6, NAT VPS or shared-port servers be connected?
BYOG currently requires a dedicated public IPv4 address and directly accessible root SSH login. IPv6, NAT VPS and shared-port servers cannot use this connection method.
If I remove BYOG, will my server be deleted?
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.
How are SSH credentials used?
SSH credentials are stored encrypted and used for Gateway installation, repair, upgrades and credential rotation. We recommend separate operational credentials for platform maintenance and keeping SSH access to the server available.