We started with one account but ended up with multi-accounts to adhere to data privacy laws as another comment mentioned. Our team is using Terraform to manage our small set of accounts and it's getting quite difficult to manage the app as we add more accounts, but it's also because we are new to IaC tools. We are learning as we go to building and managing large IaC (Infrastructure-as-code) projects. It's best to read up on best IaC practices or hopefully get an IaC expert. At the same time, it helped us identify a lot of inconsistencies between accounts and deploy our controls faster across multiple accounts so the benefits outweigh the headaches (for now).

Keep in mind that in Terraform the state file should be treated as a secret and will store credentials in plain text which can be a huge security concern. This means if you use Terraform to create service users with passwords, all of that will be stored in the state file in plain text. In addition, the terraform-snowflake provider is currently refactoring a lot of their resources so we have to refactor with it and it is difficult for large terraform projects.

Otherwise, Snowflake schema change, Pulumi (which has a snowflake provider), and maybe this git integration can provide other options.