Methodology
How the data on this site is sourced, what makes us leave a value out, and the conditions a page has to meet before it is published.
Where the numbers come from
Every factual value on this site was read from a page published by the provider it describes — their documentation, pricing page or knowledge base. Nothing is written from memory, and nothing is taken from a search result summary, a forum post or another comparison site.
Each value is stored with the URL it came from, the sentence it came from quoted verbatim, the date it was read, and how authoritative the source is. You can see all four by expanding "Sources" beside any figure. If a value has no source, it cannot be added — the build rejects it.
When we leave a cell empty
A blank is not an oversight. It means we looked and the provider does not publish that figure, or publishes it somewhere we could not treat as evidence. We would rather show a gap than a number we cannot stand behind.
Specific cases where we record nothing: when a page states a figure only after JavaScript runs and the number is missing from what we can read; when two fetches of the same page disagree; when the only statement is on a page about a different product; and when two official sources contradict each other.
That last one is real. One host's marketing page advertises unlimited bandwidth while its own fair-use policy says it does not offer unlimited bandwidth. We publish neither figure.
| Provider | Pricing | Limits | Execution | Deployment | Infrastructure | Data | n | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AWS Amplify | 16 | ||||||||||||||||||||||||||||||||||||
| Cloudflare Pages | 14 | ||||||||||||||||||||||||||||||||||||
| DigitalOcean | 21 | ||||||||||||||||||||||||||||||||||||
| Fly.io | 16 | ||||||||||||||||||||||||||||||||||||
| Heroku | 20 | ||||||||||||||||||||||||||||||||||||
| Hetzner | 12 | ||||||||||||||||||||||||||||||||||||
| Hostinger | 9 | ||||||||||||||||||||||||||||||||||||
| Hostinger VPS | 10 | ||||||||||||||||||||||||||||||||||||
| Kinsta | 14 | ||||||||||||||||||||||||||||||||||||
| Linode (Akamai Cloud) | 14 | ||||||||||||||||||||||||||||||||||||
| Netlify | 19 | ||||||||||||||||||||||||||||||||||||
| Railway | 21 | ||||||||||||||||||||||||||||||||||||
| Render | 22 | ||||||||||||||||||||||||||||||||||||
| SiteGround | 11 | ||||||||||||||||||||||||||||||||||||
| Vercel | 20 | ||||||||||||||||||||||||||||||||||||
| Vultr | 16 | ||||||||||||||||||||||||||||||||||||
| WP Engine | 10 | ||||||||||||||||||||||||||||||||||||
sourced from the provider's own documentationnot published, or not published in a form we could cite
Why some values say "limited"
Capability columns take one of three values. "Supported" means the provider documents the capability without material qualification. "Not supported" means a provider page explicitly states the absence — we never infer it from silence. "Limited" means the capability exists but is constrained, and the quoted excerpt says how.
"Limited" carries most of the useful information. Docker on a self-managed VM is not the same product as a managed Docker deploy. Autoscaling that requires a paid plan is not the same as autoscaling. Scheduled jobs on a fuzzy hourly cycle are not cron. Flattening those into a tick would lose the thing you are trying to find out.
Facts and opinions are stored differently
A sourced fact has a URL. A recommendation does not, because it is a judgment, and giving it a citation would dress opinion up as evidence.
Recommendations are stored separately, carry the name of whoever wrote them, and are marked approved or not. An unapproved recommendation blocks the page from being indexed. Where you see "Choose X if…", a person wrote and signed off on that wording.
What has to be true before a page publishes
A comparison needs at least six criteria sourced for the pair, at least three where the two genuinely differ, a relevance score showing the providers plausibly substitute for each other, no fact older than 120 days, and approved recommendations on both sides.
A provider page needs at least four sourced facts. A stack page needs at least three providers that document that stack.
Pages that fail are still built, but marked so search engines skip them, and they say on the page which requirement they missed. A URL existing is not a reason to publish it.
What we deliberately do not do
No overall scores. "8.4 out of 10" implies a measurement nobody performed, and we would have to invent the weighting. Where two providers differ we show both values and say which criteria separate them.
No star ratings or review markup. Structured data is used only where it genuinely describes the page.
No ranking by commission. There are currently no affiliate relationships on this site, and if that changes, paid links will be marked and disclosed rather than folded into an ordering you cannot see.
Freshness, and where this is weakest
Every value carries the date it was read, shown as the "Updated" stamp on each page. Pricing moves fastest; a fact older than 120 days blocks a comparison from publishing until it is re-checked.
The honest limitation: this site currently documents what providers publish about themselves. That is verifiable and it is not the same as independent measurement. Nothing here is a benchmark we ran. Where a provider publishes nothing, we have nothing — which is why a handful of cells stay empty rather than being filled in with something plausible.
Corrections
If a figure here is wrong or has changed, tell us and we will re-check it against the source and update the date. The quoted excerpt beside each value exists precisely so an error is easy to demonstrate.