Deploy new nodes. Or reuse existing resources.
Choose hosted Gateways and Connectors, or connect existing servers and SOCKS5 proxies to your team network.
View deployment optionsChoose your ingress, egress, and region independently.
Choose a region,
then deploy ingress and egress.
Gateway and Connector can be deployed in globally available regions and AXVIA’s data centers in Hong Kong, Tokyo, Singapore, the United States and elsewhere.
After you select a region and resource specifications, AXVIA deploys the node, installs the Agent and manages connection services. AXVIA-hosted and AXVIA-owned nodes are connected by dedicated lines.
Learn about Gateway deployment →Existing resources, keep using them.
A server becomes an ingress or egress; an existing proxy joins as the team’s separate SOCKS5 resource.
BYOG · Bring your own ingress
Connect an existing server as a Gateway so that employee devices and branch sites connect to your ingress, and manage access and source admission from the same console.
Learn about bring-your-own Gateway →BYOC · Bring your own egress
Connect an existing server as a Connector to serve as the final egress for your business services. When a double hop is required, it can also be switched to a dedicated relay node; choose each of the two purposes separately.
Learn about bring-your-own Connector →BYOP · Bring your own proxy
Enter the SOCKS5 address, port, and authentication details to keep using your existing proxy. No Agent installation is required, and you do not need to provide root SSH credentials.
Learn about bring-your-own Cloud Pulse →Choose your resources, and your maintenance approach.
| Choose content | Hosted nodes | BYOG / BYOC | BYOP |
|---|---|---|---|
| Resource source | AXVIA-hosted resources or AXVIA-owned infrastructure | Your existing servers; currently supports RFCHOST and KFCHOST | Your existing SOCKS5 proxy |
| Access information | Deployment region, resource specifications and billing period | Dedicated public IPv4, SSH port, and root account and password for direct login | Proxy address, port, authentication method and actual UDP capability |
| Agent and firmware | AXVIA installs, upgrades and manages the Agent and connection services | Checks the Linux environment, CPU architecture and dependencies, then installs and maintains node firmware | No Agent installation; connection information is stored and the associated node detects the proxy |
| Network and routine maintenance | Dedicated lines connect AXVIA-hosted and AXVIA-owned nodes | You maintain the server operating system, provider network and SSH credentials; AXVIA manages the Agent and service configuration | You maintain the proxy service, authentication credentials, quota and provider network |
Frequently asked questions.
Do bring-your-own nodes also use AXVIA dedicated lines?
Dedicated lines connect AXVIA-hosted and AXVIA-owned nodes. BYOG and BYOC use the server and network you provide; connection capacity depends on the customer’s provider and network conditions.
What is the difference between BYOG and BYOC?
BYOG connects a server as a Gateway for device ingress. BYOC connects it as a Connector for final egress or transit-only use. A transit-only node just forwards traffic and cannot simultaneously serve as a final egress.
Who maintains a BYOP proxy, and will it be used by other customers?
BYOP is available only to the current team and does not enter public inventory. You maintain the proxy service, authentication credentials, quota, and network; update the resource when connection information changes, and review the detection results of associated nodes.