Skip to main content

Data quality & trust

GPUVerse distinguishes what it observed from a source, what it derived by computation, what it curated as qualitative reference, and what is simply unknown. Every number below is counted from the live catalog — none is estimated.

Overview

Catalogs
12
Total entities
224
Observed
203
Curated
21
Unknown (empty)
0
Derived
VRAM (per model)

Derived values (e.g. model VRAM) are computed per-entity from observed inputs and labelled DERIVED on their own pages rather than counted as a separate catalog.

By catalog

CatalogEntitiesTrustFreshness
GPUs112Observedn/a
Providers16Observedn/a
Models0Observedfresh 0 fresh
Regions67Observedstale 67 stale
Frameworks0Observedfresh 0 fresh
Compliance5Observedn/a
Interconnects3Observedn/a
Workloads11Curatedn/a
Networking6Curatedn/a
Storage3Curatedn/a
Architectures1Curatedn/a
Benchmarks0Unknownn/a

Freshness

From the backend freshness contract — not recomputed here

Regions are sourced from provider pages on a 24-hour window; all 67 current region records are past that window (stale), so they are shown with a stale marker rather than as current. Model and framework records are within their windows (fresh). GPUs and providers carry a last-verified timestamp on their own pages.

Known data gaps

Shown as unknown, never invented
  • Benchmark measurementsNo credible benchmark has been ingested; measured performance is unknown.0 of 0
  • Region geographySome regions' source does not provide a geography; it is not inferred.18 of 67
  • Compliance issuer / scope / validityOnly the certification name is sourced from provider declarations.5 of 5
  • Interconnect bandwidth / latencyNumeric interconnect specs are not sourced; only qualitative suitability is.3 of 3