It was late 2015 when the path of a local business owner crossed with mine, and I was told his sad story of vendor lock-in.
The business owner had become very frustrated with the software vendor who had implemented his Umbraco website. The owner was unable to make updates to his site and was reluctant to work with the vendor on implementing new features.
My task was simple: free the client from their vendor lock-in, implement changes for the site, and develop a management process going forward. We needed hosting, source control, and work item management. I began a search to determine what would work best for this client.
Initially, since the client was already doing work with a large ISP well-known for their DNS management, there was a push to see if they could help with the ASP.NET website hosting as well. Although they did offer such a service, the UI to manage the application was outdated and not user-friendly.
We decided to move forward with Git since it had become the source control system of choice in many programming circles. I understood the tool well as would anyone else he brought in for future work. While the de-facto choice may be GitHub, there's an infinitely big difference between free and almost free, so the need for private repositories lead us to BitBucket.