A note on dbt product naming: dbt is an engine, and it now comes in two versions: v1.x (previously called dbt Core) and the next-generation v2.0. You can either self-host dbt or run on dbt platform (formerly dbt Cloud). Many people still search for “dbt Core” and “dbt Cloud”, but those are the previous names, so this article uses the current terms.
Choosing between self-hosted dbt and dbt platform isn’t simply a question of comparing features.
Self-hosting dbt gives organisations significant control over how dbt is deployed and operated. For teams with established infrastructure, platform engineering capability and specific architectural requirements, that control can be valuable.
dbt platform takes a different approach, providing a managed environment with capabilities for developing, orchestrating, deploying and managing dbt projects. For some organisations, this can reduce the operational responsibilities surrounding dbt and provide a more standardised environment for teams to work in.
Neither approach is inherently right for every organisation.
What we should be asking is: which operating model best fits your requirements, capabilities and priorities?
When self-hosted dbt Makes Sense
Self-hosted dbt can be an effective choice when an organisation has good reasons to retain control over its environment.
You may prefer to self-host dbt if you have established infrastructure and DevOps capabilities, specific deployment or architectural requirements, or an existing environment that operates efficiently.
It can also make sense when your team values the flexibility to build and manage the surrounding tooling itself and has the capacity to maintain it.
If your self-hosted dbt environment is working well and continues to meet the organisation’s requirements, growth alone isn’t necessarily a reason to move.
When dbt Platform Makes Sense
For other organisations, the question may be less about retaining control and more about where they want to direct their resources.
Self-hosting dbt can involve managing infrastructure, orchestration, CI/CD, environments, access, monitoring, upgrades and other capabilities around the dbt project.
As adoption grows, so does complexity. This can lead to increasingly brittle pipelines, poor documentation and observability, and slow troubleshooting when things go wrong. Many organisations consider dbt platform when they want to reduce operational burden and costs, improve data quality, and provide a governed, standardised environment for contributors.
Those potential benefits still need to be weighed against the cost, effort and implications of changing an existing environment.
Considerations When Comparing Self-Hosted dbt and dbt Platform
1.
Control
Start by considering how much control your organisation needs over its infrastructure and operating environment.
Self-hosted dbt provides considerable flexibility over how and where dbt is run. This may be important if you have specific architectural, infrastructure, security or deployment requirements.
If your organisation doesn’t require that level of control, consider whether managing it provides enough value to justify the effort involved.
2.
Internal Capability
Having the technical capability to self-host dbt is different from deciding that your organisation should continue owning that capability.
Teams with established platform engineering and DevOps functions may already have the skills, processes and infrastructure required to operate self-hosted dbt effectively.
But capability isn’t the same as capacity, and self-hosting carries ongoing costs and risks that are easy to underestimate:
- When the person who understands a custom deployment leaves, that knowledge leaves with them, and the team inherits a system nobody fully understands.
- Complex, bespoke environments take weeks to learn, which delays new team members from contributing.
Alternatively, many organisations choose dbt platform precisely because it reduces reliance on specialist operational knowledge. Documentation stays current automatically, version control is built into the workflow, and dbt Mesh gives multiple teams a governed way to build on each other’s work. Instead of a bespoke deployment that only a few people fully understand, new joiners work in a standard environment, and knowledge lives in the platform rather than in individuals’ heads.
3.
Engineering Capacity
Consider where you want your engineers spending their time.
Maintaining self-hosted dbt involves responsibilities beyond developing models. Infrastructure, deployment workflows, orchestration, upgrades, monitoring and troubleshooting all require ongoing attention, and each often relies on a separate third party tool that must be integrated, secured and kept up-to-date.
That isn’t necessarily inefficient. For some teams, these responsibilities fit naturally within their role.
For others, reducing the operational workload frees engineers to focus on modelling, data quality, analytics and new data products, rather than maintaining the machinery around it.
So the question isn’t whether your team can run dbt themselves. It’s whether that effort is the best use of your team’s capacity.
4.
Scale & Collaboration
As more people contribute to dbt, the demands on your development process change.
When only a few people can contribute, they become the bottleneck. When many contribute in silos, you get bloated monorepos, duplicated models and competing definitions, which can generate unnecessary compute and erode trust in the dtata. AI raises the stakes. Agents can generate models faster than ever, but speed without structure does not scale.
Consider how effectively your current environment supports multiple contributors, development environments, testing, deployment and cross-team collaboration. For small growth companies, self-hosted dbt may continue to scale effectively.
However, if each stage of growth demands more tooling, infrastructure or processes, it may be worth comparing that operating model with what dbt platform provides.
5.
Governance and Security Requirements
Security, access, auditability and governance matter regardless of which approach you choose, and the more people and agents contribute, the more they matter.
Most organizations need role-based, least-privilege access, data protections plus clear audit trails and documentation. When organisations self-host dbt, they must design and maintain these controls around their own infrastructure and existing technology environment.
dbt platform provides provides enterprise access controls and data protection out-of-the-box, ensuring regulated organizations meet strict compliance requirements like HIPAA.
What you should be asking is: which approach best fits your organisation’s security, compliance and governance requirements.
6.
Total Operating Cost and Effort
Licence cost alone doesn’t provide a complete comparison.
For self-hosted dbt, consider the infrastructure, supporting tools and internal resources required to operate and maintain the environment.
For dbt platform, consider subscription costs alongside migration, implementation, integration and ongoing administration.
A fair comparison should look at the total operating model, including both direct expenditure and internal effort.
Deciding Between Self-Hosted dbt vs dbt Platform
| Consideration | Self-hosted dbt may suit you when… | dbt platform may suit you when… |
| Control | Infrastructure and deployment control is important | You don’t need to manage as much of the operating environment yourself |
| Internal capability | You have established skills and processes to operate self-hosted dbt | You want to reduce operational responsibilities surrounding dbt |
| Engineering capacity | Managing the environment is an appropriate use of your team’s resources | You want to direct more capacity towards data development |
| Scale | Your existing environment and processes continue to scale effectively | Growth is increasing the effort required to manage your environment |
| Governance | Your existing controls and tooling meet your requirements | You want to consolidate more capabilities within the dbt environment |
| Commercial | Your infrastructure and internal operating costs remain appropriate | The managed model provides sufficient value to justify its cost |
Assess Before Making A Decision
If your self-hosted dbt environment is reliable, appropriately governed and cost-effective, and your team has the capacity and capability to operate it, continuing to self host dbt may be the appropriate decision.
If maintaining the environment is consuming increasing resources, limiting collaboration or restricting your organisation’s objectives, there may be a business case for considering dbt platform.
Before deciding whether to move from dbt Core to dbt Cloud, establish what you are trying to achieve.
Review your current architecture, operating effort, dependencies, workflows and costs. Identify what is working well and where genuine constraints exist. Then consider whether dbt Cloud addresses those constraints sufficiently to justify a change.
You may conclude that dbt Core remains the right fit.
You may identify improvements that can be made without migrating.
Or you may determine that moving to dbt Cloud provides a better operating model for where your organisation is heading.
If that’s the case, read on for our migration guide.
Helping Organisations Get More From dbt
Data Army is a dbt Visionary Consulting & Services Partner, the highest tier of partnership within the dbt Partner Program. As a dbt-certified organisation, we bring deep expertise in analytics engineering, implementing and optimising dbt for our clients, and helping organisations advance their modern data stack with scalable, trusted data practices.
We also use dbt extensively within Data Army’s own data environment, so our team has first-hand experience of the platform and the same practical considerations our clients encounter when implementing, managing and scaling dbt.
Considering the Move to dbt Platform?
See how we’ve helped others make the move, or learn how to manage your own migration to dbt platform.
See a dbt platform migration in action
See how Data Army helped Australian digital home loan platform and financial technology company, Lendi, upgrade to dbt platform, creating a trusted data foundation for its AI-native future.
How to upgrade to dbt platform
Our practical guide steps through how to move to dbt platform while managing dependencies, reducing disruption and taking the opportunity to build a more scalable, easier-to-manage environment.
*dbt Labs refers to what many know as dbt Core as self-hosted dbt, while dbt Cloud is dbt platform.
You can read more about the distinction between self-hosted dbt and the dbt platform here.