Method and data sources
Everything on VPS Deals Radar is produced by a small, fully deterministic pipeline. No model runs at page-generation time, no API key is used, and no number is ever typed in by hand. This page explains exactly what happens, so you can check it instead of trusting it.
Where the data comes from
Each provider's own public pricing or VPS page is fetched over plain HTTP on a
schedule. Only publicly reachable pages are read: nothing behind a login, nothing requiring
a bypass of anti-bot protection, and robots.txt is honoured. The pipeline reads
26 source pages per run and tracks 26 providers.
This site is not a scraper of other comparison sites. There is no second-hand data. If a provider's page cannot be read, the entry says so.
How a price is chosen
From each page the pipeline extracts every monthly-looking figure together with the literal text around it. It then discards anything that is clearly not a plan price — hourly rates, annual rates, backup add-ons, extra IP addresses, minimum spend figures — and publishes the cheapest survivor.
The discarded figures are not thrown away. They are listed on each provider page with the reason they were rejected, so the filtering can be audited rather than believed.
What is published next to a price
A price on its own can be true and still mislead. Two figures sitting beside it decide what it actually means, and most price tables drop both.
The commitment. Not every figure written "/mo" is a month-to-month price. 10 of the 26 priced providers here are quoting a rate that depends on something — prepaying two years, a first-three-months promotion, or a page that shows several terms beside one price without saying which one it belongs to. The Term column says which, and says not stated where the page is silent. Silence is not evidence of a monthly price, so it is not reported as one.
The renewal. 8 of the 26 providers state what the advertised rate becomes later, usually within a few words of the headline — and the jump is often large. Both figures are published, each quoted from the provider's own page, because a deals page showing only the introductory number is showing half the offer.
Both are read from prose, so both are written to stay quiet when the page is ambiguous. The commitment is only accepted when it sits immediately beside the figure. A duration attached to something else in the sentence — "free SSL for the first 12 months" — is not read as a price condition. A renewal is only accepted when it is higher than the advertised figure and no other price sits between the two, because in a plan table the nearest following sentence often belongs to the next plan down.
A discount is held to the same standard as the number it sits beside. It is only published when the quoted sentence shows the figure and some price in that sentence lands on the figure once the percentage is taken off it — so a plan reading "67% off … $19.49 $6.49/mo" is shown, while a banner elsewhere on the page reading "Up to 70% off VPS hosting" is not. Where nothing qualifies the cell is left as a dash, rather than filled with a campaign that belongs to no plan in particular.
What happens when something fails
- Page blocks the request — no price is published. The entry is marked as blocked and links to the provider instead.
- Price only exists in JavaScript — no price is published, because the pipeline only reads what the server actually returns.
- A refresh fails after a previous success — the last verified price is kept but explicitly labelled stale, with the date it was verified.
- The page states an end date that has passed — the offer is kept for the record and marked expired, never shown as live.
What this pipeline never does
- It never invents a price, a discount, a rating, or a review count.
- It never asserts a commitment the page does not state. Where the page is silent, the column says so rather than assuming the friendliest reading.
- It never warns about a renewal that is not there. A later figure is only published when the page states it and it is higher than the advertised rate.
- It never estimates a missing figure from a similar provider.
- It never carries a number forward without marking it stale and dating it.
- It never dates a carried-forward number to the refresh that failed. The date shown is the last successful read, and it does not move forward while the refreshes keep failing.
- It never lets a page, a badge, or its structured data call a figure current when the refresh failed. An InStock claim carries its qualifier inside the same block, because a search engine reads that block without the prose around it.
- It never prints a discount beside a price unless the sentence it quotes shows that price and the arithmetic works. Percentages are everywhere on these pages — site-wide "up to" ceilings, flash-sale banners, and the neighbouring plan's row — and every one of them is a real number that means nothing about the figure next to it.
- It never buys traffic, follows, or engagement.
- It never publishes structured data for a price it cannot quote.
Those rules are not documentation written after the fact. They are declared in the repository's configuration file, which the code reads at build time.
How often it updates
A scheduled job runs every 6 hours. It re-reads every source page, rebuilds the site, and commits whatever changed. The date shown on each entry is the date that specific provider's page was last read — not the date of the most recent run in general.
The price-history table on each entry is a change log, not a run log. A row is added only when the price or the status actually moves, and a later change on the same day replaces that day's row, so a date shows the last state recorded that day. A table with two rows therefore means the price moved twice — not that the pipeline ran twice.
Money
This site sells nothing and takes no payment. Some outbound links may be affiliate links once a provider's published partner programme accepts this site. Affiliate status never influences which price appears, because the price is not chosen by a person — it is whatever the extraction step returns. Where an affiliate link is in use, it replaces the plain link to the same destination.
Questions
Where do these prices come from?
Every price is read from the provider's own public pricing or VPS page at build time. Each one is shown next to the exact sentence it was taken from, and the page it came from is linked. Nothing is typed in by hand.
Why do some providers show no price?
Some pages render their prices with client-side JavaScript, and some refuse automated requests. In those cases no number is published at all, because a guessed or remembered price would be worse than none.
How often is this page updated?
The pipeline runs every 6 hours on a scheduled job. Each run re-reads every source page and commits whatever changed.
What does 'stale' mean?
It means a refresh attempt failed for that provider, so the last successfully verified price is still shown together with the date it was verified. It is never presented as current.
Do you get paid for the links?
Not currently. No outbound link on this site is an affiliate link — every one goes straight to the provider's own page. If a provider's published partner programme ever accepts this site, those links will be marked rel="sponsored" and disclosed in the footer before they go live. It would never change which price is shown, because no person chooses the price.
Check it yourself
Every entry on this site links to the exact page its number came from. Open the link, search the page for the quoted text, and see whether the figure is there. If it is not, the entry is wrong and should be reported.
Last pipeline run: 20 Oct 2026, 11:42 UTC.