Personally, there's no way I'd want a customer initiated operation to trigger something like terraform or mess with DB schemas. On the security side, it would significantly complicate the permissions structure from the application to the database. And on the performance side, I have absolutely no mental model for how operations like that scale, and how trivial of a DoS I'm exposing myself to. At the same time, I love the isolation (mostly operationally, the security & privacy side is also nice) that db-per-customer would bring. If this product helps bridge the gap, then it sounds good to me.
Last project I worked on was a mix of on prem software and cloud software.
The cloud counterpart had 600+ mongodb databases split amongst 3 Mongo clusters.
The integration team took usually 2 weeks to setup the on premises software, and the cloud stuff took about a minute.
The entire setup for the cloud was a single form that the integration team filled in with data.
The point I'm trying to make, is that if your customers require separate infra, they can wait a bisuness day to be setup. Meanwhile they can play on a sandbox environment.
It's also doable in fully automated fashion, but you will have to have strong identity and payment verifications, to avoid DoS, and in those cases usually contracts fly around.
That's for the b2b side.
For b2c, usually you rely on a single db and filter by column ID or similar, which can easily be abstracted away.
What exactly is the value prop tho? To a technical person 1 business day wait seems dumb, but few businesses move that fast where waiting a single day matters.
