Data architecture
Built to integrate real data responsibly — not to work around the absence of it.
Valyo is designed to connect to authorized public, commercial, and board-approved data feeds through provider-specific adapters. This page describes that architecture plainly, for Realtors, boards, and data providers evaluating whether Valyo is a serious technology partner to work with.
Where data comes from
Every category Valyo's architecture is built to support:
User-supplied data
What the Realtor enters directly — the subject address, corrections to auto-filled property facts, and comps they add themselves.
Public / open data
Government and municipal datasets published under an open license — no commercial agreement required, no restricted-use terms. Example: City of Vancouver's Open Data zoning API, live today.
Commercial property-data providers
Licensed vendors supplying property characteristics, sold comparables, or market statistics — integrated only once a commercial-use agreement is in place.
Authorized board / MLS / DDF / VOW feeds
Real estate board data, accessed only through a formal Technology Provider relationship and the board's own permitted-use terms — never scraped or accessed indirectly.
Municipal / planning datasets
Zoning, assessment, and planning data published by a municipality or regional authority.
Market-statistics providers
Aggregate, geography-level statistics (median price, days on market, sale-to-list ratio, trend) — never a substitute for real comparable-sale evidence.
Maps / geocoding
Address resolution and normalization — Google's Geocoding API today, a standard commercial API relationship, not a real-estate data license.
AI-assisted extraction where permitted
AI may help parse or structure data a provider has already authorized Valyo to use — it is never a substitute for a real data-access relationship, and never a way around one.
How a data source reaches a report
Every source — real or synthetic — passes through the same pipeline. No category skips a step.
- 1External data source
- 2Provider adapter
- 3Normalization
- 4Provenance recorded
- 5Permission / governance check
- 6Valuation & report workflow
Principles this architecture enforces
- Public visibility is not treated as commercial-use permission — a page being viewable doesn't make its data licensed for a paid product.
- Every record's source is tracked end-to-end — from ingestion through to what's shown in a report — not summarized or anonymized away.
- Provider-specific usage rules (display, PDF inclusion, redistribution, AI processing, model training) are enforced individually, per provider and per market — not a single blanket "data allowed" switch.
- Restricted data is never scraped or accessed by bypassing a provider's own access controls.
- An unrecognized or unconfirmed data source is treated as fully restricted by default — nothing is assumed permitted.
- A licensed provider can be connected behind an existing interface without rewriting the valuation engine, the report, or any other part of the product.
Current data status
Address resolution and Metro Vancouver municipal zoning already run on real, live data sources today — Google's Geocoding API and the City of Vancouver's Open Data program, respectively. Comparable sales, active listings, and market statistics are currently generated from Valyo's own internal demo data set while a licensed real-estate data relationship is pursued — Valyo does not have MLS, DDF, VOW, or a commercial property-data license today, and does not represent otherwise.
The architecture above exists specifically so that connecting a real, licensed provider for any of those categories — for one market or several — requires adding an adapter and a governance record, not rebuilding the product.
Data & integration partners
Valyo is actively pursuing authorized property, transaction, and market data relationships for Canadian and U.S. markets. We're interested in working with property-data providers, real estate boards and associations, brokerages, market-data providers, and municipal open-data programs.
Discuss a data integration