What it does
dbt is the industry-standard SQL transformation layer for the modern data stack. Data lands in a warehouse (Snowflake/BigQuery/Redshift/Databricks/Postgres) via a tool like Fivetran or Airbyte. dbt takes over from there: analysts write modular SELECT statements as "models," dbt handles dependencies, incremental builds, testing, and documentation. It brought software engineering practices — version control, code review, tests, CI/CD, docs — into analytics. Two forms: dbt Core (open source, MIT-licensed CLI, free) and dbt Cloud (managed IDE, orchestration, semantic layer, CI, hosted docs, priced per developer seat + usage).
Free tier
Yes
Starts at
$100/mo
Setup
hard
Key features
Integrates with
Snowflake, BigQuery, Redshift, Databricks
Who this fits
- Data/analytics engineering teams building on Snowflake, BigQuery, Redshift, or Databricks
- Companies with 3+ analysts collaborating on transformations who need version control and tests
- Any organization moving from "one giant SQL spreadsheet of dashboards" to a modeled warehouse
- SaaS/ecommerce/B2B companies with a real analytics stack and a real data team
- Consultants and data agencies delivering warehouse projects
Who it does NOT fit
- Solo, small teams with 1 analyst (dbt Core alone works but is often overkill for one person)
- Businesses without a cloud data warehouse (no warehouse = no dbt)
- Teams doing purely ad-hoc SQL with no reused logic (dbt's value is DRY + tests + docs)
- Non-technical shops (dbt assumes comfort with SQL, Git, YAML, and a CLI or IDE)
Pricing
Real gotchas
- dbt Cloud's shift to hybrid seat + usage pricing means the seat cost is not the whole bill. Successful model builds meter usage, and unoptimized builds/CI runs cost money (Source: Paradime: https://www.paradime.io/guides/dbt-cloud-pricing)
- Team tier at $100/dev/mo has a real jump to Enterprise. The gap is where mid-size teams get stuck comparing to Paradime, dbt Cloud, or self-hosted Core + Airflow/GitHub Actions
- dbt Core is free but you own the orchestration — someone has to build the Airflow/Dagster/GitHub Actions pipeline. Not free in time
- The semantic layer (Metric definition, dbt-hosted API for BI tools) is Team+ and adoption is still uneven across BI tools
- Successful-model-build metering means CI runs (test-every-PR) can rack up usage credits fast; check the CI pattern before committing to Cloud
- Cross-project references (mesh) is an Enterprise feature and central to multi-team dbt adoption
- Some connectors and adapters lag behind Core; verify your warehouse+dbt version compatibility before upgrading
Integrations that matter
Otto’s take on this tool
Recommend dbt when: user has a cloud warehouse (Snowflake/BQ/Redshift/Databricks), has 3+ analysts collaborating, and needs modeled/tested/documented transformations. Highest fit for B2B SaaS, mid-market ecommerce with a data team, and analytics consultancies. Do NOT recommend for solo, no-warehouse, or non-technical teams. If comparing to Fivetran Transformations or in-warehouse stored procs: dbt wins on git-native workflow, testing, docs, and community. If comparing to Coalesce/Paradime/SQLMesh: dbt is the safe default with the biggest community; alternatives win specific niches (SQLMesh on virtual environments, Paradime on cost + Cloud parity). Flag the hybrid seat+usage pricing so nobody quotes only the $100/seat number.
Affiliate disclosure: if you sign up through the link above, Ottomately may earn a referral commission at no cost to you. We only feature tools we have actually used or vetted through our recommendation engine.
More in Productivity
Not Sure dbt is Right?
Otto can pick for you.
30 seconds, one form, get a personalized stack with pricing and integration paths.
Get my recommendations