No lock-in. Your config is portable YAML.
AnomalyArmor speaks the Open Data Contract Standard. Every asset's freshness SLAs, validity rules, drift monitors, and alert routing export as portable YAML you can diff in Git, import into any ODCS tool, or hand to the next vendor. The exit plan is one command.
apiVersion: v3.1.0
kind: DataContract
id: 53581432-6c55-4ba2-a65f-72344a91553a
name: orders_contract
version: 1.0.0
status: active
domain: ecommerce
schema:
- name: orders
physicalName: public.orders
properties:
- name: order_id
logicalType: string
required: true
unique: true
quality:
- id: order_id_no_nulls
metric: nullValues
mustBe: 0
slaProperties:
- property: latency
value: 24
unit: h
element: orders.created_at
team:
- username: [email protected]
role: ownerThe Problem: Monitoring Config Is Trapped
Most data-quality tools keep your checks, thresholds, and alert routing inside their own database. Portability is a nice-to-have. Until you need it.
Vendor Lock-in
Every bespoke YAML format is a private dialect your next tool will not read. Leaving becomes a rewrite.
Config Lives in a Settings Page
Screenshots in PR descriptions are not a code review. Changes to monitoring rules do not diff, do not get reviewed, do not get rolled back.
Migration is Always a Rewrite
Moving off your current observability tool means rebuilding every check, every rule, every alert from scratch.
How AnomalyArmor Solves This
ODCS export and import are a first-class feature, not a future roadmap item.
Standards-Based YAML
AnomalyArmor reads and writes the Open Data Contract Standard (ODCS v3.1.0), a Linux Foundation project. Same format Soda, Great Expectations, and dbt understand.
Export Any Time, Click or CLI
Every asset or the whole warehouse exports as portable YAML. Run `armor contract pull --all` to get every contract in your account as a zip. No tickets, no waiting.
Import from Your Existing Tools
Soda ships ODCS export natively. We ship adapters that translate dbt projects into ODCS. One pipeline feeds them all into your AnomalyArmor asset.
Review Config in Pull Requests
Check contracts into Git. Reviewers see which validity rule changed, which freshness SLA tightened, which alert routing moved. Monitoring becomes code.
Migrate in two commands.
Soda ships ODCS export natively. Export once, apply to AnomalyArmor, and your existing monitoring runs without a rewrite. Or paste your YAML into our live preview without signing up first.
Use Cases
Leave Soda in Two Commands
Run soda export --odcs, then armor contract apply. Your existing monitoring lands in AnomalyArmor without rebuilding anything.
Contracts as Code
Store contracts alongside your dbt or airflow repo. Open PRs to change thresholds. Review diffs, not screenshots.
No Lock-in by Construction
Click Export, get a directory of YAML. Import it into whichever tool you pick next. The exit plan is one command.
Your config should travel with you.
Connect your warehouse, set up monitoring, export it all as YAML whenever you want.