drt

Overview

drt is a self-hosted tool for moving modeled warehouse data into the apps a team uses, with sync definitions kept in YAML and Git. It is best suited to teams already building with dbt and repository-based workflows. Its appeal is a free, inspectable batch process; your team remains responsible for running and hosting it.

Install drt-core with pip and run syncs from the terminal. A dry run with a diff previews rows that would be added, updated, or deleted before any write, giving teams a useful review point for changes.

Key features

drt lists 13 sources and 34 destinations across warehouses, SaaS APIs, cloud storage, files, and webhooks. Named connectors include BigQuery, Snowflake, Postgres, Slack, and Salesforce. That covers a range of common warehouse-to-tool flows, though the connector count alone does not guarantee a particular endpoint or operation will fit; check the connectors your pipeline needs.

For dbt users, drt can read a project and use ref() models so activations follow model lineage. Documented integrations include Dagster, Prefect, Airflow, and a dbt manifest reader. A GitHub Action supports scheduled or event-triggered syncs and structured status outputs, making drt a natural fit for teams that already manage data work in repositories and CI/CD.

The optional MCP server allows compatible clients to list syncs, run them, validate configuration, and inspect status. This can bring routine operations into an AI-enabled client, but it is optional and requires a compatible client. Data moves directly from the user's warehouse to the destination rather than through a drt-hosted intermediary. Telemetry is off by default; if enabled, it collects sync metadata and excludes sync names, SQL, destination URLs, credentials, and project paths.

The project describes Dependabot, CodeQL, pip-audit, and CycloneDX SBOM generation for releases as part of its security practices. Its vulnerability reporting policy asks for reports by email, acknowledges receipt within 48 hours, and targets critical fixes or mitigations within 7 days. The Apache 2.0 license makes drt-core open source. Teams needing RBAC, audit logging, plugins, or managed cloud hosting should account for those features sitting outside drt-core.

Pricing

drt-core: free. The free plan includes all connectors, the sync engine, CLI, MCP server, and self-hosted deployment. That is a substantial starting point for teams able to operate the tool themselves, with no paid tier required for the core listed capabilities. Its limits are operational and functional: syncs are batch, reverse sync is unavailable, and RBAC, audit logging, plugins, and managed cloud hosting are outside the core plan.

Platforms

drt supports Linux, macOS, and Windows, and is self-hosted. The pip installation and terminal workflow suit teams comfortable running command-line software on their own infrastructure.

Who it's for

Choose drt if your team ships with dbt and Git, wants reverse ETL definitions versioned alongside its project, and can own deployment and operations. The preview-before-write workflow is especially useful when you want to inspect proposed row changes before a sync applies them. Look elsewhere if you need reverse sync, managed hosting, or the enterprise controls excluded from drt-core.

Pros and cons

• Pros: The free core includes all connectors, the sync engine, CLI, and MCP server, so teams can build a self-hosted workflow without a paid plan.
• Pros: Dry-run diffs preview additions, updates, and deletions before writes, giving reviewers a concrete check on sync effects.
• Pros: dbt lineage, orchestration integrations, and a GitHub Action connect syncs to familiar repository and pipeline workflows.
• Cons: Batch syncs and no reverse sync make it unsuitable for workflows that need continuous updates or data flowing back from destinations.
• Cons: Self-hosting puts deployment and operations on the team, and RBAC, audit logging, plugins, and managed cloud hosting are outside drt-core.

Alternatives

Compare reverse ETL tools if you want to weigh drt against other options in the category.

RudderStack Customer Data Platform is a candidate if you want a broader customer data platform with Android and iOS support, a free plan covering 250K events per month, 16 SDK sources, and more than 200 cloud destinations.

Clay may fit better when lead enrichment is the priority: its free plan includes 500 actions per month, 100 data credits per month, unlimited seats and tables, and up to 200 rows per table.

Singular offers a free, conversion-billed option with 15,000 paid conversions and no credit card required, making it worth considering when that pricing model fits your needs.

Bitscale has a free plan with 200 credits, 2,000 monthly company or people searches, and 50,000 rows per grid; consider it if those research and grid limits match your workflow.

DataChannel offers a free tier with 1 million rows per month, two data sources, five user accounts, and 20 transformations, which may suit teams looking for a row-based data workflow.

Dataflowz is another option with a free Starter plan that includes one warehouse connection, three destination connections, 10K rows synced per month, and daily syncs.

Fastero has a free tier limited to public apps and 1 GB RAM per app, with paid plans from $20 a month for compute tiers up to 16 GB RAM per app.

Fivetran Database Replication may be worth comparing if its free-plan quotas—500,000 monthly active rows for connections, 3,500 for activations, and 5,000 monthly model runs for transformations—fit your workload.

Verdict

drt is a strong fit for dbt and Git-oriented teams that want a free, self-hosted way to manage batch reverse ETL, with lineage-aware syncs and a preview before writes. The case for choosing it is control over repository-managed pipelines without a software charge. The case for looking elsewhere is equally clear: it has no reverse sync, and drt-core leaves managed hosting and enterprise controls to other offerings.