[tehalex]

Most people will just use the sql templating and scheduled cron jobs features of the cloud, which is very easy to self host.

There is cloud IDE, which is just ok in my opinion. I'd rather use a local editor, but might be a value add for some.

The cloud plans also has metadata features and APIs, which could be worth it for some use cases.

The most interesting thing tied to the cloud is the new metrics feature, but I don't really like how it's done (metrics are defined as sql fragments in YAML). Really using metrics depends on proprietary parts that dbt cloud only has, so if you are using this, you'll probably be paying for the cloud.

[1] https://docs.getdbt.com/docs/use-dbt-semantic-layer/dbt-sema...

[data-ottawa]

I'm not a fan of the IDE myself, but I knew a few people who are less technical and prefer the IDE over managing a local python environment.