What is dbt Canvas? Self-service data modelling without SQL
Easier data modelling, but quality remains crucial
- Article
- Data Analytics


dbt Canvas allows you to build data models through a visual interface, without writing SQL. With drag-and-drop functionality and AI support, Analysts can now independently build models and commit them to Git. This means that even less technical Analysts can contribute to the dbt codebase. Sounds like a gamechanger, but is it?
Self-service data modelling is on the rise
More and more organisations are focusing on self-service data modelling: as an Analyst, you gain more autonomy to build models yourself. Tools like dbt Canvas cater to this trend, making the translation from business question to data model faster and more efficient. However, when more people start modelling, new challenges inevitably arise.
Why is dbt Canvas attractive?
dbt Canvas lowers the barrier for data Analysts to build models themselves. Behind the visual interface, SQL code is generated. This feature is available for dbt Enterprise and Enterprise+ accounts.
With dbt Canvas, you can:
- Explore tables, join them, and build logic visually
- See immediate previews of intermediate steps
- Apply aggregations and filters without writing SQL
- Commit the generated SQL to Git
Benefits for Analysts and Engineers:
- Faster collaboration: Analysts no longer have to wait for Engineers to make time
- Lower entry barrier: thanks to the visual interface and AI assistance
- More control and shared source of truth: logic stays in the dbt codebase, not in BI tools
- Better business alignment: Analysts best understand the business context and can translate it into concrete logic
- Easier data exploration: Analysts can dig deeper into the data, improving structure and context understanding
- Faster prototyping: Engineers can also use Canvas for quick first drafts
But… is it production-ready?
Here’s the caveat: dbt Canvas generates valid SQL, but it does not account for:
- Model standards, naming conventions, or folder structures
- Mandatory documentation (.yml files) or tests (on the roadmap)
- Query performance and validations
- SQL formatting (e.g., enforced SQLfluff)
- Full data previews: only a limited sample is shown, so join/filter errors may go unnoticed
You can run models in a dev environment, but Analysts still need to check output in the data warehouse. Basic SQL knowledge remains necessary.
Access ≠Quality
Even if models land in a separate folder and pass CI checks, they won’t automatically meet team standards. Often, an Analytics Engineer review is needed for cleanup, documentation, and tests.
Without thorough checks, logic errors may slip through, especially if there are no clear validation guidelines.
Can you trust the result?
Validation is a core part of data modelling. Normally, you would run checks like:
- COUNT(*) or COUNT(DISTINCT id)
- Row-by-row comparisons
- Analysis of query costs and runtimes
- Adding dbt tests
dbt Canvas lacks these checks in the interface, making them easy to overlook.
AI helps, but expertise remains essential
Even with AI support, modelling is still a skilled task. Best practices for joins, aggregations, maintainable logic, and validation remain critical. Canvas lowers the entry barrier, but doesn’t remove the complexity.
The key question remains: who ensures quality and performance? And how do you maintain consistency when contributors have different skill levels?
What does this mean for your team?
dbt Canvas changes team dynamics: Analysts now have direct influence on the data model, which can be valuable. But it also requires clear agreements, such as:
- Who performs reviews and enforces standards
- When an Analyst can model independently
- How to validate what’s built
- Whether Engineers relinquish some responsibility or increase oversight
Without clear governance, you may just be shifting complexity rather than solving it.
And then there’s the cost
dbt Cloud Enterprise pricing is customised, based on user numbers and usage patterns. You pay per seat and per usage (e.g., model builds).
More contributors = higher licence costs. Decide upfront who truly needs access.
Conclusion: more accessible, but not simpler
dbt Canvas lowers the barrier to modelling, and that’s positive. It can lead to faster insights, more ownership, and fewer bottlenecks. But it does not take over responsibility for quality.
If you already have dbt Enterprise, it’s worth testing. But set clear rules on validation, responsibilities, and standards.
Curious if it suits your team? We are happy to discuss it with you.
This is an article from Amira Zouaghi
Amira has been a Data Analyst at Digital Power since 2022. She enjoys diving deep into the data for clients like bol, Robeco, and FysioHolland, translating business questions into structured models. She increasingly focuses on Analytics Engineering, where she helps clients build, optimise, and future-proof their data models.
Receive data insights, use cases and behind-the-scenes peeks once a month?
Sign up for our email list and stay 'up to data':