Transform hub

dbt on your warehouse — your project, our orchestration

eltPulse syncs data from your connectors, loads it into Snowflake, BigQuery, Postgres, or DuckDB, then runs your dbt project in the same pipeline run. Pick a staging package, scaffold to Git, and watch sync → load → transform in Runs. You keep models in your repo — we are not dbt Cloud.

Start free Technical docs

How it works

Sync — eltPulse extracts from your connector (API, files, or database replication) into the warehouse you chose.
Load — raw tables land in a dataset or schema ready for modeling.
Transform — your dbt project runs in the same pipeline run, using the same destination credentials.
Observe — runs show sync, load, and dbt phases separately in telemetry.

dbt v2 roadmap

Building toward managed handoffs between sync and transform without vendor lock-in.

Connector staging package picker
Scaffold dbt project to Git
Load → dbt run phases in telemetry
dbt on managed workers (GHA)
Manifest + model list on run detail
Canvas lineage (source → staging → marts)
Webhooks with dbt test failures
Post-replication dbt job type

Staging packages by connector

Curated transform packages that match eltPulse connectors — pick one below, then enable SQL transforms in the pipeline builder's Post-load transform section.

Loading packages…

Pair with connectors & scenarios

Start from a pipeline scenario, enable dbt in the builder, and export everything to Git.

Compare to Fivetran + dbt →