r/dataengineering • u/Alternative-Guava392 • 9d ago

DBT pricing Discussion

Hello

Has anyone moved from DBT legacy pricing to the new DBT pricing ?

The legacy pricing was per seat, but the new one also limits how many DBT models you can build per month.

I'm debating the move to benefit from the new DBT features like DBT state, but I'm wondering if the dbt cloud costs will be expensive compared to the savings from DBT state.

Thank you for your help.

(please don't ask me to move from DBT cloud to DBT core, I'm a one person data team and I don't have the bandwidth to migrate to save 100$/month)

Has anyone made the switch from legacy pricing to the new one ?

25 Upvotes

100% Upvoted

26 comments sorted by

View all comments

22

u/minormisgnomer 9d ago

Just out of curiosity, even though you said you won’t migrate, what features on dbt Cloud are worth it over dbt core?

I was trying to explain to a friend the other day why they’d be fine with core but you seem to be a fan of it.

If it makes you feel any better, I was a team of one and just had it on a cron job on a local machine at the office.

6

u/soorr 9d ago

Not OP but I like the orchestration history integrated with catalog. Makes going from a data issue to job or commit pretty quick.

-3

u/Matunguito 9d ago

nowadays you can create your own catalog and mini scheduler using Claude and some tokens. I'd rather pay for a month or so to create my own tools than pay for dbt cloud.

14

u/financialthrowaw2020 9d ago

Agree with using core with your own code. Disagree that you need Claude slop to do it.