Data Contract CLI: Review, Pricing & Features
Everything you need to evaluate Data Contract CLI for data contracts: what it is, my review, pricing, features, integrations and the best alternatives.
By Ari Bajo - data engineer turned writer.
Updated on November 13, 2026
- Product
- Data Contract CLI
- Category
- Shift-left data quality
- Pricing
- Free, open source
- Paid version
- Entropy Data
- Deployment
- Self-hosted
On this page
What is Data Contract CLI?
Data Contract CLI is an open-source command-line tool to lint, test, import, and export data contracts based on the Open Data Contract Standard, maintained by the team behind Entropy Data. It's used to test data against data contracts in CI/CD.
Data Contract CLI review
Data Contract CLI is the best open-source data contracts tool for data engineers who want to test data in Snowflake, Databricks, BigQuery, Kafka, and more against ODCS data contracts in CI/CD.
Strengths
- Free under MIT and built on the open ODCS standard.
- One command tests a contract against 20+ platforms, from Snowflake to Kafka.
- Flags breaking changes between contract versions in CI.
Caveats
- Command line only: no UI, catalog or approval workflow.
- No scheduling or alerts: you run it from CI or an orchestrator.
- You write and maintain the YAML contracts yourself.
Data Contract CLI pricing
Data Contract CLI is free under the MIT license. Entropy Data, from the same team, sells the managed data contract and marketplace platform.
Checked November 2, 2026 on the GitHub repository.
Data Contract CLI features
Data Contract CLI appears in my lists of the best data contracts, data testing and open-source tools. It supports 19 of the 63 tracked data quality features.
Data Contract CLI data testing
Compare: data contracts tools · data testing tools
SQL Table Tests: Quality rules check row count, nulls, duplicates, missing and invalid values with thresholds, and SQL rules compare any query result to a threshold (docs).
DataFrame Tests: The Python API tests Spark DataFrames registered as temporary views (docs).
Unstructured Data Tests: Validates records from JSON files and HTTP APIs against the contract's JSON Schema; there are no LLM checks (docs).
Data Contracts: Built for data contracts: datacontract test checks a data source against an Open Data Contract Standard (ODCS) YAML file with schema, quality rules and SLAs (docs).
Inspect Failed Rows: The --include-failed-samples flag returns a sample of failing rows, leaving out sensitive columns (docs).
Table Comparison Tests: No command compares aggregates between two tables; changelog and breaking compare two contract files (docs).
Data Diff: Compares contract versions, not data rows (docs).
Data Contract CLI data observability
Freshness Monitors: A freshness SLA in the contract is checked on each test run — a one-off check, not a continuous monitor (docs).
Volume Monitors: A rowCount rule checks row count on each test run — a one-off check, nothing is tracked over time (docs).
Schema Monitors: Each test run fails when a contract field is missing or its type changed — a one-off check, not a continuous monitor (docs).
Custom SQL Monitors: SQL quality rules run on each test run and compare the result to a threshold — one-off checks, not tracked over time (docs).
Partition-Based Monitors: The --filter option limits a test run to rows matching a predicate, such as the latest batch (docs).
Monitors-as-Code: Checks live in ODCS YAML files kept in Git, reviewed in pull requests and tested from the command line (docs).
UI-Based Monitors: The edit command opens a web editor for the contract file; whether every check can be set up there is not documented (docs).
Data Profiling: No profiling command (docs).
Anomaly Detection: Thresholds are fixed values in the contract (docs).
Field Monitors: Column statistics are not stored over time (docs).
Distribution Monitors: No distribution metrics (docs).
Segment Monitors: No group-by checks (docs).
Window-Based Monitors: No time-window metrics (docs).
Pipeline Monitoring: No pipeline monitoring (docs).
Data Contract CLI data governance
Data Catalog: The catalog command builds an HTML page of contract files; whether it works as a searchable catalog is not documented (docs).
Data Catalog Integration: Reads schemas from catalogs on import, but does not push results to them (docs).
Data Classification: No PII detection (docs).
Data Products: Results are per contract; data products are an Entropy Data feature (docs).
Data Contract CLI workflows
CI/CD Integrations: The ci command runs tests in pipelines, writes GitHub Actions annotations and fails the build on errors (docs).
Circuit Breakers: The Python library's test() returns a run whose has_passed() result the docs use to abort the pipeline in Airflow, Dagster or Prefect (docs).
Webhooks: The --publish option posts test results to a URL, typically Entropy Data (docs).
REST / GraphQL API: datacontract api runs a REST API with test, export, changelog and breaking endpoints (docs).
Python SDK: The DataContract Python class runs test, lint, import, export and breaking, and returns results with has_passed() (docs).
dbt Integration: Imports contracts from a dbt manifest, exports dbt models and sources, and syncs contract tests into a dbt project (docs).
Scheduling: No built-in scheduler; the docs say to run it from cron, GitHub Actions or Airflow (docs).
MCP Server: No MCP server; agents use Agent Skills and llms.txt instead (docs).
Data Contract CLI AI agents
Automated Test Generation: The import command builds a contract, with schema checks, from an existing SQL, dbt, BigQuery, Glue or Snowflake schema (docs).
AI Chat Assistant: No chat (docs).
Natural Language Test Generation: Contracts are YAML; separate agent skills can write checks from plain English (docs).
AI Issue Triaging: No AI features in the CLI; separate agent skills can explain failures (docs).
AI Issue Resolution: No AI fixes in the CLI (docs).
Not covered: Incident management · Data quality analytics · Data lineage · FinOps · LLMOps
Data Contract CLI integrations
Data Contract CLI lists 18 integrations in total.
- Data Warehouse: Snowflake, Google BigQuery, Databricks SQL, Amazon Redshift, DuckDB, Oracle DB, ClickHouse
- Databases: PostgreSQL, Microsoft SQL Server, MySQL
- Data Storage: Amazon S3, Azure Blob Storage, Azure Data Lake Storage, Google Cloud Storage
- Query Engine: Trino, Amazon Athena
- Streaming: Apache Kafka
- Data Transformation: Apache Spark
Data Contract CLI deployment options
Data Contract CLI is a Python package you run locally, in CI or from an orchestrator. For a UI and a data product marketplace on top, Entropy Data runs as SaaS or self-hosted.
Self-Hosted Deployment: Installs with pip or Docker and runs locally, in CI, or as a REST API server (website).
SaaS Deployment: Software you run yourself; Entropy Data is the hosted platform (docs).
Hybrid Deployment: No vendor control plane (docs).
Cloud-Native App: A Python package, not a native app in Snowflake or Databricks (website).
Data Contract CLI security
Data Contract CLI alternatives
The closest Data Contract CLI alternatives and most popular competitors are Soda Core, Entropy Data, dbt tests, Confluent Data Contracts, OpenMetadata and Great Expectations. They share Data Contract CLI's main use cases and features, from the closest match down. The Data Contract CLI alternatives page compares their pricing, deployment and features, and says when to choose each one instead.
For a UI, approvals and a data contract marketplace, consider Entropy Data, from the same team. For contracts enforced on Kafka messages, Confluent Data Contracts; for YAML checks without the contract standard, Soda Core.
- 1. Soda CoreData Contract CLI vs Soda Core
- 2. Entropy DataData Contract CLI vs Entropy Data
- 3. dbt tests
- 4. Confluent Data Contracts
- 5. OpenMetadataData Contract CLI vs OpenMetadata
- 6. Great Expectations
Data Contract CLI FAQ
Is Data Contract CLI open source?
Yes. Open source under the MIT license.
How much does Data Contract CLI cost?
Data Contract CLI is free under the MIT license. Entropy Data, from the same team, sells the managed data contract and marketplace platform.
Can Data Contract CLI be deployed on-premise?
Yes. Data Contract CLI is a Python package you run locally, in CI or from an orchestrator. For a UI and a data product marketplace on top, Entropy Data runs as SaaS or self-hosted.
What are the best Data Contract CLI alternatives and competitors?
The closest alternatives are Soda Core, Entropy Data, dbt tests, Confluent Data Contracts, OpenMetadata and Great Expectations. The Data Contract CLI alternatives page compares their features and pricing and says when to choose each one over Data Contract CLI.
Browse all 102 tool profiles, grouped by category.
Evaluating data tools in 2026?
I curate the most comprehensive lists of data tools, up-to-date comparison tables, and actionable market guides for data teams. More useful than a Gartner report. More reliable than asking AI. Next up: Data FinOps.