Dataset 02Last reviewed

GPU Systems, Pricing & Market Data

Qualified GPU systems, hardware specifications, listings, and classified price observations organized for comparison, sales analysis, and index development.

Start a conversation

Request accessDiscuss custom coverage

Prefills dataset

qualified-ai-systems

  • Contents

    Specifications, normalized configurations, and separately classified market observations

  • Geography / period

    Declared per source where evidenced

  • Evidence classes

    7 classes, kept structurally separate

Evidence classes

A price is not one kind of fact. This dataset keeps each observation type in its own class, and never merges them into a single blended value.

ClassWhat the record assertsPresent today
specificationDeclared system and component attributes as published by the sourcein review
listingAn observed public offer at a point in time — not a completed salein review
quoteA price supplied on request for a stated configuration and quantityin review
indicative observationA reported level without a verifiable counterparty or settlementin review
reported saleA transaction asserted by a source but not independently confirmedin review
verified transactionA transaction with confirming evidence — recorded only where it existswhen available
index researchMethodology work on how a governed index could be constructedmethodology only

Rillor does not operate a live marketplace, a consolidated tape, a settlement-grade benchmark, or a production index.

Index research

GPU hardware price indexes

Rillor's index methodology defines physical GPU hardware price assessments by comparable system grade. The source set spans OEM references, distributor quotes, broker and listing observations, secondary-market results, and verified sales where they exist. No index series is published.

  1. 01

    Define comparable grades by GPU family, system configuration, condition, and market segment.

  2. 02

    Collect independent specification, quote, listing, reported-sale, and verified-transaction inputs.

  3. 03

    Preserve evidence classes so indicative, reported, and verified observations remain distinct.

  4. 04

    Govern eligibility, weighting, outliers, stale data, contributor concentration, and restatements.

  5. 05

    Publish a series only after observation depth, contributor diversity, methodology, and review gates pass.

Representative enterprise uses

  • GPU procurement benchmarking and cross-OEM comparison

  • Primary and secondary market pricing and reported-sales analysis

  • Asset valuation, depreciation, and GPU-backed finance research

  • Governed physical-hardware price index development

Intended users

  • GPU procurement, finance, and market-intelligence teams
  • AI infrastructure and capacity planners
  • Market-data, research, and index teams

Scope

A source-classified collection of qualified NVIDIA and AMD GPU systems, hardware configurations, listings, quotes, indicative prices, secondary-market sale observations, and verified transactions where they exist. Every record is typed by evidence class, so an asking price or a reported sale is never read as a completed transaction. The index program develops repeatable physical-hardware price series by comparable system grade from multiple independent inputs.

Sources, structure, quality, and delivery

Sources, rights, and provenance

Source categories

  • OEM and qualified-system catalogs, configuration records, and manufacturer specifications
  • Selected distributor, reseller, and broker listings, quotes, and availability observations where collection and use rights permit
  • Documented or reported secondary-market sale observations where provenance and transaction status can be recorded
  • Historical Rillor specification and indicative pricing research retained as research material rather than market tape

Rights posture

Every specification, listing, quote, sale record, and contributed observation requires source-level provenance and a recorded acquisition, use, and redistribution posture before commercial access.

Structure, labels, and lineage

Entity resolution and normalization

GPU family, accelerator count, memory, OEM, chassis, CPU, interconnect, cooling, condition, location, seller type, observation type, currency, unit, price basis, and observation time are modeled separately so comparable system grades can be constructed without treating unlike configurations as fungible.

Lineage

Each normalized record is designed to retain its source, capture time, evidence class, seller or venue category, configuration match, transformation history, dataset version, and applicable index-methodology version.

Quality, reconciliation, and versioning

Quality and reconciliation

Quality work covers SKU and OEM resolution, configuration equivalence, sale-status verification, condition and geography adjustments, currency and unit normalization, duplicate handling, outlier review, and contributor diversity. Index outputs require separate methodology, governance, and sufficiency gates.

Freshness and versioning

Refresh and reverification are scoped per source. No continuous or real-time market-data commitment is offered.

Delivery and access discussion

Access state

There is no public raw feed, download, API, live benchmark, settlement-grade index, or service-level commitment.

Delivery discussion

An authenticated API, a scheduled export, or an agreed structured format can be scoped for this dataset. Coverage, schema, authentication, cadence, versions, rights, and support are defined with the engagement.

Use and attribution

Notes for working with this record and attributing its contents.

  • This dataset is not an operating exchange, transaction venue, or order book.
  • A listing, asking price, quote, or indicative reference is not presented as a completed sale.
  • Index work remains methodology and research; no public series is represented as live or settlement-grade.
  • Qualification does not certify fitness for a particular workload or commercial outcome.
  • A documented sale record can omit fees, taxes, shipping, warranties, or other economic terms.
  • A price observed in one market segment may not transfer to another.
  • Published specifications may not describe an installed system's exact configuration or support entitlement.
  • Cite the originating source when a record is reused or republished.
  • Coverage follows the reviewed source set for each dataset.
  • Rillor is not an official market, exchange, or vendor source.
  • Access, delivery, and support terms are agreed per engagement.
  • Recording a rights posture is not the same as holding commercial redistribution rights for every source; permitted use is confirmed during qualification.
  • Conflicting observations are reconciled with the decision retained rather than overwritten, and no accuracy, fill-rate, or match-rate figure is published until it is regenerated and reviewed.