ComputeFinder

Method

What we publish, how we check it, and what we leave out on purpose.

What is published

ComputeFinder publishes original source-linked accounts and specifically licensed data imports. Provider and programme guides, infrastructure records, research and news retain their own evidence, dates and limits. We do not publish a live price or availability feed. Use the official links for current prices, terms, eligibility and application status.

Publication rules

These rules govern new and corrected content. Where a review note is published, read its scope alongside the sources and dates.

  1. Evidence. Factual wording needs direct support from a fetched original source, with dates, attribution and uncertainty recorded.
  2. Exact source use. Ordinary links, original factual accounts, licensed adaptations and dataset imports are assessed separately. Public access or a citation does not grant rights to copy text, images or databases. Source-specific conditions stay attached. See sources and licences.
  3. Review. Routine factual changes require independent review. Units, scope, stage and basis must stay explicit. Software tests check behaviour; they do not establish factual truth.
  4. Release. Changes require applicable checks and independent release review before automatic deployment, followed by a live check. Ordinary pages use published records rather than fetching a provider during your visit.

Dates and unknowns

A source's publication date, an event date, a retrieval time and an evidence check or review date describe different events. A new page or build does not recheck older facts. Missing dates and values stay unknown; missing is not zero.

A proposal, permission, operating facility and compute available to use are distinct claims. Read capacity with its metric, stage, basis, date and source. We do not add capacity figures across different metrics, stages or sites.

Targeted change checks

The targeted change detector records retrieval metadata and compares fingerprints within assessed source scopes. It keeps no source bodies or excerpts. A detected change is a candidate for review, not an automatic change to a public fact or check date. A listed source or a configured check does not prove continuous monitoring.

How we know

What we leave out

There is no single best score and no ranking. We do not scrape a source whose terms forbid it. Missing values stay unknown, and estimates retain their source's scope and uncertainty. Suggest a correction if a record is wrong or out of date.