Here at ParkMyCloud, we’re always trying to solve a problem many companies are facing: overspending on cloud. As we now support Microsoft Azure along with Amazon Web Services (AWS), we have spent significant time over the past several weeks talking with analysts, writers, and industry pundits about this problem and our vision for our customers and the ParkMyCloud platform. What is interesting in these discussions is the current size of the public cloud IaaS market ($23B in 2016) and the growth rate (28% in 2016).
The Size of the Massive Public Cloud “Utility”
Most analyst reports clearly state that AWS is the public cloud market leader, with at least 3X the size of Azure in terms of market share, generally measured by revenue. AWS has roughly 31-33% of the public cloud market, while Azure has roughly 11%, followed by IBM Bluemix and Google Compute Engine. All are growing rapidly. In fact, according to analyst reports, the “Big 4” are growing anywhere from 50-100% year-over-year. In fact, each of the Big 4 providers are growing much faster than the industry average – it is a truly disruptive, transformational time in IT.
What comes with this growth is greater adoption. According to Gartner, at the end of 2016 only 14% of enterprise workloads were in the public cloud, but by 2020 they expect that to grow to 41%. That basically means the public cloud needs to triple in size to support this workload migration to public cloud (assuming it’s not already “overbuilt” and new technologies don’t drastically shrink the infrastructure needed to support applications). At these current growth rates, the public cloud infrastructure market will be a $60B+ industry by 2020. This will be one BIG $%# market, right?
Public Cloud: The “Utility” for Enterprises
One way to think about the public cloud is as a “utility” – you can buy services on demand, just like electricity, or water, or heating. Each of these utilities are consumable – as you grow you can consume more, as you shrink you can consume less – it’s elastic. Seems like an interesting parallel to compute, databases, and storage. In the case of the public cloud, you are consuming IT-related infrastructure and services to build, test, and run enterprise and consumer applications which we consume either as an enterprise (e.g., Salesforce) or a consumer (e.g., Netflix) .
But like any utility, there is waste – lights are left on, faucets leak or are left running, and the heat running when you are not home, I am guessing you get the gist. This is why there are now consumer applications like Nest. Buildings and homes alike have ‘automated’ ways to turn lights and water off/on to reduce waste and save money and protect the environment. Why should the public cloud be any different?
Overspending on Cloud Expected to Grow
Enter the problem of overspending on cloud, or cloud waste – servers left running when people are not using them (at nights and weekends), oversized databases and servers not optimized for the applications they support, and storage volumes not being used or “lost” in the cloud. These are just a couple examples, there are many more.
This overspending is a huge problem in the cloud market.
We are excited to share that ParkMyCloud now supports Microsoft Azure scheduling!
For the past 18 months since our launch, Amazon Web Services (AWS) customers have been using ParkMyCloud to manage their compute resources by turning them off when not needed (called “instance scheduling”) – saving a total of $1,749,279.06 so far – and counting!
Now, that same “Nest for the Cloud” capability is available to Microsoft Azure customers.
Plus, if you use both AWS and Azure, you can manage and govern your accounts together in a single ParkMyCloud dashboard.
Why We’re Excited
Being able to control costs with Microsoft Azure scheduling is our most frequently-requested capability – so we’re excited to share this with our customers and new users.
The size of cloud waste is enormous, with up to $5.6 billion wasted every year on computing time that no one is using. While much of this wasted spend is on AWS resources, Azure is certainly the second-biggest player in the public cloud market. We look forward to helping Azure customers eliminate wasted spend. Learn more in our official press release.
How Does ParkMyCloud Work on Azure?
Just like AWS, it’s simple:
Discover: Connect with Azure to discover your virtual machines (VMs)
Schedule: Schedule on/off times for the desired VMs
Smile: Reduce your costs by up to 60%
If you’re new to ParkMyCloud, check out these additional resources:
Zero-Touch Parking – how to use the ParkMyCloud policy engine to create rules for schedules to be automatically applied
Auto-Scheduling for Microsoft Azure Opens Door for Microsoft Azure Customers to Save Millions
January 24, 2017 (Sterling, VA) – ParkMyCloud, the leading enterprise app for optimizing and reducing cloud spend, today announced that it now supports auto-scheduling for Microsoft Azure in addition to Amazon Web Services (AWS). ParkMyCloud launched its “Nest for the cloud” platform in September 2015 to enable AWS customers to automatically turn off idle instances, saving 20-60% on their cloud bills every month. The company has seen rapid customer growth, and customers include companies such as McDonald’s, Sage Software, Neustar, Avid, and Wolters Kluwer.
With Azure, ParkMyCloud significantly broadens its public cloud appeal. AWS has the largest Infrastructure-as-a-Service (IaaS) market share at about 30%, while Azure comes in second at 11%. Adding the second-largest provider means that a greater share of public cloud users can now manage and optimize their resources and get savings on their cloud environments. Additionally, ParkMyCloud now supports not only customers who primarily use one provider or the other, but others who have a multi-cloud environment crossing both AWS and Azure.
451 Research Vice President William Fellows commented on the announcement, saying, “After ParkMyCloud’s work in 2016 deepening their functionality in AWS, supporting Azure helps them target this additional market. The single-purpose tool approach helps ParkMyCloud efficiently address the cloud cost control market and Azure customers should appreciate the new opportunity for simple savings.”
“During 2016, our customers saved over $1.6 million on their cloud bills using our innovative approach to cost savings,” said ParkMyCloud CEO Jay Chapel. “Support for Azure was the top requested feature, so today’s launch will help us drive even bigger growth during 2017 as we become a go-to resource for DevOps and IT users on all the major cloud service providers.”
ParkMyCloud plans to support Google Compute Engine early this year. Following this expansion, ParkMyCloud will broaden its cost-saving offerings to cover databases, storage, and rightsizing.
ParkMyCloud is a simple, single-purpose SaaS tool that enables users to automatically schedule on/off times for their idle cloud computing servers (also known as “parking”). Users save up to 60% on cloud server spend by paying only for the time they actually use to avoid wasted spending. Customers include McDonald’s, Sage Software, Neustar, Avid, Wolters Kluwer and Tristar Medical Group. For more information, visit http://www.parkmycloud.com.
Today I’d like to tell you a story* about how one company learned to control cloud costs. Let me introduce you to Jack.
Jack is the instance slayer.
“The instance slayer?” you ask. “What does that mean? It sounds fun and powerful.”
Powerful? Perhaps. Fun? Not exactly.
You see, Jack is a software engineer at a large financial services company. Unlike some of his co-workers who are more specialized, Jack is, well, a jack-of-all-trades. He does a little in mobile, a little in infrastructure, a little in architecture. He’s busy.
One day, Jack’s boss came to him with a new task.
“We need to take control of our department’s cloud instances to control cloud costs,” his boss said. “I need you to come up with a way to ensure that instances are turned off when they’re not being used.”
So, Jack developed a set of scripts that determined whether everyone’s instances met the new on/off compliance standards. These standards required non-production instances to be “stopped” when not being used. If they were left running when they shouldn’t have been – and a lot were – Jack would first send an email to the owners of the offending instances. But if after the email they still didn’t comply, Jack’s scripts would terminate the instances overnight.
As you can imagine, people got quite annoyed when Jack’s scripts terminated their instances.
“Well, I warned you,” he would say. What could Jack do? This wasn’t his idea. He understood that there was a lot of wasted cloud spend each month, but ultimately this was just a task he was carrying out at the request of his manager.
Nonetheless, Jack made a couple of enemies. They’d call him the Terminator. The Instance Slayer.
Jack didn’t mind the enemies. It was the time out of his day that it took to wrangle them, email them, and clean up their instances that irked him. He had things on his to-do list that he’d much rather spend his time on.
Then, Jack’s teammate Roland introduced ParkMyCloud to the team. A bunch of people tried it out, including Jack.
“This is great,” Jack told Roland. “If I set up simple automated policies to put everyone’s instances on schedules, I won’t need to chase them about turning their resources off when they’re not being used. I’ll have more time for my other projects.”
Everyone else was happy, too. With ParkMyCloud’s simple governance model, Jack and the other administrators could add users and create teams, enabling end-users to apply their own schedules. Plus they got reporting to know if instances weren’t complying. Remember those scripts? Well, Jack didn’t need those anymore.
Jack gets free time: Jack wins. Jack’s teammates get more control over their resources: Jack’s teammates win. Jack’s company gets to control cloud costs by cutting wasted spend on unused cloud time: Jack’s company wins. Win, win, win.
Jack may have stood down as the instance slayer, but his name will live on in legend.
*This is based on a true story! Names changed & company anonymized to protect our customer’s privacy – especially Jack.
As we launch into 2017, we’re looking to bring our public cloud users even more ways to save on their cloud spend. Here’s a preview of some of the more impactful features and functionality we’ll be releasing throughout the year.
New Cloud Service Providers
Thus far, ParkMyCloud has supported customers of Amazon Web Services (AWS) alone. (No small fries here; about 30% of public cloud infrastructure is in AWS). However, in two weeks, we’re expanding by releasing support for Microsoft Azure.You will be able to manage AWS and Azure resources side-by-side in a single dashboard.
In the following months, Google Compute Engine support will follow.
New Ways to Save
In addition to the new cloud service providers, we’re also adding support for additional services and new ways to save on your cloud infrastructure.
We’ll start the expansion from compute services by parking databases (Amazon RDS and others). We will also offer resource rightsizing, so you can ensure that you’re not wasting money on resources that are larger than you need them to be.
Adding to the ParkMyCloud Experience
We’ll also be enhancing the ParkMyCloud experience with surrounding features, starting with single sign-on (SSO) using SAML 2.0 coming in February.
Following that, we’ll add external notifications leveraging AWS SNS. And for the quants out there we’ll be adding a data analytics layer. We’re also excited to share that we’ll have native mobile support for iOS and Androidby the summer.
Of course, as a small and agile company, this list is not complete! We’re happy to hear your thoughts and suggestions about what you’d like to see in ParkMyCloud this year – so what’s at the top of your list?