decision guide
Build or Buy Vehicle Data
Compare the work of building vehicle data with using a ready-made source.
Engineering and data-product leaders deciding whether vehicle normalization is core product work.
why it matters
What this helps solve
A first source import is cheap, but schema changes, duplicate variants, licensing checks, provenance, release management, and serving compound over time.
coverage and freshness
Coverage for the current release
Share of export-cleared variants linked to at least one hard external identifier — a source-owned key that resolves to exactly one variant, so joins never rely on name or specification matching.
Share of export-cleared variants with a sourced combined CO2 emissions value in grams per kilometre.
Share of electric and plug-in hybrid variants with a sourced WLTP electric range value.
Maximum age 8 days. Oldest measured source refresh: 2026-09-15.
Apex is designed for weekly source-aware releases, but automated publication remains pending explicit production activation; each source keeps its measured fetch date and may follow a longer upstream publication cadence.
details
What to evaluate
What building entails
An internal implementation must own connectors, retries, source-change monitoring, variant matching, unit normalization, provenance history, licensing controls, releases, and API operations.
Where licensing fits
A licensed layer fits when normalized delivery and reproducibility matter more than owning every ingestion detail; source-specific gaps can still remain pack-owned extensions.
scope boundaries
Keep these limits visible
- Licensing does not remove the buyer's responsibility to validate fitness, source terms, and decision-specific controls.
- Teams with narrow single-source requirements may reasonably prefer an official source integration over aggregation.
- Not a regulatory type-approval or emissions-compliance certification.
- Not a consumer valuation, repair, or vehicle-purchase recommendation service.