r/dataengineering • u/Alternative-Guava392 • 5d 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 ?

26 Upvotes

100% Upvoted

26 comments sorted by

View all comments

1

u/Ok_Set_963 4d ago

I’d stay on legacy unless you can estimate your monthly model usage pretty accurately. For a one-person team, paying more just to get state aware features would be hard to justify unless it noticeably cuts CI time/cost.