dbt Cloud Overview

dbt Cloud is a managed web application built by dbt Labs on top of dbt Core. It provides a browser-based IDE, scheduled job runs, a hosted documentation site, team collaboration tools, and observability features — all without managing servers or infrastructure yourself. This topic explains what dbt Cloud offers, how it differs from dbt Core, and when it makes sense to use it.

dbt Core vs dbt Cloud

Feature                   dbt Core          dbt Cloud
-----------------------   ---------         ---------
Cost                      Free              Paid (Developer plan is free)
Interface                 Terminal only     Browser IDE + terminal
Scheduler                 External tool     Built-in scheduler
Documentation hosting     Self-hosted       Hosted automatically
Team collaboration        Via Git only      In-app environment sharing
CI/CD integration         Manual setup      One-click setup
Alerts & notifications    External tool     Built-in email/Slack alerts
Audit logs                Log files only    Web-based audit trail
Model timing metrics      Log files only    Visual run history
Semantic Layer            Not included      Included (paid plans)

dbt Cloud Plans

Plan          Who It's For                Key Limits
----------    -------------------         ----------
Developer     Individual users (free)     1 developer seat, limited jobs
Team          Small teams                 Multiple seats, more jobs
Enterprise    Large organizations         SSO, audit logs, dedicated support

Core Components of dbt Cloud

Environments

An environment in dbt Cloud maps to a target in dbt Core. You create separate environments for development and production. Each environment stores its own connection credentials, dbt version, and environment variables.

Development environment:
  - Each developer runs dbt in their own personal schema
  - Changes do not affect production data
  - Runs interactively in the Cloud IDE

Production environment:
  - Runs on a schedule via dbt Cloud Jobs
  - Writes to the production schema used by dashboards
  - Sends alerts on failure

Connections

A connection stores the warehouse credentials dbt Cloud uses to connect to your database. You configure it once per environment. dbt Cloud encrypts all credentials at rest.

Repositories

dbt Cloud connects to your Git repository (GitHub, GitLab, Bitbucket, Azure DevOps). It reads your dbt project from there. Each developer works on a branch; merges to main trigger production runs.

dbt Cloud Architecture Diagram

Developer's Browser
       |
       v
  dbt Cloud IDE ──── Git Repository (GitHub/GitLab)
       |                      |
       v                      v
  Run dbt commands     dbt Cloud Scheduler
       |                      |
       v                      v
  Dev Warehouse Schema   Prod Warehouse Schema
  (dbt_alice.fct_orders) (analytics.fct_orders)
       |
       v
  dbt Cloud Docs Site ─── Team Members View Docs

Key dbt Cloud Features

Semantic Layer

The dbt Semantic Layer (available on paid plans) lets you define metrics once in dbt and query them from any connected BI tool. A metric defined in dbt automatically appears in Tableau, Looker, and other tools without rebuilding it in each one.

Explorer

dbt Cloud Explorer is a visual interface for browsing your project's models, sources, tests, and lineage. It includes column-level lineage — showing not just which models depend on each other, but which specific columns flow between them.

Run History

Every dbt Cloud job run is recorded. You can see which models ran, how long each took, which tests passed or failed, and the exact SQL that was executed. This history is searchable and exportable.

Notifications

Configure email or Slack alerts when a job fails, succeeds, or produces warnings. Alerts go to specific team members or channels so issues are noticed immediately.

Setting Up dbt Cloud (Quick Steps)

Step 1: Create account at cloud.getdbt.com
Step 2: Connect your Git repository
Step 3: Set up a warehouse connection (Snowflake, BigQuery, etc.)
Step 4: Create a development environment
Step 5: Open the Cloud IDE and run dbt debug
Step 6: Create a production environment
Step 7: Create a job to run dbt build on a schedule

When to Choose dbt Cloud

• Your team has multiple data engineers or analytics engineers
• You need a scheduler without setting up Airflow or another tool
• You want hosted documentation that updates automatically
• You want built-in CI/CD without configuring GitHub Actions manually
• Your organization needs audit logs, SSO, and enterprise security controls

When dbt Core Alone Is Enough

• You are a solo analyst or engineer
• You already have Airflow or Prefect for scheduling
• Your organization cannot use external SaaS tools for security reasons
• You are learning dbt and want the free open-source option