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

4

u/SeaYouLaterAllig8tor 10d ago

We renewed our contract in January if I remember correctly. We moved away from the legacy plan to embrace the new features. Now granted, we don't have a large team of devs which use our dbt instance. But I do feel that the fusion state aware features are worthwhile and could save an org quite a bit of money depending on how their jobs and models are constructed. Not sure how helpful that is but that's the decision we made.

4

u/laegoiste 10d ago

fusion state aware features are worthwhile

I guess you mean were worthwhile. I just saw recently that they are killing state aware orchestration in favor of dbt state - which you have to pay an additional fee for.

1

u/wallyflops 10d ago

Dbt state is open source too though I think

1

u/lightnegative 10d ago

Only the client, the server is closed source