ParkMyCloud has developed an innovative cloud parking service that can be used to automatically turn off cloud resources when they are not in use, and turn them on when they are needed, saving companies a small fortune by cutting out cloud expenditure.
The Dulles, VA-based startup’s cloud parking service has been available for AWS resources for some time, and now Azure users can also benefit from the cost savings the offered by its solution.
It made sense ParkMyCloud to initially focus on providing its cloud cost optimization platform for Amazon Web Services, as AWS was the leading cloud provider by some distance. Since the launch of the platform, the firm has been refining its AWS service, and has held back from releasing the tool for Azure, the second biggest player in the market.
Now that its AWS cloud scheduling service has been perfected, and following a new round of seed funding in the fall of 2016 that raised a further $1.65 million in investment, the cloud parking service has finally been brought to Azure.
ParkMyCloud started working with Microsoft in the summer of 2016 and redeveloped its platform to provide the same cost saving benefits to users of Azure. It has taken six months, but support for Azure can now be provided. The Azure parking service was launched at the weekend in beta form.
Customers get the same functionality as its AWS parking service, and similarly, the Azure on/off cloud resource scheduling tool is being provided as Software-as-a-Service.
The new release will see a further 35-45% of the market opened up to ParkMyCloud, helping to drive company growth and help many more businesses save money on their cloud expenditure.
With the Azure parking service now up and running, ParkMyCloud will be switching attention to making its platform available for Google Cloud. The Google Compute Engine is expected to be made available in Q3, 2017, with conservative estimates of 3 months to bring the platform to market.
ParkMyCloud is also currently considering developing its platform for use with IBM’s SoftLayer, although a final decision on the IBM version has not yet been made.
