I would say when you have something that is going to be cheaper for you to have it in your own server. Not all servers are that expensive (you can even use an old PC for this purpose)if they is only going to be used for a limit amount of users.
Specially when you are going to do a lot of dev/tests in your Cloud server, that for sure can raise the costs way more than expected. I know teams should first test on their local machines and then push everything to the cloud server, lambda, whatever you use... but, devs usually don't respect this...
And yes, for many companies their data is still a really valuable asset that they don't want to share with anyone.
I would say when you have something that is going to be cheaper for you to have it in your own server. Not all servers are that expensive (you can even use an old PC for this purpose)if they is only going to be used for a limit amount of users.
Specially when you are going to do a lot of dev/tests in your Cloud server, that for sure can raise the costs way more than expected. I know teams should first test on their local machines and then push everything to the cloud server, lambda, whatever you use... but, devs usually don't respect this...
And yes, for many companies their data is still a really valuable asset that they don't want to share with anyone.
Interesting view, thanks :)