Cost Estimation
Standalone Server
Nodepilot helps in provisioning a standalone node on the platform of your choice.
Sui
The following is the estimated cost for running a recommended configuration Sui blockchain node on popular platform providers in Americas region.
As per the official documentation for a Sui full node its recommended to have minimum of the following:
- CPU: 8 cores or 16 vCPUs
- Memory: 128 GB
- Disk: 4 TB NVMe
Provider | Server Type | Server Cost ($) | Disk (GB) | Disk Type | Disk Cost($) | Monthly Cost ($) |
---|---|---|---|---|---|---|
AWS | r6a.4xlarge | 666.26 | 4000 | GP3 | 320.00 | 986.26 |
GCP | n2-highmem-16 | 695.01 | 4000 | Balanced SSD | 440.00 | 1135.01 |
Azure | EC16as v5 | 659.92 | 4096 | Standard SSD | 307.20 | 967.12 |
DigitalOcean | m-16vcpu-128gb | 672.00 | 4000 | Default | 400 | 1072.00 |
Latitude | c3.medium.x86 | 367.00 | 1900 x2 | NVMe | included | 388.00 |
The costs estimation was based on Americas region and may vary user to user. It’s possible to run nodes on lower configuration, it totally depends on the usecase.
GCP cost can be reduced by sunstained use discount, so the overall server cost could reduced to 1012.10.
Ethereum
The following is the estimated cost for running a recommended configuration Ethereum blockchain Geth-Lighthouse node on popular platform providers in Americas region.
As per the official documentation for a Ethereum full node its recommended to have the following:
- CPU: 4 cores or 8 vCPUs
- Memory: 16 GB
- Disk: 2 TB NVMe
Provider | Server Type | Server Cost ($) | Disk (GB) | Disk Type | Disk Cost($) | Monthly Cost ($) |
---|---|---|---|---|---|---|
AWS | c6a.2xlarge | 227.38 | 2000 | GP3 | 160.00 | 387.38 |
GCP | c3d-highcpu-8 | 224.39 | 2000 | Balanced SSD | 220.00 | 444.39 |
Azure | F8s v2 | 246.74 | 2048 | Standard SSD | 153.60 | 400.34 |
DigitalOcean | g-4vcpu-16gb | 126.00 | 2000 | Default | 200.00 | 326.00 |
Latitude | c2.large.x86 | 285.00 | 2000 | NVMe | included | 285.00 |
Avalanche
Based on the official documentation for a AvalancheGo full node its recommended to have the following:
- CPU: 4 cores or 8 vCPUs
- Memory: 16 GB
- Disk: 1 TB SSD
Provider | Server Type | Server Cost ($) | Disk (GB) | Disk Type | Disk Cost($) | Monthly Cost ($) |
---|---|---|---|---|---|---|
AWS | c6a.2xlarge | 227.38 | 1000 | GP3 | 80.00 | 307.38 |
GCP | c3d-highcpu-8 | 224.39 | 1000 | Balanced SSD | 110.00 | 334.39 |
Azure | F8s v2 | 246.74 | 1024 | Standard SSD | 76.80 | 323.54 |
DigitalOcean | c-8 | 168.00 | 1000 | Default | 100.00 | 268.00 |
Latitude | s2.small.x86 | 248.00 | 1000 | NVMe | included | 248.00 |
Polygon
Based on the official documentation for a Polygon full node its recommended to have the following:
- CPU: 32 cores or 64 vCPUs
- Memory: 64 GB
- Disk: 5 TB SSD
Provider | Server Type | Server Cost ($) | Disk (GB) | Disk Type | Disk Cost($) | Monthly Cost ($) |
---|---|---|---|---|---|---|
AWS | c6a.8xlarge | 897.52 | 5000 | GP3 | 400.00 | 1297.52 |
GCP | e2-standard-32 | 887 | 5000 | Balanced SSD | 550.00 | 1437.00 |
Azure | F32s v2 | 987.69 | 8192 | Standard SSD | 614.40 | 1602.09 |
Latitude | c3.medium.x86 | 367.00 | 1900 x2 | NVMe | included | 372.00 |
Base
According to the official documentation for a Base full node its recommended to have an SSD of 1TB but we recommend to have atleast 4TB SSD for downloading and restoring snapshots. As per writing this doc each mainnet snapshot takes around 1.5TB of space. So here are our recommendations:
- CPU: 4 cores or 8 vCPUs
- Memory: 16 GB
- Disk: 4 TB SSD
Provider | Server Type | Server Cost ($) | Disk (GB) | Disk Type | Disk Cost($) | Monthly Cost ($) |
---|---|---|---|---|---|---|
AWS | c6a.2xlarge | 227.38 | 4000 | GP3 | 320.00 | 547.38 |
GCP | c3d-highcpu-8 | 224.39 | 4000 | Balanced SSD | 440.00 | 664.39 |
Azure | F8s v2 | 246.74 | 4096 | Standard SSD | 307.40 | 554.14 |
DigitalOcean | c-8 | 168.00 | 4000 | Default | 400.00 | 568.00 |
Latitude | c3.medium.x86 | 367.00 | 1900 x2 | NVMe | included | 388.00 |
Solana
Based on the official documentation for a Solana full node its recommended to have the following:
- CPU: 16 cores or 32 vCPUs
- Memory: 512 GB
- Disk: 2 TB SSD
But we recommend to have atleast a buffer of 1 TB for logs and other operational purposes. Also as per our observations and the doc we will run a VM with 64 vCPUs for cloud providers. So here are our recommendations:
- CPU: 64 vCPUs
- Memory: 512 GB
- Disk: 3 TB SSD
Provider | Server Type | Server Cost ($) | Disk (GB) | Disk Type | Disk Cost($) | Monthly Cost ($) |
---|---|---|---|---|---|---|
AWS | r6i.16xlarge | 2947.36 | 3000 | GP3 | 240.00 | 3187.36 |
GCP | n2d-highmem-64 | 3004.18 | 3000 | Balanced SSD | 307.34 | 3311.52 |
Azure | Standard E64as v5 | 2642.69 | 4096 | Standard SSD | 307.40 | 2950.09 |
Latitude | s3.large.x86 | 735.00 | 2 x 3800 | NVMe | included | 735.00 |