Data contracts & SLOs
A data contract is a producer's commitment in writing: this product has this shape, arrives by this time, and meets these thresholds. OntaVera checks the commitment continuously and shows consumers the live status, so your finance team knows before close whether the feed it depends on is healthy. When a contract breaks, trust in the product drops on its own, and nobody has to notice first.
Producers declare schema, freshness, and quality SLOs per product, and the declaration is versioned and visible to every consumer.
Checks run continuously against source metadata, and a feed that simply stops arriving registers as a breach. Absence is failure.
Live contract status shows on the product page, so consumers check health before they build on a feed.
Breaches open issues automatically and route to the producer, and closure is verified, meaning the checks pass again before the issue can close.
The product's trust score moves with contract health. It is derived from evidence, with no manual override.
Contract changes go through maker-checker review with notice to consumers before the new version takes effect.
Declare
The producer commits to shape, freshness, and thresholds as part of publishing the product.
Verify
Scheduled checks test the commitment against the source, and a check that cannot run counts as a failure rather than a silent pass.
Signal
Status and trust update on their own, and consumers see the same state the producer does.
Resolve
A breach opens an issue that closes only when evidence shows the contract holds again.
“Is the feed behind our liquidity numbers current right now?”
Live contract status shows on the product page, so you check freshness before close, not after. Checks run continuously against source metadata, and a feed that stops arriving registers as a breach immediately.
“Who changed this schema, and did my team get notice?”
Contract changes go through maker-checker review, and consumers receive notice before the new version takes effect. The declaration is versioned, so you can see exactly what changed and when.
“When a contract breaks, how do I know it was actually fixed?”
A breach opens an issue that closes only when evidence shows the contract holds again. The checks have to pass before closure, so a closed issue means a verified fix, not a claimed one.
Start with proof, not a promise.
There are three ways in, and each one earns the next. You approve the exit criteria before we spend any more of your time or budget.
A 60-minute working session
Bring one report that is expensive to prove. We walk the mechanism against it. Nothing is required from your side.
A two-week guided sandbox
Your team works hands-on against a synthetic sample bank. It requires zero access to your systems and zero procurement.
A six-week proof on your systems
We use read-only metadata across five systems and one priority report, scored against criteria both sides sign first. The decision it produces is yours.