Data Foundation · 10 min read · May 2026
dbt Cloud vs dbt Core in 2026: The Honest Decision Framework
By Thinklytics Partners, Data Foundation Practice
dbt Cloud went up in price again. dbt Core is still free but needs a real engineering team. The honest 2026 decision framework: who should pay for Cloud, who should self-host Core, what the per-developer math looks like at your team size, and how to migrate either direction without rewriting your project.
Topics covered
- dbt Cloud
- dbt Core
- dbt pricing 2026
- dbt Cloud vs Core
- dbt self-hosted
- dbt orchestration
- data engineering team
Frequently asked questions
What's the difference between dbt Cloud and dbt Core?
dbt Core is the open-source Python package that compiles your SQL transformations into a DAG, runs them against your warehouse, and tests them. Free. dbt Cloud is dbt Labs' hosted SaaS that wraps dbt Core with an IDE, scheduler, CI/CD, semantic layer, and observability. Paid per developer seat plus usage-based runtime costs as of 2026.
How much does dbt Cloud cost in 2026?
Developer seats are roughly $100/dev/month for Team tier and $300+/dev/month for Enterprise tier. Plus usage-based runtime fees calculated on successful model runs. A 10-developer team on Team tier runs $12K/year minimum on seats, often $25K-$60K/year all-in once you include runtime. Enterprise runs $50K-$150K+/year.
Can we self-host dbt Core for free?
The dbt Core package is free, yes. But you still need a scheduler (Airflow, Prefect, Dagster, or cron + scripts), CI/CD (GitHub Actions or similar), an IDE (VS Code with the dbt Power User extension), and somewhere for engineers to run jobs. The realistic 'free' setup costs 0.5-1.0 FTE of platform engineering time at minimum, which is more expensive than dbt Cloud at most team sizes.
When does dbt Cloud pay for itself?
Below 5 developers, dbt Cloud is almost always cheaper than the FTE cost of self-hosted infrastructure. Between 5-15 developers it depends on whether you have an existing data platform team. Above 15 developers, the per-seat math gets uncomfortable; many teams at that scale shift back to dbt Core on internal infrastructure.
What runs dbt Core in production if not Cloud?
Most production self-hosted dbt deployments use Airflow, Dagster, or Prefect as the orchestrator. Dagster has the cleanest dbt integration as of 2026 (native asset model, partial-failure recovery, lineage UI). Airflow is the most common because most data teams already run it. Prefect is the smallest setup if you don't have an existing orchestrator.
Can we move from dbt Cloud to dbt Core without rewriting?
Yes. The dbt project itself (models, tests, sources, macros) is platform-portable. The migration work is in the orchestration layer (rebuilding job schedules in Airflow / Dagster / Prefect), CI/CD (rebuilding the Cloud Slim CI in GitHub Actions), and access controls (rebuilding what Cloud's permission system gave you for free). 4-12 weeks for a typical mid-size project.