Trust & data
Built to be trusted with vehicle data
VehIQ is the trust layer for global automotive, so how we handle data is the product - not an afterthought. These are the architecture commitments we're building on from day one.
Tenant isolation in the database
Isolation is enforced with row-level security in Postgres - not application checks a forgotten WHERE clause can defeat. One dealer's data can never be read by another.
Data you own, in open formats
Operational Postgres plus an Iceberg-class lakehouse the customer owns. Compute engines (Snowflake, Databricks, your own) become interchangeable - never the owner of your data.
Versioned contracts that don't break
Date-pinned API versions and a 12-month deprecation promise. Integrations you build keep working; that stability is what lets an ecosystem form on top.
Lineage and auditability
Every field traces back to its source, and every AI recommendation is stored with its outcome - so a dealer can trust an answer and a regulator can audit it.
In-region data residency
Hosted in-region by default - the EU today, more regions including the Gulf as we expand - with documented residency and a per-source licensing strategy for vehicle data (registry access, commercial providers, and data-access regulation like the EU Data Act).
Confidence, not black boxes
Valuations and decisions show their sources and a confidence interval. Nothing important is a number you have to take on faith.
Honest about our stage
VehIQ is pre-seed. The above are deliberate architecture decisions and design commitments - not a claim of formal certifications we don't yet hold. As we grow with design partners, we'll pursue the certifications and audits the global automotive industry expects, and document them here.
Security disclosures: simon@siax.io.