> But then, What stops SaaS providers from Hosting in their own environment?
You mean why SaaS providers are reluctant to provide their stack on-premise?
If your main tech is providing a web daemon that "just works" it is simpler (cheaper) to provide (install, update, configure) it on your (the SaaS-company's) infrastructure, as otherwise you have to support integrating your SaaS into the security domain of your customer which is very non-trivial (that's why you often see Team-Support and certain variations of authorization and authentication in the higher-priced plans).
I understand that many customers would like that but I also understand that it is harder (more expensive) to support for SaaS companies. I wonder how long GitLab will support their dual-approach using .com and the self-hosted, on-premise variant.
You mean why SaaS providers are reluctant to provide their stack on-premise?
If your main tech is providing a web daemon that "just works" it is simpler (cheaper) to provide (install, update, configure) it on your (the SaaS-company's) infrastructure, as otherwise you have to support integrating your SaaS into the security domain of your customer which is very non-trivial (that's why you often see Team-Support and certain variations of authorization and authentication in the higher-priced plans).
I understand that many customers would like that but I also understand that it is harder (more expensive) to support for SaaS companies. I wonder how long GitLab will support their dual-approach using .com and the self-hosted, on-premise variant.