Datafold is a commercial platform built on value-level data diffing: it compares the output of a proposed change against production in CI, validates parity during warehouse migrations, and monitors metrics for deviation, deployable as SaaS or inside the customer's own cloud.
Multi-tenant SaaS, or a dedicated cloud hosted by Datafold or by you, deployable into your own VPC on AWS, GCP, or Azure with PrivateLink, peering, allow-listing, or SSH tunnels. Fourteen databases and warehouses connect, with GitHub, GitLab, dbt, and Airflow on the code and pipeline side.
How Datafold answers the questions Data Quality turns on.
| How it works | |
| Authoring model | Very little: a diff needs two tables and a key rather than a rule, and the CI integration is either no-code or API-driven with a dbt-specific path beside it. Where assertions are genuinely wanted, monitors are declared in the UI or as Monitors as Code |
| Detection model | A diff between two versions of the data rather than a monitor over one, value-level comparison row by row and column by column, within a database or across two different platforms, so the question answered is what a change did to the numbers rather than whether today resembles yesterday. Metric monitors sit beside it for the conventional question |
| Built-in monitors | Four kinds beside the diff itself (metric monitors over row count, freshness, cardinality or any custom metric against automatic or manual thresholds; data test monitors that validate business rules and surface the records that failed; schema change monitors; and data diff monitors) each schedulable daily, hourly or by cron expression |
| Prevention or detection | Prevention, and at a point nothing else here occupies, the gate is the pull request rather than the pipeline. Every change is tested, diffed and validated in CI before it reaches production, so what it stops is a developer shipping a transformation that quietly changes numbers, not a job failing loudly at three in the morning |
| Lineage | Private beta, and not to be relied on yet, the Data Knowledge Graph gathers lineage, business logic, usage statistics and BI connections into one context layer, but it is enabled by contacting sales rather than generally available |
| Alerts and delivery | Slack, email, PagerDuty, webhooks and Microsoft Teams, attached to monitors on a schedule, with Slack alerts able to tag the groups or individuals who ought to see them |
| Incidents and ownership | Little by design: the finding arrives in the pull request or the alert channel, and there is no incident, owner or status of the kind the observability platforms here carry. The workflow it assumes is code review, not on-call |
| Running it | |
| What you run | Multi-tenant SaaS, or a dedicated cloud that Datafold hosts or the customer hosts and manages themselves, deployable into a VPC on AWS, GCP or Azure, with PrivateLink, VPC peering, IP allow-listing and SSH tunnelling as the connection options |
| Connections | |
| Connectors | Fourteen databases and warehouses (Snowflake, BigQuery, Athena, Redshift, Databricks, PostgreSQL, SQL Server, Oracle, MySQL, Dremio, SAP HANA, Starburst, Teradata and Netezza) with GitHub and GitLab on the code side and dbt and Airflow on the pipeline side |
| Cost | |
| Billing unit | Nothing published for the platform. The one priced artefact is the Migration Agent, sold at a fixed price with a timeline and data parity as the deliverable rather than metered, a professional-services shape rather than a software meter, and unique in this corpus |
Same headline facts as Datafold
vs Datafold: Open source (permissive) · Self-hosted · Free · Operational complexity: Low · Scala
vs Datafold: Open source (permissive) · Free · Subscription · Operational complexity: Low · Python