AXVIA
AXVIA is an enterprise network connectivity and management platform. Choose an ingress and an egress, connect your computer or branch router, then configure traffic routing and access permissions.
See how to get connectedGateway and Connector can be deployed in globally available regions and AXVIA’s data centers in Hong Kong, Tokyo, Singapore, the United States and elsewhere. Choose an ingress near your devices and a final egress suited to your services.
The ingress for employee computers and branches. Use a client subscription, or generate a supported standalone configuration for routers and firewalls.
Choose an access region →An existing connection between the ingress and the egress. Reuse node combinations for single-hop or dual-hop paths, without deploying a pair of servers for every connection.
Combine business connections →The final egress for business access to the public internet. Choose a region by service, then check destinations, protocols, and access traffic here.
Choose a public egress →An optional SOCKS5 egress. Change the egress for supported standalone device configurations; other devices keep their existing settings.
Learn about independent egress →AXVIA international network
International dedicated lines connect AXVIA-hosted and AXVIA-owned nodes across Hong Kong, Tokyo, Singapore, the United States, and Germany. Ingress sits close to employees, while egress is chosen by service.
Learn about RelayLatency 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.
Company business traffic goes through a designated Relay, while other destinations are connected directly or blocked. After the rules are published, employees refresh their original subscription to get the update.
Learn about client rules →Gateways connected directly or Connectors with traffic routing enforce domain and IPv4 policies. Administrators adjust egress centrally, while devices keep their original connection configuration.
Learn about node policies →Manage Passkeys, passwords, and two-factor authentication. The proxy ingress approves source IPv4 addresses, and configuration is revoked individually when a device is disabled.
Learn about access and identity →From the final egress, view target domains or IPs, protocols and traffic, trace access back by time, and query archived historical windows.
View target access audit →Trace member actions, Relay creation requests, node service entitlements and BYOP takeover history by permission.
View account activity audit →Find the node a device uses and view public network probes, Agent heartbeats, data-plane services and sampled traffic separately.
Learn about runtime observability →Connect your own AI tools via REST or MCP. You set the resources, permissions and quotas of independent Agents, with separate authorization for diagnosis, planning and execution.
Repairs require separately pre-authorized nodes and actions and must meet the maintenance conditions; they are currently used only for nodes without an active Relay. Task records retain the evidence, plan and health review results.
Learn about AI Use →Connect to Gateway via BYOG, keeping the ingress location and provider. AXVIA installs and manages the Agent and the ingress service.
Learn about bringing your own ingress →Connect a Connector via BYOC, retaining the original region and network, and choose its use as final egress or dedicated transit.
Learn about bringing your own egress →Connect SOCKS5 as a team-private Cloud Pulse, with no need to install an Agent on the proxy.
Learn about bringing your own proxy →BYOG and BYOC currently support RFCHOST and KFCHOST. A directly reachable dedicated public IPv4 address, a root SSH password and a port are required. Linux, CPU architecture and dependencies are checked before installation. Customer-provided servers and proxies use the customer’s network.
