dbt turned its AI on by default. Check the toggle.

dbt turned its AI on by default. From September 1, Wizard and Copilot ship enabled. Already on for new accounts, rolling out to existing ones. If your org opted out, you stay off. Everyone else: the meter is running.

This is not a product review. It is a governance notice. The feature change is fine. The billing change underneath it is the thing that pages you at quarter close.

The billing shift nobody should miss

Wizard moved to per-token metering against your account consumption pool. Turning AI on does not charge you by itself. But every query draws from the pool, and the pool is shared across the whole account. Not per user. Per account.

Read that as a data engineer: a shared, finite resource, with no per-consumer quota by default, metered on usage. You have seen this shape before. It is a warehouse with no resource monitors. It ends the same way.

The gotcha: read-only users can spend the budget

Here is the part that should make you check the toggle today. Questions asked in Explore mode draw from that same shared pool, including questions from read-only users. Anyone with Explore access can spend the budget. Your intern’s curiosity is now a line item.

This is the failure mode nobody demos. The AI feature works exactly as advertised. The access model around it was designed for a world where asking questions was free. It is not free anymore. Every seat with Explore access is now a seat with spend access, whether your cost center knows it or not.

Three moves

None of this is a reason to turn the AI off. It is a reason to own the toggle instead of discovering it on the invoice.

First, check the toggle in Account settings. Know whether it is on, who turned it on, and whether your org ever made a decision about it or just inherited the default.

Second, set a monthly spend limit. Billing and Usage, then Usage-based features, then Wizard. Usage pauses when you hit the limit. A pause you chose beats a bill you did not.

Third, bring your own key. With BYOK your provider bills you directly and dbt’s pool never gets touched. Your existing enterprise AI contract, your existing controls, no shared pool at all.

AI spend is a data-governance problem now

That is the real verdict. The dbt change is one instance of a pattern: AI features arriving default-on, metered against shared pools, with access models from the free era. Every tool you own will do a version of this. The question is never whether the AI works. It is who owns the toggle, who sees the meter, and what happens when the pool runs dry.

Who owns the toggle on your account?

This post started as an Instagram post →