Methodology

This site is designed to help you build a shortlist quickly, then verify details on official provider pages. Dataset last checked: 2026-01-13.

Data sources

Every provider and plan includes a sources list (URL + retrieved date). Automated updaters fetch official pricing pages and generate plan entries. See Dataset & freshness.

npm run vps:update
npm run vps:tags
npm run vps:measure
npm run vps:validate

Price normalization

Plans store the native monthly price and optionally a USD monthly price. Filters and scoring prefer USD to compare across currencies. Plans can also store a billing cycle and the total billed amount per cycle for annual/quarterly pricing. If USD is not available for a plan, it may be excluded by USD budget filters. When a promotional/intro price is known, the dataset can also store a separate regular/renewal monthly price and a promo label.

Route tags

Route tags are a lightweight taxonomy used for filtering and comparisons. Some tags are sourced from provider pages, while others are derived from plan attributes (for example nvme, ipv6, refund-eligible). The tag normalization step keeps tags lowercase and consistent. Browse tags on Route tags.

Latency tiers

Latency tiers are primarily derived from scripted, multi-probe measurements (Globalping ping; optional traceroute for route tags). If a plan has a city/country but no measurement target yet, the system falls back to a distance-based estimate to avoid empty data. See Latency tiers for targets and tier bands.

Benchmarks

Benchmarks are optional and are stored separately from the pricing dataset so automated pricing syncs don’t overwrite them. When available, benchmark results are used on the Performance page. Results can vary due to noisy neighbors, host differences, and time of day — treat them as signals, not guarantees.

# 1) Run a benchmark script on the VPS (example: YABS), save output to a file
# 2) Add it to the dataset by plan slug:
npm run vps:bench:add -- --plan <plan-slug> --file <yabs-output.txt>

Scoring

The score is a heuristic (CPU/RAM/storage + storage type + IPv6 + refund signals + value-for-money). It is not a benchmark. If a regular/renewal price is available, scoring uses that price to avoid over-weighting short-lived promos. Use it to sort results, then confirm performance for your workloads.