drt vs Weld
drt
github.com
Weld
weld.appSide by side
| Figure | drt | Weld |
|---|---|---|
| Price from | Free | $99/mo |
| Free plan | Yes | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | — | Yes |
| Self-hosted | Yes | — |
| Plans published | 1 | 4 |
| Spec score · Reverse ETL Tools | 8.1 (#9) | 7.7 (#14) |
| Connectors | The project lists 13 sources and 34 destinations, including BigQuery, Snowflake, Postgres, Slack, and Salesforce. | The connector directory lists 300+ prebuilt connectors and supports custom connectors. |
| Purpose | drt moves modeled warehouse data into team tools as reverse ETL, with syncs defined in YAML and versioned in Git. | Weld moves data from sources into warehouses and back into business tools for analytics, AI and operational workflows. |
| Security | The security policy describes Dependabot, CodeQL, pip-audit, and CycloneDX SBOM generation for releases. | Weld says it uses TLS 1.2+ in transit, strong encryption at rest, least-privilege access and audited controls. |
| 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. | Support tiers listed by plan are basic for Basic, premium for Premium, priority for Business and Enterprise, with a customer success manager on Enterprise. |
Plans
Weld
- Basic$99 a month
- Premium$389 a month
- Business$959 a month
- EnterprisePriced 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.