Glossary

Data Lakehouse

A modern data architecture that combines the low-cost, flexible storage of a data lake with the transactional guarantees and SQL semantics of a data warehouse. The dominant pattern for dealer-owned automotive data infrastructure.

QoreVault is implemented as a dealer-owned lakehouse. The dealer holds raw extracts, transformed tables, and the unified core in a single governed environment, with the audit log and a Continuity Certificate.

Also known as: lakehouse

What it looks like in a dealership

  • Raw CDK extracts land in the lake layer, while cleaned customer and deal tables sit in the warehouse layer, all in one governed environment.
  • QoreVault stores raw, transformed, and unified tables under a single audit log, so every answer can be traced back to the source row.

Common questions

Why not just use a data warehouse?+

A warehouse alone forces you to transform data before you can store it, which means throwing away raw history you may need later. A lakehouse keeps the raw extracts and the finished tables together, governed the same way.

Who owns the lakehouse?+

With QoreVault, the dealer does. The environment, the data, and the audit trail are yours, documented in a Continuity Certificate so the data outlives any vendor contract.