Google Adjusts GAE Pricing Terms Based on User Reaction
Google has reacted to recent developments regarding the increase in GAE prices which took developers by surprise, making a number of adjustments to the pricing plan, the most important being: the new billing is delayed until November 1st and the number of free Instance-Hours is raised from 24/day to 28/day.
Google announced that GAE will leave the 3 years long preview state and enter normality back in May at IO 2011, practically saying that the previous pricing scheme did not provide enough revenue to sustain their cloud business:
In order to become an official Google product we must restructure our pricing model to obtain sustainable revenue. Based on customer feedback this means focusing on usage-based pricing and placing per-user, per-app pricing on hold until further notice.
At that time, they announced a new pricing list and details on how users will be affected and how they can see the costs under the new pricing options. Google said that several features available to GAE business users (GAE4B) will be available to everyone, including “SLA, SSL for custom domains, SQL, Operational and Developer support, and the new business-oriented Terms of Service.”
Google also announced new Usage Types – Free, Paid Apps, and Premier Accounts –, and new usage fees for Instances, APIs, and Datastore Storage. The most important change seemed to be that from paying per CPU cycles to paying for Instance-Hours (IH). Under the new pricing scheme, one would pay for each application instance running even if that application is mostly idle. Also, the quotas for free usage have dropped, especially the API calls.
Google reiterated their intent to switch to the new billing system on August 31, saying that it will go into effect in the second part of September. Unlike the previous announcement which went mostly unnoticed, this want created a strong reaction among Google’s over 100,000 GAE developers, many being surprised by the change, and some expressing their dissatisfaction and announcing moving to other cheaper solutions.
Analyzing some of the comments posted by people on Google’s blog post, it seems that most complains come from people having simple websites, mostly static, and being idle most of the time. This is the case of Guillaume Laforge, Groovy Project Manager, who commented on a related Google Plus post:
I have a simple blog application (http://glaforge.appspot.com), with not much traffic, but enough of regular hits from random guys, feed readers, and Google search bots to keep my blog instance always on. Despite having toggled the "sliders" (max instances / idle time), my small blog will cost me quite a bit. I was really expecting a small blog website wouldn't be not free to run. I'm really disappointed.
Ten days later, Google reacted and announced a number of adjustments to the new GAE pricing. Besides better analysis tools, comparative usage reports, an extended 50% discount on instance prices until December 1st, and the intent to introduce Premier Accounts as soon as possible, the main adjustments are:
- the new pricing scheme will be applied from November 1st, leaving developers more time to think things over and decide what is best for them, to stay with GAE or to move to another cloud
- 28 free Instance-Hour/day instead of 24/day, allowing developers to test their applications by running an instance for an entire day and have a few occasional spikes when more than an instance is started
Also, Google has provided advice on how to lower the costs of running apps on GAE and how to manage resource usage, but the basics are: lower the number of running instances to a minimum possible and using reserved Instance-Hours which are cheaper. A developer applied the advice and wrote:
My billing went from $0.14/day to $3-$4/day (i can't afford $4/day... $1/day is my maximum right now). I set the "Set Max Idle instances" to 1 since I don't really need more than that most of the time, the 5-8 instances that I had were idle almost all day serving few requests. My costs are down to $0.39/day. 3x increase is more than ok with me, the old prices were to cheap anyway.
Premier Accounts offer the opportunity to large businesses to pay a monthly $500 fee for one account without having to pay $9/month/application as it is the case for Paid Apps. But there are still additional fees for running instances and using bandwidth. Although Google has touted the new GAE features as beneficial for large organizations, their costs will rise by a factor of 2 to 5, according to Peter Magnusson, Engineering Director at Google responsible for App Engine:
That said, the new App Engine prices are higher. In fact I expect many large applications after optimizing will end up paying 2-5x more than before. Many small applications will no longer fit into the free quota without optimization or performance tradeoffs. And many applications that only had to pay a little bit above free quota now have to pay more.
Google still believes their pricing is competitive to other offers, and invites developers to write to email@example.com if that’s not their case.
Caitie McCaffrey Apr 24, 2015