Deployment for dbts
dbt deployment is running dbt reliably outside your laptop. It covers scheduled production jobs in dbt Cloud, Airflow or another scheduler, separate dev and prod targets, and continuous integration that builds and tests only changed models on each pull request, so that bad code is caught before merging.
Stage: Deploy and Serve · Part of the dbt roadmap · Last reviewed 19 November 2026
What to learn in Deployment
- Configure separate dev and prod targets in profiles.yml
- Schedule a production dbt build job with alerts on failure
- Run slim CI that builds only modified models for each pull request
- Store credentials in environment variables or a secrets manager
- Publish docs and track source freshness with dbt source freshness
Deployment interview questions
What is slim CI in dbt?
Slim CI builds and tests only the models changed in a pull request and their downstream dependents, using state comparison against production artifacts. It gives fast feedback and low warehouse cost compared with rebuilding the whole project.
Why keep separate dev and prod environments?
Developers can build and test changes in a personal schema without touching tables that dashboards use. Production runs from the main branch with controlled credentials, so a broken experiment never reaches business users.
Where Deployment fits in the dbt roadmap
Deployment belongs to the Deploy and Serve stage (advanced level). Production.