Declared freshness targets
Write the expectation once — warning and critical thresholds tied to the watched table.
On the roadmap
This solution is planned — not live yet. Related VectorData capabilities that already ship are linked below.
Use case · Roadmap
Data contracts / SLOs
Freshness targets and owner expectations per table — on the roadmap.
The problem
“The table should be fresh by 8am” lives in a wiki, a Slack thread, or someone’s head. When it breaks, there is no shared contract to point at.
The outcome
Planned: declare freshness SLOs and owners per watched table, surface breaches as contract failures in Watchdog, and keep the definition next to the alert.
Soon
On the VectorData roadmap
Per table
Target + owner, not tribal knowledge
Metadata
Same BigQuery signals as today
Capabilities
Named owners
Route contract breaches to the person who can fix the pipeline, not the whole channel.
Breach history
Show how often a contract failed so leadership can prioritize hardening.
Clear roadmap
Available today: freshness thresholds and alerts. Contracts UI and ownership layer coming next.
- ✓Today’s freshness monitoring already supports per-table thresholds
- ✓Contracts and ownership UX are on the roadmap
- ✓Metadata-only architecture stays the same when contracts ship
- ✓Book a Data Stack Health Audit to prioritize which tables need contracts first
Related
Watchdog / Fix first
AI ranks stale tables, failed dbt runs, and cost spikes into one Fix-first queue.
Read →Executive KPI trust
Know the KPI tables are fresh before the Monday leadership meeting.
Read →Board deck confidence
Freeze the numbers that go in the board pack — with a freshness check first.
Read →Pipeline on-call
Escalation and mute windows for data incidents — without pager chaos.
Read →