We've seen a recurring pattern in threads here: teams start with DBT Core, then hit a wall and migrate to DBT Cloud. The pricing difference is stark—a managed service seat can cost roughly 5x more than the infrastructure to run Core. Yet the switch keeps happening.
I want to move beyond the surface-level "Core is free, Cloud is expensive" take. Let's get concrete about what you're actually buying and when the premium becomes justified. For a team of 5 analytics engineers, Cloud could easily be $50k+ annually versus maybe $10k in managed compute for Core.
The key costs to factor for Core (beyond engineer hours):
* Orchestration/scheduling (Airflow, Dagster, Prefect)
* Hosting for the IDE & documentation (if needed)
* CI/CD pipeline management
* Ongoing maintenance & upgrade time for the above
For Cloud, you're paying for:
* The integrated IDE (Development, Staging, Prod environments)
* The scheduler
* Managed CI/CD with PR workflows
* Support & SLAs
So my question to the community is this: **At what point does the operational overhead of Core become a cost center that justifies the 5x multiplier?** Are we talking team size, complexity of DAGs, or simply the opportunity cost of your engineers managing pipelines instead of building models?
Please share your team's scale, your "gotcha" moments, and any hard numbers on time saved or lost. Vendor-neutral, evidence-backed experiences will be most valuable here.
- mod hj
Keep it constructive.
I'm a data engineer at a 200-person SaaS company, and we've run both setups. We currently use DBT Core in production with Dagster for orchestration, managing about 700 models.
1. **Orchestration Effort:** Core requires you to build and manage a scheduler. Using Dagster took us roughly 80-100 engineering hours to get a reliable pipeline with retries, logging, and monitoring. Our monthly maintenance for updates and troubleshooting averages 4-6 hours. Cloud eliminates this entirely.
2. **IDE & Development Workflow:** The biggest hidden cost with Core is replicating a collaborative development environment. We spun up a simple web IDE, but it lacked Cloud's integrated state management (development/staging/prod). This caused environment drift issues that took us about 10 hours a month to resolve before we built more tooling.
3. **CI/CD Management:** With Core, you wire it yourself. We used GitHub Actions, which added configuration overhead. Every time we needed to adjust the build matrix or add a new test, it was a 2-3 hour task. Cloud's PR-based deployment workflows are a zero-configuration win for teams that deploy multiple times a day.
4. **Support and Upgrades:** With Core, you're on your own. A breaking change in a dependency (like a Python version shift) can halt runs and require immediate, unplanned work. In my last shop, a Snowflake connector update broke our runs and took two engineers a full day to fix. Cloud's managed service includes handling these updates, which has tangible value during critical incidents.
I recommend DBT Core for teams with dedicated DevOps or platform engineer support and lower deployment frequency (say, once a week or less). If you're a team of 5 analytics engineers with no dedicated platform help and you deploy models daily, go with Cloud. To make the call clean, tell us how many platform/DevOps hours you can realistically allocate per month and your current average weekly deployment count.
Your point about the orchestration effort is fair, but I think your 80-100 engineering hour estimate is a best-case scenario. That assumes your team already has deep Dagster/Prefect/Airflow expertise. For a team learning on the fly, that can easily double, especially when you factor in the time spent on the wrong abstraction or debugging obscure YAML.
And regarding Cloud eliminating maintenance entirely, that's a bit optimistic. You're trading internal maintenance for dependency on an external vendor. Their downtime is your downtime, their breaking API change is your emergency. You've just shifted the maintenance burden from operational to vendor management and contract negotiation.
Question everything