# Dbt Labs Dbt > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-10-04. - **Brand record:** https://optimly.ai/brand/dbt-labs-dbt - **Dataset:** https://optimly.ai/brand/dbt-labs-dbt.json - **Markdown:** https://optimly.ai/brand/dbt-labs-dbt/llms.txt - **Official website:** https://getdbt.com - **Slug:** dbt-labs-dbt - **Categories:** data-analytics-business-intelligence ## Overview - **Tagline:** Transforms data with SQL using software engineering best practices (modular, tested, version-controlled), offers interactive lineage, automatic model/column refactoring (Fusion engine), interoperable with a deep ecosystem of data tools, and provides smart orchestration for cost savings on warehouse spend. Source: Brand's website (https://getdbt.com) · 2026-10-04 - **Description:** Dbt Labs provides an analytics engineering platform that empowers data teams to transform, test, and deploy data models using SQL. It facilitates building robust data pipelines, improving data quality, strengthening governance, and accelerating the development of trusted analytics and AI products. Source: Brand's website (https://getdbt.com) · 2026-10-04 ## Offerings - **Core capabilities:** - dbt (Data Build Tool) - Fusion engine - dbt Catalog - dbt Semantic Layer - dbt IDE extension Source: Brand's website (https://getdbt.com) · 2026-10-04 - **Pricing:** Not explicitly stated Source: Brand's website (https://getdbt.com) · 2026-10-04 ## Audience - **Target industry:** Data teams, analytics engineers, organizations seeking to build trusted data models and pipelines for analytics and AI development across various industries. Source: Brand's website (https://getdbt.com) · 2026-10-04 Page last updated 2026-10-17. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.