Run the work.
Run on shared workers, or use an operator-enabled dedicated compute profile for eligible workloads.
Explore executionConfigure syncs, run jobs, and monitor results in one workflow.
Start in the UI or define your workflows in Git. Choose shared or eligible dedicated execution.
Pay for usage. No subscription required.
Choose how you configure it.
Keep execution and monitoring together.
Timezone: UTC
Existing tasks in this job
load.ordersload.customersRun on shared workers, or use an operator-enabled dedicated compute profile for eligible workloads.
Explore executionFollow runs, destination freshness, row volumes, and reported quality issues.
Explore observabilityBuy credits for usage. Dedicated capacity is metered by lease time. No monthly subscription required.
How pricing worksFollow credit consumption by job run. Shared runs use standard usage credits; dedicated capacity is metered by lease time.
Explore usage & pricingReview credits alongside run history. Failed shared runs have no standard run charge; a ready dedicated lease can still accrue cost.
Eligible organizations can choose a named compute profile. Its hourly rate and lease lifetime determine the maximum credit reservation; unused credits return at settlement.
We’re planning credit estimates for each job, informed by workload, past runs, and compute configuration, so you can review expected usage before starting.
Build dbt projects in your warehouse after a job succeeds, on a schedule, or on demand. Dedicated compute remains available for eligible workloads.
What's new in v0.20.0Check a Git-backed project before saving it, then inspect model and test results for each build.
Run transformations on shared workers or use a granted dedicated compute profile.
Get notified when a transformation build or its dbt tests fail.
Start with one real workflow during the beta.
Get early access