dbt Core is free and fully customizable. dbt Cloud adds IDE, scheduling, CI/CD, and governance. Choose Core for cost-conscious teams with DevOps skills; choose Cloud for productivity and enterprise features.
Introduction
dbt (data build tool) comes in two flavors: **dbt Core** (free, open-source CLI) and **dbt Cloud** (commercial SaaS platform by dbt Labs). Both use the same SQL-based transformation engine, but dbt Cloud adds a web IDE, job scheduling, CI/CD, documentation hosting, and enterprise governance features on top. The choice is essentially: build your own tooling around Core, or pay for Cloud's integrated experience.
Feature Comparison
Feature
dbt Core
dbt Cloud
Winner
Cost
Free and open-source
Free tier + paid plans ($100+/seat/month)
Tie
IDE
Use any editor (VS Code, vim)
Built-in web IDE with autocomplete
Tie
Scheduling
DIY (Airflow, cron, GitHub Actions)
Built-in job scheduler
Tie
CI/CD
DIY (GitHub Actions, GitLab CI)
Built-in Slim CI (test only changed models)
Tie
Documentation
Self-hosted (dbt docs generate + serve)
Auto-hosted documentation site
Tie
Column-Level Lineage
Not available
Enterprise plan only
Tie
Semantic Layer
Not available
dbt Semantic Layer (MetricFlow)
Tie
Environment Management
Manual (profiles.yml, env vars)
Built-in environment management
Tie
SSO / RBAC
Not applicable
Enterprise plan (SSO, RBAC, audit logs)
Tie
✅ dbt Core Pros
Completely free — no per-seat licensing costs
Full control over infrastructure and deployment
Use any IDE, any CI/CD system, any scheduler
No vendor dependency — pure open source
Can be containerized and deployed anywhere
⚠️ dbt Core Cons
Need to build your own CI/CD, scheduling, and hosting
No web IDE — requires local setup for each developer
No column-level lineage
Documentation requires manual hosting
More DevOps burden on data engineering teams
✅ dbt Cloud Pros
Built-in web IDE with SQL autocomplete and preview
One-click job scheduling without Airflow or cron
Slim CI automatically tests only changed models
Auto-hosted documentation with search
Column-level lineage and semantic layer (Enterprise)
Easier onboarding for non-DevOps teams
⚠️ dbt Cloud Cons
Per-seat pricing gets expensive for large teams
Enterprise features (lineage, RBAC) require expensive plans
Vendor lock-in to dbt Labs platform
Web IDE can feel limiting for power users
Some features lag behind Core CLI releases
Final Verdict
### Verdict
**Choose dbt Core if:**
* Budget is a primary concern (it's free!)
* Your team has strong DevOps skills (CI/CD, Airflow, Docker)
* You want full control over your deployment environment
* You already have scheduling infrastructure (Airflow, Dagster)
* You prefer working in VS Code or your favorite editor
**Choose dbt Cloud if:**
* You want an integrated experience without building tooling
* Your team is analytics-focused (not DevOps-heavy)
* You need built-in scheduling, CI/CD, and documentation
* Column-level lineage or semantic layer is important
* You want the fastest onboarding for new team members