Price data and source checks

Available files

The public JSON, CSV and health files report aggregate coverage only. They do not contain provider-by-provider price rows, source links, retained history, or embeddable price badges.

The full retained set still drives the comparison, calculator and provider pages. Limiting bulk downloads does not remove a plan from the human comparison; its source status and billing completeness decide whether it may rank.

• /api/v2/latest.json: retained, current, non-ranking, plan and reference-meter counts, plus the publication limit.
• /deployment-prices.csv: the same counts in one CSV row.
• /api/v2/health.json: whether the complete retained set loaded and the exact current/non-ranking split.
• /openapi.json: the contract for those aggregate files.

What the comparison uses

The retained set contains 996 source-linked facts: 991 deployable plans across 53 providers and 5 reference meters. Current eligibility is recalculated from the latest source decision at every build; the generated summary below and the public aggregate files report the current and non-ranking split.

The represented source checks run from 2026-07-25 15:00 UTC through 2026-07-26 11:43 UTC. The assembly date does not make an older source check newer. Each price uses the update limit appropriate to its provider and offer type.

• Plan coverage: 593 VPS, 267 PaaS, 59 managed Postgres, 38 serverless-container, 19 Kubernetes and 15 static-host plans.
• Price coverage: 701 provider-published facts, 194 reproducible calculations, 75 rows that need visitor inputs and 26 quote-only rows.
• Reference coverage: 5 internet-egress meters. There is no complete provider-wide table for storage, requests, inter-zone traffic, inter-region traffic, backups or load balancers.

Why a price cannot rank

A price is not ranked when its source check is too old, the offer is sold out, present orderability is unknown for a limited offer, the cited page is unavailable, or a moved page no longer proves the same provider and offer. A price also stays out when the visitor must request a quote or supply usage details first.

A source-linked plan can still produce no total. If the selected workload needs storage, transfer, public IPv4, a load balancer, a database, or another mandatory charge whose price is unknown, the calculator shows the missing item and does not treat it as free.

The source decision comes first. Compatibility and complete-bill checks then decide whether a current plan fits the selected workload and has every required charge. Reference meters provide context but never rank as deployable plans.

How moved and blocked sources are treated

The bounded source review found 41 redirects. Five HostBrr order links kept the same provider and offer slug, and one Linode credit link moved to the matching Akamai offer; these moves do not refresh the dated facts. Thirty-three GreenCloudVPS offer links now land on one generic cart, one Upsun trial link lands on an archived article, and the Platform.sh pricing page now points to Upsun. Those destinations do not prove the retained offer, so the affected facts cannot look current or rank.

The Leaseweb source returned HTTP 400 and the Oracle compute source returned HTTP 403. No block was bypassed and no price was inferred. An HTTP response describes that check; it is not a claim that a provider refused publication.

Automatic collection is a separate decision from displaying a dated fact. Only a provider route with recorded access, terms, robots, schedule, request load and stop conditions may be refreshed unattended. The lack of such a route does not erase a still-current fact that was checked manually.

Publication and reuse limit

An original comparison or calculator explanation may show an isolated dated price fact when it states the real value and billing meaning, links to the provider's own source, gives the checked time, uses original wording, copies no provider prose or assets, and makes no affiliation claim. A blanket written grant is not required for that use.

Bulk redistribution is different. No provider-level basis has yet been recorded for publishing all price rows or retained history as downloadable JSON, CSV or badges, so those details are withheld. The public files expose aggregate counts and health only. Anyone seeking to reuse provider facts should follow each source and assess the intended use against the provider's current terms.

Corrections

Use the correction instructions to report a stale price, wrong formula, moved source, missing charge or plan-mapping error. Include the Where To Deploy page, the provider source page and the value that should be reviewed.

Use the corrections form to report a price, meter, formula, or plan-mapping problem. Include the affected page and provider source so the result can be recomputed.