drt vs Hightouch
drt
github.com
Hightouch
hightouch.comSide by side
| Figure | drt | Hightouch |
|---|---|---|
| Price from | Free | $350/mo |
| Free plan | Yes | Yes |
| Free trial | — | Yes |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| iOS | — | Yes |
| Android | — | Yes |
| API | — | Yes |
| Self-hosted | Yes | — |
| Plans published | 1 | 9 |
| Spec score · Reverse ETL Tools | 8.1 (#9) | 9.0 (#4) |
| Intended users | The site describes drt as suited to teams that ship with dbt and Git and want reverse ETL pipelines managed in their repository. | Hightouch says it serves enterprise marketing teams and is designed to help them activate customer data using AI and existing data infrastructure. |
| Security | The security policy describes Dependabot, CodeQL, pip-audit, and CycloneDX SBOM generation for releases. | Hightouch states it does not store customer data, runs queries directly on the customer’s warehouse, and transfers data to destinations without storing it. |
| Support | The security policy asks vulnerability reports to be emailed and says receipt is acknowledged within 48 hours, with critical fixes or mitigations within 7 days. | Composable CDP plans list dedicated expert support, and the pricing page describes dedicated Slack, a dedicated customer success manager, onboarding, and custom support SLAs. |
Plans
Hightouch
- FreeFree
- Self-servePriced on request
- Basic Reverse ETLFree
- FreeFree
- Starter$350 a month
- Pro$800 a month
- Agentic Marketing PlatformPriced on request
- BusinessPriced on request
- Composable CDPPriced on request
In their own words
drt
drt is a free reverse ETL tool for moving modeled warehouse data into team tools. Teams define syncs in YAML, version them in Git, install drt-core with pip, and run jobs from the terminal. A dry run with a diff previews rows due to be added, updated, or deleted before writing. The project lists 13 sources and 34 destinations, including BigQuery, Snowflake, Postgres, Slack, and Salesforce, across warehouses, SaaS APIs, cloud storage, files, and webhooks. drt can read dbt projects and use `ref()` models to follow model lineage. Its listed orchestration integrations include Dagster, Prefect, Airflow, and a dbt manifest reader; a GitHub Action supports scheduled or event-triggered syncs. An optional MCP server lets compatible clients validate configuration, run syncs, list them, and inspect status. Data moves directly from the user's warehouse to the destination without a drt-hosted intermediary. Syncs are batch-based, the core is self-hosted, and the project is licensed under Apache 2.0. RBAC, audit logging, plugins, and managed cloud hosting are outside drt-core.