import Base from '../layouts/Base.astro';
import Breadcrumbs from '../components/Breadcrumbs.astro';
const title = 'Methodology — How VPSFinder Verifies VPS Prices';
const description = 'How VPSFinder collects, verifies and version-controls VPS plan data: official sources only, append-only price observations, unknown beats wrong.'
Plan prices, specs and stock status are taken from official provider pages only. Each plan row records
the exact source_url and the checked_at date.
Third-party directories (e.g. FindHost, CC BY 4.0) are used only for provider-level metadata such as
headquarters country, regions and official URLs — never for prices.
When a third-party source conflicts with an official page (or the official page is unclear), the row is not published. Conflicting items go to a review queue and re-enter the dataset only after a fresh official-page check. Missing fields render as "—" rather than guesses.
Every check appends a price observation (date, price, currency, billing period, source). Observations are never overwritten or deleted, so plan pages can show 30/90-day lows and medians once enough checks accumulate. A single observation is labelled "Current price" — no historical statistics are invented.
Ordering uses explicit metrics: native price, monthly-equivalent price (for sorting across billing periods), RAM, vCPU, storage, price per GB of RAM and price per vCPU. Cross-currency comparisons use a fixed snapshot FX table and are marked as approximations. We do not accept payment for placement, and no provider is presented as "best".
The entire dataset lives in the public GitHub repository as JSON, validated by a zod schema on every build. The site is fully static: if the build passes, the numbers you see are exactly the numbers in the repo at that commit.