OpenDQV Cloud
Start free trial
Write-time data quality enforcement

Bad data stops at the door.

Most tools tell you on Tuesday what went wrong on Friday. OpenDQV Cloud validates every record as it is written — against plain-YAML contracts you own — and seals every decision in a tamper-evident audit chain. The bouncer at the door, at enterprise scale.

Start free trial See how it works

14 days · 200 engine-hours · no credit card

<1 msmedian engine-side validation — fast enough to sit in the write path
3 clouds · 6 regionsAWS, Azure and Google Cloud — you choose where your data lives
40+ starter contractsevery one born in observation mode — nothing enforces until you decide
Every decisionsealed on a hash-chained, tamper-evident audit trail
The platform

One engine. Three jobs.

Your own Vanguard Compute Engine, per-second metered, doing the three things data quality actually needs: stop bad records, measure before you enforce, and prove what happened.

Enforce

Block it at write time

A failing record never enters your system. The decision is synchronous, sub-millisecond in the engine, and returned to the caller with the exact rules that failed.

dob_not_futureBLOCKED
caller informed422 + reasons
Observe

Measure before you enforce

Every contract starts in observation mode: it counts what would have failed on your real traffic without blocking anything. Promote to enforcement deliberately, with the numbers in front of you.

would-block · 7 days220 records
top failing rulebalance_non_negative
Prove

An audit trail that can't be quietly edited

Every validation lands on a sealed, hash-chained audit log — coordinator-witnessed, independently verifiable, built for the conversations you have with regulators.

verify_audit_chainintact ✓
chaingenesis #1 → tip, witnessed
Ask

Your AI assistant already speaks to it

Every contract, metric and audit event is exposed over MCP — the open protocol AI assistants use. Data quality stops being the dashboard someone opens on Tuesdays and becomes a question anyone can ask, mid-conversation, and a check any agent can run before it writes.

“What failed in the customer contract last week?”
→ 220 records would have been blocked. Top rule:
  balance_non_negative (112). Want the audit rows?
How it works

Contract in, evidence out

From signup to your first validated record is about two minutes. The sequence below is the whole product.

STEP 01

Write what “valid” means

A contract is plain YAML — readable by your engineers, your auditors, and your AI. Start from 40+ samples or write your own.

# customer_profile.yaml rules: - field: email type: email_format - field: balance type: non_negative
STEP 02

Put the engine in the write path

Call it from your pipeline over HTTPS, or let your AI assistant call it over MCP. Same engine, same contracts, same audit trail.

curl -X POST \ https://<your-engine>/api/v1/validate \ -d @record.json # → valid: false, rules: [...]
STEP 03

Promote with evidence

Watch observation counts on live traffic, then flip the contract to enforcement — one deliberate action, recorded on the chain like everything else.

contract: customer_profile mode: observation → enforcement # 7-day evidence: 220 would-block # promoted by: you, on the record
Built on an open standard

Your contracts are portable by construction

OpenDQV Core is the MIT-licensed open-source project that defines the contract format. OpenDQV Cloud runs those same contracts on a managed engine — so the rules you write here run anywhere the standard runs.

If you leave, your YAML goes with you. That is the point of a standard — and the reason you can adopt one without asking permission first.

OpenDQV Core on GitHub →

the portability promise
contracts  → plain YAML, exportable any time
audit log  → exportable any time, API or dashboard
records    → never stored by the service
lock-in    → none by design
Pricing you can read

The prices on the page are the prices

Metered on engine uptime, like the compute you already buy. No sales call at any self-serve tier. No minimum commitment, no termination fee.

Trial
Free

14 days or 200 engine-hours, whichever comes first. One XS engine, every feature that runs on it. No credit card.

Start free trial
Standard
£5 / ODU + VAT

Pay for the engine while it is running. Per-second billing, 60-second minimum per start. Stop the engine and the meter stops. Sizes XS–S.

Upgrade in-product
Enterprise
£8 / ODU + VAT

Same uptime billing, engine sizes to L (8 vCPU), SSO (OpenID Connect), 365-day audit retention, continuous-run pinning, direct support.

Upgrade in-product
VPS
from £13 / ODU · POA

Everything in Enterprise, on your own substrate, inside your own network. This one is a conversation — the only one.

Talk to the founder

1 ODU = one vCPU-hour of engine uptime. Larger engines meter at their vCPU multiple. Observation mode costs the same as enforcement — the meter is the engine being on, not what you ask of it. Trial → Standard → Enterprise is entirely self-serve.

Put the bouncer on the door

Your first validated record,
about two minutes from now.

Signup → engine provisioned → sample validated. Tell us what breaks — the founder reads every reply.

Start free trial
Questions

Get to know OpenDQV Cloud

What is a data contract?
A plain-YAML statement of what “valid” means for a dataset — field by field, rule by rule. Contracts are versioned, auditable, human-readable, and yours: author them in the dashboard, in YAML, or let your AI assistant draft one.
What happens to the records I validate?
They are processed in memory and never stored in your audit trail, backups, or logs. Only the decision — pass, would-block, or blocked, with rule names and hashes — is recorded. Full detail in the Privacy Policy and DPA.
Where does my data live?
In the cloud region you select at signup — AWS, Azure, or Google Cloud, UK, EU, or US today — and never anywhere else. The region is your choice and it is fixed for the life of your account.
Can my AI assistant use it?
Yes — natively. Every contract, metric, audit event and validation is exposed over MCP, the open protocol MCP-compatible assistants speak. Connect once and “what failed last week?” is a sentence, not a dashboard safari.
What does it cost to try?
Nothing. The trial is 14 days or 200 engine-hours, whichever comes first, with no credit card. After that, Standard is £5 per engine vCPU-hour (+ VAT), metered per second, and the engine stops itself when idle.