Shared Compute - General Compute
$5.00/mo
1 vCPU · 1 GB · 20 GB
Choose location
Ashburn, United States
| Provider | Plan | vCPU | RAM | Disk | Regions | Billing | Price |
|---|---|---|---|---|---|---|---|
| Enzonix | Shared Compute - General Compute | 1 | 1 GB | 20 GB | Ashburn, United States | Fixed price | $5.00/mo |
| Enzonix | Shared Compute - General Compute | 1 | 1 GB | 20 GB | Amsterdam, Netherlands | Fixed price | $5.00/mo |
| Enzonix | Shared Compute - General Compute | 2 | 4 GB | 80 GB | Amsterdam, Netherlands | Fixed price | $9.00/mo |
| Enzonix | Shared Compute - General Compute | 2 | 4 GB | 80 GB | Ashburn, United States | Fixed price | $9.00/mo |
| Enzonix | Shared Compute - General Compute | 4 | 8 GB | 160 GB | Amsterdam, Netherlands | Fixed price | $16.00/mo |
| Enzonix | Shared Compute - General Compute | 4 | 8 GB | 160 GB | Ashburn, United States | Fixed price | $16.00/mo |
| Enzonix | Shared Compute - General Compute | 8 | 16 GB | 320 GB | Amsterdam, Netherlands | Fixed price | $32.00/mo |
| Enzonix | Shared Compute - General Compute | 8 | 16 GB | 320 GB | Ashburn, United States | Fixed price | $32.00/mo |
| Enzonix | Shared Compute - General Compute | 1 | 1 GB | 20 GB | Ashburn, United States | Hourly | $0.007/hr |
| Enzonix | Shared Compute - General Compute | 1 | 2 GB | 40 GB | Ashburn, United States | Hourly | $0.01/hr |
| Enzonix | Shared Compute - General Compute | 2 | 4 GB | 80 GB | Ashburn, United States | Hourly | $0.015/hr |
X-UI Instant App
X-UI is the Alireza0 panel for an Xray-core server. Compare live prices, CPU, memory, disk, and regions, deploy the panel with a client link already written, and connect a phone or laptop with v2rayNG, Hiddify, or Happ.
X-UI
Instant App on marketplace VPS
Live marketplace offers
Choose billing and size, compare providers side by side, pick a location, then launch.
1 provider
X-UI is the web panel, and Xray-core on the same VPS is what accepts connections and forwards traffic. From the panel you add VLESS, VMess, Trojan, Shadowsocks, or Hysteria inbounds, then share a QR code or export URLs. This Instant App creates one VLESS TCP inbound and a client link for you, with no form fields at create time. Use it instead of paying for a commercial Xray panel or a retail VPN subscription.

The panel shows whether Xray is running, along with CPU, memory, and throughput. Stop, restart, logs, and the Xray config are on the same screen.

Each inbound is a protocol, a port, and a transport. This Instant App creates one VLESS TCP inbound on port 8443, named noderings-default, with TLS off. Add another inbound in this list when the first one is not enough.

Expand an inbound to see its clients. Clients have a label, a traffic cap, and an expiry. The first client label is noderings, and its link is in the credentials file. Add another client when a second phone should have its own quota.

