dbt Cloud vs dbt Core cost: paying for convenience or running it yourself

Quick answer

dbt Core is free and open source: you pay nothing for the tool but must run, schedule, and host it yourself (via your own orchestrator, CI, and compute). dbt Cloud is a paid managed service billed per developer seat (plus usage on higher tiers) that adds a hosted IDE, scheduling, CI integration, documentation hosting, and collaboration. The real comparison is subscription fees plus lower operational burden (dbt Cloud) versus zero license cost plus your own engineering time to build and maintain orchestration (dbt Core). Neither includes your data warehouse compute, which you pay for separately either way.

dbt (data build tool) comes in two flavors with very different cost models. dbt Core is the free, open-source command-line tool. dbt Cloud is a commercial managed service built around it. Choosing between them is a classic build-versus-buy decision: pay a subscription for convenience, or run it yourself and pay in engineering time and infrastructure.

What each costs

Aspect	dbt Core	dbt Cloud
License	Free, open source	Paid, per developer seat (plus usage on higher tiers)
Orchestration	You build it (Airflow, cron, CI)	Built-in scheduler
Compute to run dbt	Your own (CI runners, a VM)	Included in the service
IDE and docs hosting	Local, self-hosted	Hosted IDE and docs
Warehouse compute	You pay separately	You pay separately

Crucially, neither includes the cost of the warehouse that actually runs your SQL, that is your data warehouse compute (Snowflake, BigQuery, Redshift, Databricks), and it is usually the largest data-stack cost regardless of which dbt you use. The dbt decision is only about the tooling and orchestration layer on top.

The dbt Core cost: your time and infrastructure

dbt Core has no license fee, but running it in production is not free. You need somewhere to schedule and execute dbt runs (an orchestrator like Airflow, a CI pipeline, or a small always-on runner), CI to test changes, a place to host documentation, and the engineering time to build and maintain all of it. For a team that already runs CI/CD and an orchestrator, that marginal cost is small; for a team starting from scratch, it is real engineering work.

The dbt Cloud cost: seats and usage

dbt Cloud is billed primarily per developer seat, with a free tier for a single developer and paid team and enterprise tiers that add seats, features (governance, more environments), and on higher tiers usage-based charges. You are paying for the hosted IDE, the scheduler, CI integration, docs hosting, and not having to operate any of it. For small teams the seat cost can be modest; for large teams with many developers, seat fees add up and the ROI depends on how much operational burden it removes versus what self-hosting would cost you.

How to choose on cost

Choose dbt Core when you have the platform engineering to run orchestration yourself and want to avoid per-seat fees at scale, or when your team is small enough to run dbt from existing CI cheaply. Choose dbt Cloud when the convenience (scheduling, IDE, collaboration, no ops) is worth the subscription, or when you lack the engineering capacity to build and maintain the surrounding infrastructure. Either way, keep your eye on the warehouse bill, which dwarfs both, and price your data infrastructure before you commit. See the resource catalog for how the underlying compute is priced.

FAQ

Is dbt Core free?

Yes, dbt Core is free and open source, with no license fee. But running it in production is not free: you must provide your own scheduling and orchestration (Airflow, cron, or CI), compute to execute runs, documentation hosting, and the engineering time to build and maintain all of it. For teams that already run CI and an orchestrator the marginal cost is small; from scratch it is real work.

How is dbt Cloud priced?

dbt Cloud is billed primarily per developer seat, with a free tier for a single developer and paid team and enterprise tiers that add seats, features, and on higher tiers usage-based charges. You pay for the hosted IDE, built-in scheduler, CI integration, documentation hosting, and not having to operate any of it yourself. Costs scale with the number of developers who need seats.

What is the cost difference between dbt Cloud and dbt Core?

dbt Cloud is a subscription (per seat plus usage on higher tiers) that removes operational burden; dbt Core has zero license cost but requires you to build and maintain orchestration, CI, and hosting yourself, paying in engineering time and infrastructure. Neither includes your data warehouse compute, which you pay separately either way and which is usually the largest data-stack cost.

Does dbt include the cost of running queries?

No. Neither dbt Core nor dbt Cloud includes the cost of the data warehouse that actually executes your SQL. That warehouse compute (Snowflake, BigQuery, Redshift, or Databricks) is billed separately by your provider and is typically the largest data-stack cost regardless of which dbt you use. The dbt choice only affects the tooling and orchestration layer above the warehouse.

When is dbt Cloud worth the cost?

When the convenience (hosted scheduling, IDE, CI integration, collaboration, and no operations) is worth the per-seat subscription, or when your team lacks the platform engineering capacity to build and maintain the surrounding infrastructure for dbt Core. For large teams with many developers, seat fees add up, so the ROI depends on how much operational cost it saves versus self-hosting.

How does C3X relate to dbt cost?

C3X prices the cloud infrastructure behind your data stack (the warehouse, compute, and orchestration resources) from Terraform before deploy. While it does not price dbt seats, it surfaces the warehouse and infrastructure cost that dominates the total, helping you keep the largest part of data-stack spend visible at design time whichever dbt flavor you choose.

What to do next

Keep the largest part of your data-stack cost visible before deploy. C3X prices your resources against a live catalog. Start with the quickstart.