dbt-expectations vs Great Expectations.
dbt-expectations and Great Expectations both anchor in quality & testing — 7 dimensions differ, 4 hold. Below: posture, coverage diff, and capability matrix.
What each is betting on.
Apache-2.0 dbt package, not a company. The original repo (calogica/dbt-expectations) was marked no longer maintained on 2024-12-18; active development forked to metaplane/dbt-expectations and the dbt Package Hub listing now publishes under the `metaplane` namespace (latest 0.10.x, dbt Fusion-compatible). Metaplane was itself acquired by Datadog (announced 2025-04-23). The package remains free and Apache-2.0 — it was never sold or made proprietary.
Acquired May 2026 (acquirer not publicly named in the May 6 community update). GX Cloud announced as discontinued June 1, 2026 — the team is being absorbed into the acquirer's platform. GX Core (Apache-2.0) continues under new stewardship; the OSS path is the only continuing option pending the new stewards' roadmap.
Each tool's current strategic narrative, verbatim from its profile.
How each tool describes the other.
dbt-expectations is a dbt package — a library, not a platform. It ports the assertion style popularised by the standalone Great Expectations framework into native dbt generic tests: 50-plus pre-built checks, declared in dbt YAML, that compile to SQL and run inside dbt test or dbt build against your own warehouse. The library spans row-count and volume checks, freshness windows, schema-shape assertions, value ranges and sets, regex and LIKE pattern matching, and distributional bounds (mean, median, standard deviation, quantiles, and N-standard-deviation envelopes).
Great Expectations's page doesn't directly mention dbt-expectations. See the Great Expectations detail page.
Each quote is pulled from the named tool's own "Where it fits" write-up.
Spec sheet diff.
| dbt-expectations | Great Expectations | |
|---|---|---|
| Vendor | Metaplane (Datadog) | Great Expectations |
| Deployment | Self-hosted only | SaaS · Self-hosted |
| Pricing | OSS · paid tiers | OSS · free |
| dbt integration | Native | None |
| Founded | 2020 | 2017 |
| Status | ● active | ○ acquired |
| Authoring style | YAML | Python |
Both share Primary cluster: Quality & testing · License: Open source · Free tier: Yes · OSS self-host: Yes · OpenLineage: None · Test paradigm: Assertion-based
Each tool's center of gravity.
| Cluster | dbt-expectations | Great Expectations |
|---|---|---|
| Quality & testing | 3/3primary | 3/3primary |
| Catalog & discovery | 0/3 | 0/3 |
| Lineage & metadata | 0/3 | 0/3 |
Scored 0–3 per cluster on the same rubric across all tools. A 0 means the cluster isn't the tool's focus, not that the feature is absent. See the methodology.
Where they cover different ground.
The declared feature set.
1 of 4 declared features differ — listed first.
These are each tool's self-declared key_features; a blank dot means
undeclared, not impossible.
| Feature | dbt-expectations | Great Expectations |
|---|---|---|
| dbt-Native Testing Quality & testing | ||
| Assertion-Based Testing Quality & testing | ||
| Schema Change Detection Quality & testing | ||
| Warehouse-Native Monitoring Quality & testing |
Where they disagree.
Quality & testing
5 of 13 differ| dbt-expectations | Great Expectations | |
|---|---|---|
| dbt-native | ||
| Pre-merge diffing | ||
| Freshness | ||
| Circuit breaker | ||
| Column profiling |
When to pick each.
dbt-centric analytics-engineering teams that already run dbt test in CI and want a broad library of declarative, in-warehouse assertions — value ranges, regex and pattern matching, schema shape, and distributional bounds (mean, median, stdev, quantiles) — with zero added cost or infrastructure. It is the natural first step up from dbt's four built-in tests (unique, not_null, accepted_values, relationships) for a team that wants richer checks without leaving the dbt workflow.
Python-first data engineering teams who treat data quality as a software engineering problem and want their tests to live in the same repository, version control, and CI as their pipeline code. GX Core remains the most mature OSS data-validation framework — Apache-2.0, deeply embedded in Airflow, Dagster, and Prefect operators, and supported by roughly 300 built-in Expectations covering schema, value distribution, statistical, and multi-column relationships. Particularly well-suited to healthcare, financial-services, and other regulated buyers who need pure-OSS, on-prem deployment with no SaaS dependency, since the project is permissive Apache-2.0 with no copyleft or relicensing risk.
What each does best.
dbt-expectations stands out for
- Free and Apache-2.0 with no paid tier, no SaaS, and no lock-in — the only cost is your own warehouse compute
- A library of 50+ assertions far beyond dbt's four built-ins (value ranges, regex, schema shape, distributional bounds)
- Fully native to dbt — declared in YAML, run by dbt test / dbt build, inheriting dbt severity levels, CI, and run artifacts; the current fork release is dbt Fusion-compatible
- Push-down execution across Postgres, Snowflake, BigQuery, DuckDB, Spark, and Trino
Great Expectations stands out for
- Largest open-source data-validation community by stars and contributors, with deep first-party Airflow, Dagster, and Prefect operator support
- Apache-2.0 license with permissive reuse — no source-available games, no rug-pull risk on the OSS path
- Roughly 300 built-in Expectations cover schema, distribution, statistical, and multi-column relationships — the broadest assertion library in the cluster
- Data Docs auto-generate human-readable validation results that non-engineering stakeholders can actually read
Tools both also compete with.
A note on this comparison.
Every capability value above traces to dbt-expectations or Great Expectations's own structured spec, which links back to its source — nothing here is averaged or smoothed across the two.
Notice something inaccurate? Send a correction.