Get started with dbt today

Team plans are billed monthly on the credit card used to sign up, based on developer seat count ($100USD per seat per month) and successful models built (over 15,000 per month). You’ll also be sent a monthly receipt to the billing email of your choice. If you’d like to change any billing information, just reach out to us at support@getdbt.com.

Enterprise plan customers are billed annually based on the number of developer seats and successful models built, as well as any additional services + features in your chosen plan.

At present, dbt Cloud Team plan payments must be made via credit card, and by default they will be billed monthly based on the number of developer seats.

We don’t have any plans to do invoicing for Team plan accounts in the near future, but we do currently support invoices for companies on the dbt Cloud Enterprise plan. Feel free to contact us to build your Enterprise pricing plan.

​​Yes, you can upgrade or downgrade at any time. Account Owners can access their dedicated billing page via the account settings page: just click the hamburger icon and “Billing” to adjust your plan or update credit card information.

If you’re not sure which plan is right for you, get in touch and we’ll be happy to help you find one that fits your needs.

You can cancel your account at any time on your Account Settings page. Of course, we’d hate to see you go – drop us a line and we’ll do everything we can to make it right!

dbt Cloud stores the following data persistently:

• dbt Cloud account information including job definitions, database connection information, users, etc. Cloud account information does not include any raw data from your warehouse.
• Logs associated with jobs and interactive queries you’ve run.
• Your dbt “assets” which include artifacts like run_results.json and manifest.json.

Logs and assets do not include raw data from the warehouse, unless the code you write commands it.

For example, it’s possible to write dbt code that fetches all customer data from your customer table and writes it to the logs. While that’s usually not a good idea and we do not recommend it, if you did that it’d mean that information is stored in dbt Cloud.

When writing interactive queries from the IDE (for example: select * from customers limit 100) the resulting query output passes through dbt Cloud infrastructure on the way to your browser.

However, this data is not persisted in any way (caching or otherwise). It does not live on our servers outside of your browser session.

The legacy version will be deprecated in December 2023. Learn how to upgrade to the new Semantic Layer with MetricFlow using this migration guide, and see pricing information on the dbt Documentation Billing page.

Team and Enterprise customers can use 1,000 Queried Metrics per month for no additional cost on a limited trial basis, subject to reasonable use limitations. For more information, please see the dbt documentation Billing FAQs.

There are other limitations that most clients are unlikely to encounter, depending on client usage patterns. Truly “unlimited” usage of current and/or future features, products or services is never possible because costs, expenses, and supplier charges are subject to fluctuation and/or inflationary or other permanent increases. Client usage must remain subject to other reasonable use limitations. dbt Labs reserves the right to adjust limits, encourage optimization or increase pricing dependent on market forces, client usage patterns, and, ultimately, its discretion.