Keep employees and branches on their existing connections. Access business services from the region you choose using Gateway and Relay; you can also connect to your existing servers with BYOC.
Choose an egress in a globally available region. AXVIA creates the cloud server, installs the Agent and manages egress services.
Global deployment regions
21
Availability Zone
56
ChengduCN
Mainland China
Availability Zone
2
View all availability zones+
Beijing6 availability zones
Beijing Zone 3, Beijing Zone 4*, Beijing Zone 5*, Beijing Zone 6, Beijing Zone 7, Beijing Zone 8
Shanghai7 availability zones
Shanghai Zone 2, Shanghai Zone 3*, Shanghai Zone 4*, Shanghai Zone 5, Shanghai Zone 8, Shanghai Zone 9*, Shanghai Zone 10*
Nanjing3 availability zones
Nanjing Zone 1, Nanjing Zone 2*, Nanjing Zone 3
Guangzhou5 availability zones
Guangzhou Zone 3*, Guangzhou Zone 4*, Guangzhou Zone 5, Guangzhou Zone 6, Guangzhou Zone 7
Chengdu2 availability zones
Chengdu Zone 1, Chengdu Zone 2*
Chongqing1 availability zone
Chongqing Zone 1
Zhongwei1 availability zone
Zhongwei Zone 1*
Hong Kong3 availability zones
Hong Kong Zone 1*, Hong Kong Zone 2, Hong Kong Zone 3
Singapore4 availability zones
Singapore Zone 1, Singapore Zone 2, Singapore Zone 3*, Singapore Zone 4*
Johor Bahru2 availability zones
Johor Bahru Zone 1, Johor Bahru Zone 2
Jakarta3 availability zones
Jakarta Zone 1, Jakarta Zone 2, Jakarta Zone 3*
Seoul2 availability zones
Seoul Zone 1, Seoul Zone 2
Tokyo2 availability zones
Tokyo Zone 1, Tokyo Zone 2
Osaka1 availability zone
Osaka Zone 1
Bangkok3 availability zones
Bangkok Zone 1, Bangkok Zone 2, Bangkok Zone 3*
Riyadh2 availability zones
Riyadh Zone 1, Riyadh Zone 2
São Paulo1 availability zone
São Paulo Zone 1
Querétaro1 availability zone
Querétaro Zone 1*
Silicon Valley2 availability zones
Silicon Valley Zone 1, Silicon Valley Zone 2
Virginia2 availability zones
Virginia Zone 1, Virginia Zone 2
Frankfurt3 availability zones
Frankfurt Zone 1, Frankfurt Zone 2, Frankfurt Zone 3
Availability zones marked with * require an application to be enabled.
AXVIA's own infrastructure.
Connector can also be deployed in AXVIA’s data centers in Hong Kong, Tokyo, Singapore, the United States and elsewhere. Dedicated lines connect AXVIA-hosted and AXVIA-owned nodes.
Specific services,a different egress.
Based on domain and IPv4 rules, hand the designated services to the next-hop Connector, while other services can still be accessed from the current node.
Connector
First select the next Connector, establish a node link, then use it in traffic routing rules. After publishing the policy, check whether the node has applied it; devices continue to use their original access configuration.
Choose Cloud Pulse for a specific WireGuard or RouterOS configuration. The final Connector accesses the public internet through the selected proxy; other devices retain their own egress settings.
Connector
The firmware at both ends must support independent configuration binding, and the proxy can only be used after passing the check. For services that require UDP, choose a proxy with UDP capability; existing tunnels and already configured intranet connectivity continue to be used.
The final Connector aggregates destination domains or IPs, ports, protocols, upload and download traffic, and connection counts. Find the main destinations by traffic volume and review service access by time.
Online lookup of recent records
30days
Longest single archived query
7days
Destination access audits and Gateway billable usage are counted separately.
Connect an existing server through BYOC, keeping its provider, region and network. AXVIA installs and manages the Agent and egress services; you maintain the server operating system, SSH credentials and provider network.
Currently supports RFCHOST and KFCHOST.
A directly reachable public IPv4 address, plus root SSH password and port.
Before installation, verify Linux, the CPU architecture, and runtime dependencies.
Customer-provided nodes use your network; connection capacity depends on the server and provider network.
What is the difference between a relay Connector and a final egress?+
In a two-hop Relay, the transit-only Connector forwards traffic only to the next tunnel segment. The final Connector handles public internet egress, Cloud Pulse forwarding and access auditing. Remove associated Relays before changing the node’s purpose; the two purposes cannot be used simultaneously.
If the bound Cloud Pulse becomes unavailable, will direct connection be restored automatically?+
No. If the proxy is unavailable or lacks the required UDP capability, the related public access is blocked. Explicitly switch to a verified egress, or clear the binding and choose a direct Connector; then wait for the node to confirm the change before verifying access to your services.
Can an independent Cloud Pulse binding and node traffic routing be used together?+
The same endpoint configuration cannot use both bindings at once. To apply node policies by destination, first clear this configuration’s individual Cloud Pulse binding, then select a node routing policy.
