Bad data stops before the warehouse
Expectations, schema contracts and redaction run on the way in. Analytics engineers hear about a broken source at the pipeline that loaded it, while the fix is cheap and the warehouse is still clean.
Checks, contracts and redaction
Quality governs the values, contracts govern the shape, and redaction governs what is allowed to land at all. All three run in the pipeline rather than in a dashboard downstream.
Data quality
Declare expectations once. Rows that fail are quarantined before they reach the warehouse, per dataset, table or row.
Checked per dataset, table or row
Contracts
Declare what the warehouse is allowed to receive. Schema changes are accepted, blocked or quarantined by rule, on the run that introduced them.
| Schema change | Dataset | Contract says | |
|---|---|---|---|
| Column added: discount_pct | orders | Allowed, added | |
| Type changed: amount | orders | Blocked, run halted | |
| Table added: refunds | finance | Allowed, added |
Redaction
Mark a column as sensitive and it is redacted before the load, so the raw value never lands in the warehouse.
Explore the rest of dltHub
Managed infrastructure
Scheduling, instance sizes, observability and the CLI, with nothing to keep warm between runs.
See the platformTransformations
Annotate your sources, generate the canonical model, and keep your dbt models running.
See the modelsAI harness
The skills, commands and MCP servers your coding agent calls to build and fix pipelines.
See the harnessSecurity and compliance
Access controls, credential handling, encryption, data residency and audit, with the control set published.
See the controlsPricing
Pick a machine size per job and pay by the second, with the meter running only while the job does.
See pricing
