PathX Acceleration routes your cloud hosts' requests to international development resources — GitHub, AI model repositories, package registries — through NubexCloud's private backbone instead of the public internet. Configure once. Instant effect. No code changes.
Measured across NubexCloud cloud hosts accessing international development resources before and after enabling PathX Acceleration.
PathX works by redirecting DNS resolution on your cloud hosts through NubexCloud's optimised nameservers. No code changes, no proxy setup, no application modifications.
Choose the domains you need accelerated. You can add or remove domains at any time — changes take effect instantly. The instance fee scales with the number of domains.
Change the DNS servers on each cloud host to PathX's resolvers. Works on Linux (CentOS, Ubuntu, Debian, RedHat) and Windows Server. Takes effect immediately after restart.
Acceleration is active immediately. No application restart required. Your cloud host now resolves and routes all configured domains through the PathX backbone.
International resource access from NubexCloud VMs in the UAE and GCC region is heavily affected by public internet routing congestion. PathX eliminates that bottleneck entirely.
AI model training pipelines, CI/CD builds, and development environments all stop when international resource access is slow. PathX eliminates that bottleneck.
As your project evolves, the acceleration domains you need change. Add new domains and remove unused ones from the console without restarting anything. Changes take effect immediately.
The backbone path between NubexCloud's UAE region and major international destinations is shorter, less congested, and more reliable than public internet routing. Results are consistent, not luck.
No proxy software to install. No application code to modify. No VPN clients. Change two lines of DNS configuration on your cloud hosts and acceleration is active — for every tool that makes DNS requests.
Prices below are approximate USD conversions from CNY billing. Exact pricing visible in the console at current exchange rates.
Traffic is measured in MB from accelerated domain requests made through the PathX backbone. Only traffic on configured and accelerated domains is charged — other internet traffic from your cloud hosts is not affected or billed.
Slow access to international development resources is one of the most underestimated productivity bottlenecks for teams building on cloud infrastructure in the MENA region.
AI model files are enormous — 7B parameter models are 14–28 GB, 70B models exceed 100 GB. Without PathX, a 10 GB model download takes over two hours at 1.2 MB/s. With PathX at 92 MB/s, the same download takes 110 seconds. For teams running multiple experiments per day, this compounds into hours of saved waiting time every week.
Development teams on NubexCloud VMs that rely on public code repositories face slow git operations, slow package downloads, and occasional timeouts that break CI/CD pipelines. PathX stabilises and accelerates all repository operations — git clone, pull, push, package installs — without any application changes.
AI image generation workflows require frequent downloads of model weights, LoRA adapters, and style packs from international creative AI repositories. Each slow download compounds — a pipeline that downloads 10 different model components over a slow connection becomes completely impractical. PathX turns hours of downloads into minutes, making iterative creative AI workflows on NubexCloud cloud hosts practical.
We run a Stable Diffusion image generation cluster on NubexCloud VMs. Downloading model packs used to be the biggest blocker — a new model set could take 4–6 hours. After enabling PathX Acceleration, the same downloads finish in under 8 minutes. Our team can iterate on models multiple times per day instead of once per week.
Our CI/CD pipeline pulls dependencies from public package registries on every build. Before PathX, builds would occasionally timeout and fail mid-pipeline because of slow or dropped connections to package servers. Since configuring the DNS on our build VMs, we haven't had a single network-related build failure. The setup took literally 5 minutes.
We train LLM variants and need to pull multi-GB checkpoint files regularly. With 280ms+ latency and 1 MB/s to international model repos, we were basically stuck. PathX cut our download time for a 30 GB checkpoint from over 8 hours to about 6 minutes. Our researchers stopped wasting time waiting and started actually experimenting.
Change two DNS lines on your cloud hosts. Configure your domains in the console. That's it — acceleration is active immediately, for every tool and pipeline that uses DNS.