We've got a new update. We now offer our own Web Console. Open the console and type ssh root@your-server-ip to reach any server you own, right from your browser. No SSH app needed.
The Avalanche docs ask for 8 vCPUs, 16 GiB of RAM and 1 TiB of SSD. A VPS with those specs is $30 a month; a dedicated server with more headroom is $82. Pay in Bitcoin, Monero, Ethereum or USDT.
Prices are for Romania on a one-month term; a 12-month term takes 50% off.
or $15/mo on a 12-month term (−50%)
Meets the published 8 vCPU, 16 GB RAM and SSD requirement. The docs list 1 TiB of storage; this VPS has 1,000 GB, so watch disk use and plan to move up if it nears full.
Configure and orderor $41/mo on a 12-month term (−50%)
2 TB of NVMe and far more RAM and CPU, for a node you do not want to resize or for running extra chains.
Configure and orderThe Avalanche documentation lists the equivalent of 8 AWS vCPUs, 16 GiB of RAM and 1 TiB of storage, and says an SSD is strongly suggested because slow drives cause slower, less reliable reads and writes. It also notes that a fully connected node keeps a couple of thousand live TCP connections, which can overwhelm a weak home router. A server in a data centre does not have that problem.
The VPS build matches the published numbers: 8 vCPU, 16 GB of RAM and a 1,000 GB NVMe disk. That is slightly under 1 TiB, so check df -h regularly and set an alert at 85%. If you want headroom, or you will run more than one chain, the dedicated Medium has 2 TB of NVMe and 128 GB of RAM.
Pick the VPS or the dedicated server and pay with crypto.
Avalanche publishes an installer script that sets up AvalancheGo and a systemd service.
Port 9651 must accept inbound connections. Keep 9650 (the API) on localhost.
The first bootstrap takes a while. Ask the node when it is done.
Commands assume Ubuntu 22.04 or 24.04 and a root login.
# log in from your computer
ssh root@YOUR_SERVER_IP
# update the system and create a user that will run the node
apt update && apt -y upgrade
adduser --disabled-password --gecos "" avax
# firewall: SSH first, then only the ports below
ufw allow OpenSSH
ufw enable
ufw allow 9651/tcp # AvalancheGo peer port; the docs require inbound access here
# do not open 9650 (the HTTP API) to the internetThe installer script is published in the Avalanche docs. Open the installer page to confirm the current script address before you run it, and read the script first.
wget -nd -m https://raw.githubusercontent.com/ava-labs/avalanche-docs/master/scripts/avalanchego-installer.sh
less avalanchego-installer.sh # read it before you run it
chmod 755 avalanchego-installer.sh
./avalanchego-installer.sh # follow the prompts for a mainnet node# download the avalanchego-linux-amd64 tarball from the official releases page,
# unpack it, then run it with the API bound to localhost:
./avalanchego --http-host=127.0.0.1The installer creates a service called avalanchego. The first bootstrap takes time while the node downloads and verifies the chains.
systemctl status avalanchego
journalctl -u avalanchego -f # Ctrl+C to stop watchingcurl -s -X POST --data '{
"jsonrpc":"2.0", "id":1,
"method":"info.isBootstrapped",
"params":{"chain":"X"}
}' -H 'content-type:application/json;' 127.0.0.1:9650/ext/info
df -h / # disk left; alert at 85%The Avalanche docs list the equivalent of 8 AWS vCPUs, 16 GiB of RAM and 1 TiB of storage, with an SSD strongly suggested. Port 9651 must accept inbound connections.
It is slightly under the published 1 TiB. It works as long as usage stays below that, so check df -h regularly. If you want headroom, take the dedicated server with 2 TB of NVMe.
9651 for peer connections (inbound required per the docs) and 9650 for the HTTP API, which you should keep on localhost.
Validating requires staking AVAX and meeting further requirements. Read the Avalanche validator documentation first; hosting a node here is the infrastructure part only.
No. You create an account with a generated login, top up with crypto and deploy. See no-KYC VPS hosting. You stay responsible for what you run, under our terms.
Checked 20 October 2026. Chain sizes and software requirements change, so confirm against the source before you order.
Pick a size, pay in crypto, log in as root. No ID, no card.