From the client row, open the QR code, or use Export All URLs on the inbound to copy the VLESS link. For the first client, the same link is the alixui_client_link line in the credentials file.
Xray-core
X-UI stores clients, inbounds, and traffic. Xray-core is the process that listens for VLESS and the other protocols you enable, then forwards that traffic. The overview reports Xray as running or stopped. A panel login with no imported client leaves the phone on its normal connection.
After the VPS is up, sign in, change the panel password, and check that the ready inbound is the one you want to hand out.
01
In a browser, open http:// and the IPv4 from your order. You should see the X-UI login.
02
SSH in as root with the create-flow password or key. The file lists the panel user, the panel password, and the first VLESS link. The alixui_core line says xray-core.
cat /root/.noderings_password03
Use alixui_admin_user and alixui_admin_pass from that file. Change the password in Panel Settings before you leave the login on the public internet.
04
TCP 22 is SSH. TCP 80 is the panel. TCP 8443 is the ready VLESS inbound Xray-core is listening on. The container uses the host network, so those ports are on the VPS itself.
05
Remark noderings-default, protocol VLESS, transport TCP, port 8443, TLS off. That link exists so a phone can connect on first boot. On a filtered network, add a TLS or REALITY inbound in the panel and give clients that link. Plain VLESS is easy for a network to recognize.
A user is a client on an inbound. The Instant App creates the first one. You create the rest in the panel.
01
In the panel, go to Inbounds. Expand noderings-default, or create a new inbound when you want a different protocol or port.
02
Use Add Client on that inbound. VLESS clients get a UUID. The email field is a label (the first one is noderings). You can set a traffic cap and an expiry.
03
From the client row, open the QR code. From the inbound menu, use Export All URLs to copy every share link. For the first client, the same link is the alixui_client_link line in the credentials file.
04
Importing one link on a phone and a laptop counts as one client. Add a separate client when you want a separate quota or a clean revoke.
05
Disable or delete that client in the panel and save. The panel updates Xray-core. The old link stops working after the reload.
You import a VLESS link, a QR code of that link, or an exported URL list. Then you turn the tunnel on in the client app.
01
Android: v2rayNG or Hiddify. iOS: Hiddify, Streisand, Happ, or Shadowrocket. Windows: v2rayN, Happ, or Hiddify. macOS and Linux: Hiddify, Happ, or Clash Verge Rev with a Clash subscription.
02
Paste the VLESS link, scan the QR from the panel, or import the exported URLs. The first link is alixui_client_link in the credentials file.
03
Select that profile and turn the tunnel on. Allow the VPN permission the phone asks for.
04
Open a page that shows your public IP and compare it with the VPS address. In the panel, the client should show as online. If the IP did not change, the tunnel is not carrying traffic.
05
Confirm TCP 8443 is open and the link host is the VPS IP, not 127.0.0.1. A TCP inbound will not connect if the client is set to UDP. After you switch an inbound to REALITY, a phone with the wrong clock often fails the handshake. Set the phone time to automatic and try again.
These apps run on the phone or computer. They are not Instant Apps. Import a link from this server, and pick an app that speaks the protocol of the inbound you are using. The ready inbound is VLESS over TCP.
Android. Scan the QR or paste the VLESS link.
Android client built on sing-box. Imports the same VLESS link.
The Hiddify app, separate from Hiddify Manager. Imports a link or a subscription.
iOS, and macOS on Apple silicon. Imports the VLESS link.
Phone and desktop builds. Imports the VLESS link or a subscription.
Paid iOS app. Imports the VLESS link.
Windows client from the v2rayN project. Paste the VLESS link or add a subscription.
Android uses Clash Meta for Android. Desktop uses Clash Verge Rev. Import a Clash subscription when the panel provides one.
A VPS in a region you pick is an exit for traffic you send through Xray-core. On a filtered ISP, the result depends on the inbound, the client, and what that network blocks. The ready inbound is plain VLESS over TCP, with no TLS.
| Situation | Fit | What to expect |
|---|---|---|
| Everyday privacy exit | Depends on the network | Useful when you want traffic from a phone to leave through a VPS you picked. The hosting provider can see that server. The exit address is yours. |
| Filtered networks in Iran | Often used | A common classic panel when a mobile ISP blocks ordinary VPN apps. Operators usually replace plain VLESS TCP with REALITY or Hysteria. Test it on your own line. Prefer S-UI or 3X-UI unless you specifically want this Alireza0 X-UI line. |
| China (GFW) | Depends on the network | People test REALITY, Hysteria, and similar inbounds. Plain VLESS TCP is a weak start there. Verify on the network you actually use. |
| Russia and other filtered ISPs | Depends on the network | Sometimes chosen when a network filters WireGuard or OpenVPN. The protocol still has to pass that ISP. |
| OpenVPN-only or office VPN profiles | Poor match | OpenVPN Connect will not import a VLESS link. This Instant App creates a VLESS inbound. |
Compare live X-UI VPS plans from independent providers, then run the Alireza0 panel and Xray-core on the offer you pick. Use it instead of paying for a commercial Xray panel or a retail VPN subscription.
See live prices, regions, and plan sizes before you buy. Shop self-hosted Xray panel hosts across independent providers.
Deploy X-UI and the VPS comes up with the panel, Xray-core, a VLESS inbound, and a client link. You still get root SSH.
The provider region is the geography of the VPS address clients will use. That choice is separate from whether a filtered ISP lets the tunnel connect.
The panel password and the first client link are written on the server. You change the password, revoke clients, and decide which inbound stays open.
Most X-UI VPS pages sell one company's servers. NodeRings lists Compute Instance plans from independent providers so you can compare self-hosted Xray offers by price, size, and region, then launch on the one that fits.
X-UI Instant App prepares the panel and Xray-core on the provider VPS you selected. The provider operates that machine. NodeRings lists the plan and deploys the Instant App.
Compare plans, pick a provider offer, and launch X-UI on that server.
01
Pick a provider offer. A sensible start is 1 vCPU, 2 GB RAM, and 20 GB disk. Smaller and larger plans stay on the list.
02
Launch the Instant App on that plan. The panel and Xray-core come up together. There are no extra form fields.
03
Read the VLESS link from the server, import it in v2rayNG, Hiddify, Happ, or another app below, and confirm the tunnel from the phone.
NodeRings Instant App brings X-UI and Xray-core up with Docker Compose on the host network. The panel listens on port 80. A VLESS inbound listens on port 8443. The admin password and the first client link are written for you.
Credentials are written on first boot to:
/root/.noderings_passwordRead them over SSH:
cat /root/.noderings_passwordCompose project directory
/opt/noderings/x-ui
/opt/noderings/x-ui/docker-compose.yml
/opt/noderings/x-ui/.envWorking directory for Compose, the stack file, and generated admin and client values.
Panel database
/opt/noderings/x-ui/dbX-UI data directory, mounted into the container. Inbounds and clients live here.
Certificate directory
/opt/noderings/x-ui/certPresent for panel certificates you add later. The first boot does not issue one.
Credentials file
/root/.noderings_passwordWritten on first boot. Includes the panel password and the first client link.
Boot unit
/etc/systemd/system/noderings-x-ui.serviceBrings Compose up after Docker is ready.
One Compose service, x-ui, runs the panel and Xray-core on the host network. Port 80 is the panel. Port 8443 is the ready VLESS inbound. The container is allowed to manage network interfaces so Xray-core can forward traffic.
x-uiWeb panel and Xray-core on the host network.
Container status
cd /opt/noderings/x-ui && docker compose psLive logs
cd /opt/noderings/x-ui && docker compose logs -fRestart containers
cd /opt/noderings/x-ui && docker compose restartsystemd unit status
systemctl status noderings-x-uiYour X-UI panel starts on http://. Cloudflare can give the panel a padlock without installing a certificate on the VPS. This covers the website on ports 80 and 443. It does not carry the VLESS inbound.
Add your domain
Sign up at Cloudflare and add the domain you want to use for the panel.
Point it at your VPS
Create an A record to your server IP and leave the orange cloud on.
Open the https panel
Visit https://your-domain and sign in with the panel password. Keep the VLESS client link pointed at the raw VPS IP and port 8443. Cloudflare's proxy does not forward that raw TCP inbound.
Only allow Cloudflare to the panel
Optional. With SSH (port 22) allowed, open Cloudflare to ports 80 and 443 for the panel, and leave TCP 8443 open so clients can still reach Xray-core:
curl -s https://www.cloudflare.com/ips-v4 | while read ip; do sudo ufw allow from "$ip" to any port 80,443 proto tcp; done
sudo ufw allow 22/tcp
sudo ufw allow 8443/tcpThat is enough for a first secure visit to the panel. You can tighten SSL in Cloudflare later if you need it. Keep port 22 allowed for SSH. Keep TCP 8443 allowed for the ready inbound, or the phone will not connect.
Xray-core and the panel are light on disk. CPU and bandwidth matter more once several clients are connected, especially with REALITY or Hysteria. These rows are starting points, not a filter on the plans above.
| Workload | Illustrative starting point | Note |
|---|---|---|
| One or two phones | 1 vCPU, 2 GB RAM, 20 GB disk | Matches the Instant App floor. Enough for the panel and a personal VLESS inbound. |
| A household or a small team | 2 vCPU, 4 GB RAM, 40 GB disk | More headroom when several clients are online and you add a second inbound. |
| Many subscription users | 4 vCPU, 8 GB RAM, 40 GB disk | CPU and the provider's bandwidth cap show up before disk does. |
Illustrative only. Live plans are not filtered by this table. A filtered network can still block a tunnel that fits on a small VPS.
You get root on a provider VPS. NodeRings lists the plan and deploys X-UI. The provider runs the machine.
Panel password, which inbounds exist, who receives a client link, the host firewall, and the provider's terms. The ready inbound is plain VLESS. Change it if that is not what you want on the public internet.
The VPS, the network, and the exit IP. Abuse on a public proxy port can get that provider to suspend the server.
The marketplace and the Instant App that deploys X-UI with Xray-core. NodeRings does not run a VPN service and does not see client traffic.
v2rayNG and NekoBox on Android. Hiddify and Happ on Android, iOS, Windows, macOS, and Linux. Streisand on iOS and macOS. Shadowrocket on iOS. v2rayN on Windows. Clash Meta for Android, and Clash Verge Rev on Windows, macOS, and Linux, when you import a Clash subscription. The app has to speak the protocol of the inbound. OpenVPN Connect will not import a VLESS link.
People commonly run X-UI and Xray-core when an ISP filters ordinary VPN apps. A line connects when the inbound, the client, and that ISP still match. The ready inbound is VLESS over TCP with no TLS, and many filtered networks block it. Add REALITY or Hysteria in the panel if you need a different inbound. Expect to test on your own connection.
In the panel, add another client on the inbound, or import the same link on a second device. One shared link counts as one client. To stop a device, disable or delete that client and save.
You rent a VPS and run Xray-core yourself. You choose the region, the inbound, and who gets a client link. The VPS provider can see the server. NodeRings lists plans and deploys the Instant App.
TCP 22 for SSH, TCP 80 for the panel, and TCP 8443 for the ready VLESS inbound. If you add inbounds on other ports, open those too. Hysteria inbounds you create later also need their UDP ports.
NodeRings lists provider plans and deploys the Instant App onto the plan you pick. The provider operates the VPS. You operate X-UI and Xray-core.
A VLESS URL for the inbound on port 8443, stored as alixui_client_link. Import it to test that the phone can reach Xray-core. For a network that filters plain proxies, create a TLS or REALITY inbound in the panel and hand out that link instead.
This Instant App is Alireza0 X-UI with Xray-core. 3X-UI is the Sanaei panel, also with Xray-core. S-UI is the Alireza0 panel with sing-box. Prefer S-UI or 3X-UI unless you specifically want classic X-UI.
3X-UI Instant App
The Sanaei panel with Xray-core on the same VPS. A more active Xray-panel fork for many buyers.
S-UI Instant App
The Alireza panel with sing-box on the same VPS. Same kind of client links, a different core.
Libertea Instant App
All-in-one multi-protocol panel with Xray providers, Shadowsocks, and CDN camouflage routes.
TX-UI Instant App
3X-UI fork with AmneziaWG 3.1, MTProto FakeTLS, and Iran routing helpers.
All Instant Apps
Browse every Instant App landing on Compute Instance.
Compute Instance
Live VPS plans from independent providers.