Skip to content
c17 .ioJoin list

Stacks / Analytics

Medium

dbt Core / SQLMesh

Warehouse transforms you run. dbt Core is Apache-2.0; SQLMesh is Apache-2.0 — dbt Cloud without the seat.

The problem

dbt Cloud meters developers, jobs, and the IDE. You wanted the transform engine. dbt Core is Apache-2.0 (dbt-labs/dbt on GitHub). SQLMesh is Apache-2.0 (SQLMesh/sqlmesh) if you want that framework with dbt compatibility. This is not dbt Cloud's scheduler UI, Semantic Layer SKU, or every native Git integration. ELT stays on /replace/fivetran. Orchestration stays on /replace/astronomer.

Replaces

dbt Cloud

Replace dbt Cloud See all best open-source data tools

Estimated SaaS saved

$1,200

per year, small team, before lock-in

Start on Railway

Airflow if this is scheduling the job, not the SQL transform

Sponsor this stack Tip jar

Placeholder: dbt Core or SQLMesh as a CI/worker job against the warehouse you already have. Not a public website. No one-click template in this repo yet — Start on Railway. Extract stays on /stacks/meltano-elt; scheduling on /stacks/airflow-orchestrate.

The stack

Cost table

You stop payingTypical / yearSelf-host instead
dbt Cloud (small team)$1,200dbt Core or SQLMesh in CI

Agent setup prompt

Replace dbt Cloud with dbt Core (preferred) or SQLMesh.

- Run dbt in CI against the warehouse you already have. One model you actually ship. Do not enable dbt Cloud and call it Core.
- SQLMesh if you want that framework. Orchestrate with Airflow if jobs need a scheduler — /stacks/airflow-orchestrate.
- Write AGENT_PROMPT.md.

Also as markdown: /stacks/dbt-core-transform.md

FAQ

dbt Core or SQLMesh?
dbt Core if the project is already dbt. SQLMesh if you want that engine with dbt compatibility. Pick one.
Is this Fivetran?
No. Fivetran is extract-and-load — /replace/fivetran. dbt is transforms in the warehouse.
Who runs the job?
CI, or Airflow (/replace/astronomer). dbt Cloud's scheduler is the product this page leaves.