Nodes and validators.
Peers pull, nothing counts it.
A node is an egress machine with an appetite for IOPS: peers sync from you around the clock, and the state only grows. Neither of those becomes a line on the invoice here.
what you get
- traffic
- unmetered ingress and egress
- port
- 1, 10, 100 Gbps
- disks
- NVMe arrays, sized to the chain and the node type
- cpu
- Intel Xeon or AMD EPYC
- memory
- sized with the build
- addressing
- 2 × IPv4 + native IPv6
- access
- root and IPMI
- operating system
- any Linux distribution, mount your own ISO over IPMI, Proxmox or VMware ESXi
- locations
- AMS · NL · MEP · NL · IAD · US-EAST · PHX · US-WEST
- delivery
- a few hours to 7 business days
Custom builds, mostly. Tell us the chain, whether it is a full or an archive node, and what the state weighs today — the array is sized against that rather than against a table on a web page.
where we draw the line
- We do not run the node. No snapshots, no fast sync, no RPC endpoint, no watching your chain for you.
- Unmetered is about the counter, not about physics: a port moves what a port moves, and sync time is mostly the disks.
- One page, not one per chain. The machine is the same machine — the chain changes how the array is sized and nothing else we sell.
- Lawful use only. The acceptable use section applies here exactly as it does everywhere else.
related
workloadCDN originsPull as hard as you like. →workloadstreaming serversThe big night costs the same. →workloadgame serversSilicon nobody shares. →workloadstorage serversRestores cost nothing. →workloaddatabase & computeSame work, same time. →workloadvirtualisation hostsYou bring the hypervisor. →networkunmetered serversNo counter on the port. →network10 Gbps serversPort matched to the machine. →network100 Gbps serversBuilt to order. →