Account-specific features
The features in dbt are tailored to each organization's unique configuration, including user permissions, project setup, and subscription level, with guidance provided to help teams make the most of their available capabilities.
This document provides a comprehensive overview of account-specific features in dbt according to plan type.
dbt Wizard
dbt Wizard is an AI-powered assistant designed to accelerate your development workflow and help you focus on delivering high-quality data.
dbt Wizard is available to all users in dbt but limits are imposed according to plan type. Have a look at dbt's pricing for more information.
dbt Wizard features
Codegen StarterEnterpriseEnterprise +
dbt Wizard codegen refers to the code generation capabilities provided by dbt Wizard, an AI-powered assistant integrated into dbt. This feature allows users to generate SQL code, documentation, tests, and semantic models directly from natural language prompts, helping automate and accelerate common analytics engineering workflows.
dbt Wizard codegen uses metadata such as relationships, lineage, and model context from your dbt projects to produce contextually accurate code. This helps avoid mistakes common with generic AI tools by ensuring generated code matches your actual schema and conventions.
The code dbt Wizard generates may include:
- Base/staging/semantic models (including SQL for new models)
- YAML files for documentation or tests
- Inline SQL expressions
- Semantic model structures and metrics
dbt Wizard codegen is available in the Studio IDE, making it possible to generate and edit code directly within it.
Bring your own key (BYOK) EnterpriseEnterprise +
BYOK allows users to provide and manage their own encryption or API keys, rather than relying on keys managed by a vendor or third party. This gives organizations greater control over data security, compliance, and contracts.
BYOK means users can bring and configure their own OpenAI, Anthropic, or Azure AI Foundry credentials. With BYOK, users have more control over privacy, observability, and security for their data and metadata. Take note of the following when using BYOK:
- When you use your own API key, your contract with the LLM provider (not dbt Labs') applies. You are responsible for managing costs, usage limits, and data handling. This means ownership and liability for API use rests with the user, not dbt Labs.
- dbt Labs does not impose usage limits on the user's key, as it does with internally managed keys.
-
OpenAI projects with data residency controls enabled and configured for the United States (project region set to US) don't currently support BYOK. These projects can only use the API key in the dbt platform configuration. Specifying custom endpoints required for data residency isn’t yet supported, and we’re evaluating a solution for this.
To use BYOK, ensure your OpenAI project doesn’t have data residency controls enabled. Projects without project region settings will use the standard OpenAI endpoint (
https://api.openai.com) and support BYOK. - Currently, BYOK in dbt supports OpenAI and Azure-hosted OpenAI API keys. Users enter their key through the account settings, and requests made by dbt Wizard or other AI features are billed directly to the customer by the respective provider.
The dbt Wizard experience with BYOK and Azure OpenAI will not use metadata information in the Studio IDE.
Without this contextual data, the LLM's responses may be suboptimal compared to those generated by the default dbt AI service. This is a temporary limitation, and we are working on an update that will enable the use of Azure OpenAI APIs.
If you choose to BYOK, we don't monitor or collect any data related to your usage.
Some of the reasons organizations require BYOK include:
- Regulatory and compliance demands (for example, keeping encryption keys or sensitive operations under customer control)
- Assurances about how and where data is processed
- Ability to negotiate and manage their own vendor contracts
- Ability to collect their own observability metrics
Note that BYOK is different from bring your own cloud (BYOC). BYOK refers to key or credential management, whereas BYOC refers to running software workloads in your own cloud environment.
dbt Mesh cross platform EnterpriseEnterprise +
dbt Mesh cross-platform (sometimes called "cross-platform Mesh" or "cross-platform dbt Mesh") is a capability in dbt Mesh that allows for referencing models and sharing lineage across multiple dbt projects, even when those projects use different data warehouse platforms.
SCIM EnterpriseEnterprise +
SCIM (System for Cross-Domain Identity Management) automates user identities and groups, enhancing security and simplifying admin tasks. It allows for real-time user provisioning, deprovisioning, and profile updates in dbt, primarily using Okta as the identity provider.
Hybrid projects EnterpriseEnterprise +
Hybrid projects refer to a setup where both dbt v1 and dbt are utilized within the same organization, often working on the same codebase or data platform. This approach enables different teams or contributors to work in the environment that aligns best with their preferences or workflows, while still benefiting from shared assets and centralized metadata.
Enterprise security Enterprise +
Enterprise security includes robust capabilities for managing network access and user permissions, designed to safeguard sensitive data. Two widely used features that support these efforts are PrivateLink and IP allowlisting.
PrivateLink
PrivateLink provides a secure and private connection between your organization's environments, such as databases, version control systems, or data warehouses and dbt. This setup ensures that traffic remains within the AWS network, avoiding exposure to the public internet.
IP allowlist
IP restrictions (IP allowlist/blocklist) let organizations control which IPs can access their dbt account.
Projects and run slots
The number of projects and run slots available to your organization varies based on your selected plan tier. For detailed information, please refer to our pricing page.
Upgrade plan
dbt offers a range of plans with varying features to suit different organizational needs.
For information on the different plan types and upgrading your plan, refer to our document on How to upgrade a dbt Cloud account.
Related content
Was this page helpful?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.