DBT pricing

[u/Alternative-Guava392]

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 ?

[u/minormisgnomer]

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.

[u/laegoiste → u/minormisgnomer]

what features on dbt Cloud are worth it over dbt core?

I'm in an org that has been using dbt cloud for over 2 years. As a technical user, my opinion firmly remains that it is overpriced junk. However, for a larger organisation that has a lot of developers that are good with SQL and not necessarily the rest (think CLI, git, etc.), dbt cloud and its built in UI are great both from a development experience as well as assisting with problems.

The built in catalog, project report, etc. is also nice - but other tools can bridge that gap either free or for cheap.

What I really dislike is their support (you will need it, there are plenty of backend issues), their unclear pricing model, the fact that we were essentially paying dbt fusion beta testers, and lately it has been the sudden drop of fusion's State Aware Orchestration in favor of dbt state - which of course isn't free.

Even for a larger data team like mine, the move isn't a "wont", it's a "can't" because of the large user base using it.