AXVIA

Gateway

Global deployment. Nearby access.

Choose the nearest ingress for employee computers and branch routers. Deploy it in available regions worldwide and on AXVIA infrastructure, or use your existing servers through BYOG.

Global deployment regions
21
Availability Zone
56
View available regions
Mainland China
ChengduCHENGDU2 availability zones
Mainland China
ZhongweiZHONGWEI1 availability zone
Mainland China
ChongqingCHONGQING1 availability zone
Mainland China
GuangzhouGUANGZHOU5 availability zones
Mainland China
BeijingBEIJING6 availability zones
Mainland China
NanjingNANJING3 availability zones
Mainland China
ShanghaiSHANGHAI7 availability zones
Hong Kong, China
Hong KongHONGKONG3 availability zones
Singapore
SingaporeSINGAPORE4 availability zones
Malaysia
Johor BahruJOHORBAHRU2 availability zones
Indonesia
JakartaJAKARTA3 availability zones
South Korea
SeoulSEOUL2 availability zones
Japan
TokyoTOKYO2 availability zones
Japan
OsakaOSAKA1 availability zone
Thailand
BangkokBANGKOK3 availability zones
Saudi Arabia
RiyadhSAUDI-ARABIA2 availability zones
Brazil
São PauloSAOPAULO1 availability zone
Mexico
QuerétaroQUERETARO1 availability zone
United States
Silicon ValleySILICONVALLEY2 availability zones
United States
VirginiaASHBURN2 availability zones
Germany
FrankfurtFRANKFURT3 availability zones

Deploy the ingress nearby.
Choose the egress region with Connector.

Deployment options.

Use managed resources, or keep your own servers.

Available regions.

Deploy an ingress in any available region worldwide; AXVIA creates the cloud server and installs the service. Choose the region that best suits your team's location.

Global deployment regions
21
Availability Zone
56
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 Infrastructure

From ingress to egress,
connected by dedicated lines.

Multiple data centers in Hong Kong, Tokyo, Singapore, the United States and elsewhere support Gateway and Connector deployments. AXVIA-hosted and AXVIA-owned nodes are connected by dedicated lines.

Starting connection bandwidth
200Mbps
Maximum per single Relay
1000Mbps
10,000-packet test
0% packet loss
Lowest China–Hong Kong RTT
2–3ms
Lowest China–Japan RTT
28ms
Lowest China–Singapore RTT
30ms
Lowest China–US RTT
130ms or less

Latency is measured as the round-trip time (RTT) between nodes; packet loss results come from a 10,000-packet test, and line jitter is minimal. These figures apply to dedicated lines between AXVIA-hosted and AXVIA-owned nodes.

BYOG

Your existing servers.
Keep using them.

Connect your existing servers as Gateways. AXVIA installs and manages the Agent, and you keep using your own servers and network.

  • Supports RFCHOST and KFCHOST.
  • Directly connectable public IPv4 · root SSH password and port
  • Validates Linux, CPU architecture and runtime dependencies before onboarding.
Learn about BYOG

An employee's computer.
A branch router.

Generates subscription links for employees, and standalone configurations supported by each router and firewall.

Client subscription
Surge 6MihomoShadowrocket
Standalone configuration
WireGuardRouterOSFortiGate / IPsec
Learn about device access

Ingress management.

Manage the sources allowed to connect.

The client proxy ingress checks the source public IPv4. After a device authenticates via a link or QR code, it connects within the allowed range.

Every device, its own profile.

A separate configuration can set rate limits and intranet connectivity. If a device is deactivated or its configuration is leaked, that specific configuration can be revoked on its own.

Different services, different egress points.

Enable direct-connect Gateway mode to enforce domain, IPv4, and rule-set policies at the ingress.

Connect an ingress port to a specific service.

Set up a port forwarding Relay using dedicated firmware on both ends to map TCP / UDP ports to a specified terminal or internal service.

Frequently asked questions.

Is a Gateway's region the same as its public egress region?

The ingress of a standard Relay is at the Gateway, and the final egress is at the Connector. You can choose the ingress and egress regions separately, then connect them with a Relay.

Do self-hosted servers also use AXVIA dedicated lines?

Traffic between AXVIA-hosted and AXVIA-owned nodes runs over dedicated lines. BYOG nodes use the network you provide; their connection capacity depends on the customer’s servers and providers.

Do all devices require source IP approval through the web page?

Native WireGuard connects through a Peer key in a separate configuration. The AnyTLS and SOCKS5 proxy ingress used by clients has its own public IPv4 source admission.

Can a regular Gateway be switched directly to a port forwarding ingress?

Port forwarding requires dedicated firmware on both ends. Before changing the purpose, remove the associated Relay; switching is not possible while the version is locked, and connections may be interrupted during firmware installation.

Connect your
your first device.

Open console View the onboarding process