dbt

dbt is how analytics teams turn raw warehouse tables into trustworthy, documented data models, using plain SQL plus the engineering discipline that was always missing from analytics: version control, testing, and dependency tracking. You write SELECT statements, dbt handles the order they run in, tests the output, and builds the documentation. dbt Core, the command-line tool, is open source and free, and as of the v2 line it is squarely Apache-2.0.

The big 2026 shift is Fusion. dbt rewrote its engine in Rust and put it under dbt 2.0 (in alpha as of this writing), promising faster parsing and real-time SQL validation. The catch is licensing nuance: the classic dbt Core stays Apache-2.0, but Fusion is a mix of source-available (ELv2), Apache, and proprietary parts, and the new Fusion-powered VS Code extension is free only up to 15 users before it needs a commercial license. Self-hosting the core still costs nothing and runs anywhere Python does; you bring your own scheduler (Airflow, cron, Dagster) to run it in production.

Solo analysts and small teams: dbt Core plus a scheduler is the free, complete path, and it is the industry standard for a reason. dbt Cloud starts to make sense when you want the hosted IDE, scheduling, and the Semantic Layer without assembling them yourself: Developer is free for one seat, Starter runs $100/seat/mo, and Enterprise (Mesh, advanced catalog) is custom-quoted. The honest line: you are paying for orchestration and collaboration, not for dbt the transformation tool, which you can always run yourself.

Watch the Fusion rollout. It is the future dbt is steering toward, but it is where the open-source line gets blurry, source-available here, a per-seat gate there. The transformation core you depend on is still free and open; just read the license on each new piece before you build on it.