Google App Engine Reviews and Pricing

Consultant with 51-200 employees

Jul 8, 2013

3 reasons I would choose to use AppEngine

There are 3 reasons I would choose to use AppEngine
1. Software is super simple and working with servers in the future is a no go.
2. Software is going to have 100+ millions users overnight. Will still need to be tweaked and optimized to handle the traffic on AppEngine. I have never seen anyone with this crystal ball but who knows you may have one.
3. Google integration is at the core of the software. AppEngine is really easy to do things like authentication with a Google account. Using Google storage or say the Google SQL service would greatly benefit from the software running inside the Google network.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

it_user7533

Developer at a tech vendor with 51-200 employees

Jul 4, 2013

The hidden cost of Google App Engine

Google App Engine's pricing model costs me way more than the small amount of money I'm charged every week. It costs hours of time.

Now what do I mean by that. I love App Engine and use it every day, there is currently no faster way to get an experiment up and running. The pricing model sounds great: Pay only for what you use. But without realizing, that this model can take giant tolls on development time, it will. At least if you have to care about money.

The problem develops as follows:

1. You have a great new feature to implement.
2. You design a rough implementation, that will get it working asap.
3. You notice a few unnecessary datastore/bandwith/cpu calls/bytes/hours (which AppEngine charges for), that might cost you thousands, if the first few million users hit your site on launch day...
4. But no worries, this can be solved with a slightly redesigned data-model. Go back to 2.

All the momentum you can build up with GAE (setting up a new project in about 5 minutes) can be destroyed in this vicious circle.

Maybe this is common knowledge, but if you are like me, try this:
Ignore everything you know about GAE optimizations and get your feature implemented.
If, one day, millions of people should hit on your site, be happy, pay a higher bill that month and start optimizing.

This should apply to a lot of "Pay as you go" - models out there.

Again, maybe this is just me learning obvious stuff, but this mindset saved me hours, and saving time is great.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Buyer's Guide

Google App Engine

June 2025

Free Report: Google App Engine Reviews and More

Learn what your peers think about Google App Engine. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.

DOWNLOAD NOW

857,028 professionals have used our research since 2012.

it_user7524

Developer at a manufacturing company with 10,001+ employees

Jul 4, 2013

One of the first PaaS solutions around and still one of the best

One of the first PaaS solutions around and still one of the best, Google App Engine is a solid choice to launch your next app idea. You can deploy Java, Python or Go based web apps and enjoy a variety of free and low-cost add-ons.

If you want a mostly-static website with some dynamic content, strongly consider the webapp2 framework. It is light-weight and easy to learn. With just a few lines of Python code, you can deploy an app that can serve a website, provide database backed storage, send emails and make HTTP requests. If you want to go enterprise, it is rare to find a Spring compatible hosting service for cheap, let alone free, but here it is.

One thing that App Engine can do better than any other free service is send emails. If your app needs to send emails, I would strongly consider App Engine. As if that is not enough, your app can actually receive e-mails as well. You can also send and receive instant messages using the XMPP protocol. If your users likely have a Google account, you can authenticate them and consume other Google APIs with ease.

If your website gets incredibly busy you have the option to scale up the performance of your website and pay a small fee. For example, a single massive burst to your site may cost you $0.50 – $1.00. A constantly busy site will cost you more. You have complete control of the billing and can set quotas and alerts. Unlike the other PaaS services, pricing ramps up gradually as your traffic increases.

If your website is not very busy then there is a down-side: Your website may pause for a couple seconds the first time someone accessess a page after it has been idle for some time. In the grand scheme, this is a very minor point, but it is present. Also, signing up for App Engine requires you to authenticate your identity by receiving a text message. Once confirmed, you can deploy a website in about 30 minutes.

Pros: three languages, database support, excellent email sending, Google integration
Cons: Performance can be poor on idle websites, signup requires a text message

Checkout the 5 minute tutorial or sign up.

While Google’s App Engine has a more linear price curve as your app grows in popularity, I have to give creds to Heroku for making pricing simple and clear.

Which to choose?

If you want a static website that showcases your open source involvement, use Github pages.
If you need a static website with geographic diversity and you don’t mind paying a very low amount, or if you need to host large amounts of data (like Videos or file downloads) use Amazon’s S3 service
If you want to host with PHP or you want a very generous PaaS solution and can tollerate unclear vendor support, use Openshift
If you want Ruby on Rails support use Heroku
If you are OK with Python support and/or you need excellent e-mail sending capability use App Engine
If you just don’t know what you want then use App Engine and see if it meets your needs. If it doesn’t, by then you’ll know what you do want and can pick the right tool.

Read the full post on my blog.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

it_user4401Developer at a transportation company with 1,001-5,000 employees

Report as inappropriate

Jun 9, 2014

You are right, I can deploy Java, Python or Go based web applications. Related to this topic, do you know which JVM languages I can use in my App Engine application?

it_user3636

Principal Consultant/VP of Technology

Jan 11, 2013

Download

Easy to upload from IDE. ...

Valuable Features:

Easy to upload from IDE.

Room for Improvement:

Need a better documentation and tech support.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

it_user1158

Developer at a tech company with 51-200 employees

Jul 18, 2012

Download

Overall a good and cheap platform with scalability support. Good for individuals and startups, but not suitable for heavy/large applications.

Valuable Features:

- A very good platform for those applications that store something and retrieve it back. - Google takes care of deploying the code to the clusters, monitoring, failover, and launching application instances as and when necessary. This takes a lot of the administrative work off the user. - Easy and cheaper (in the short term) - Unlimited scalabity to your application, and scales with demand. - GAE supports MySQL db as well. - App Engine doesn't provide you with the flexibility to use an equivalent service if you need to pick something else for your app.

Room for Improvement:

- Developers have read-only access to the filesystem on the Google App Engine. - GAE is not suitable for CPU intensive calculations. - You cannot produce a social graph using Google app engine. - Once you think of migrating out of the AppEngine world, you'll face a lot of problems. For example, having to change your code to use your own datastore, task queues, and other services. If your application is fairly large, this will be a very difficult process. - Since the backend is completely manage by Google, you don't have control over the environment your application runs in. - Apart from the free space and to build some "Hobby" websites, Google App Engine is not the place java guys should look in as Java is quite heavy on memory front.

Other Advice:

Overall a good platform for running small applications that basically deals with storing and retrieving data from backend. Since the backend is handled by Google, you get a scalable app platform, but at the cost of losing control over the backend environment. You cannot tweak the backend and you just have to leave with whatever Google has to offer.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

it_user3876Database Manager at a tech company with 51-200 employees

Report as inappropriate

Jun 23, 2013

There are a number of reasons that make GAE a good choice including automatic scaling, easy to code and setup configuration files and a pre-configured architecture that makes application development easier.

See all 2 comments

it_user981

Manager of Development at a tech company with 51-200 employees

Jun 25, 2012

Download

A good application hosting option for short term, low budget startups

Valuable Features:

Zero maintenance cost for web servers Reliable for scalability Free basic account with limited quota for trial Suitable for startups with limited users and limited resources

Room for Improvement:

No filesystem access More expensive than the alternate options if a product/service has a lot of users Language support limited to Java and Python Database options limited to MySQL and Google data store

Other Advice:

I have been using it for a startup for over an year. Initially it was great, but with an expanding user base, it makes more sense to host my own servers.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

it_user82776Chief Executive Officer at a tech services company with 1,001-5,000 employees

Report as inappropriate

Feb 12, 2014

I think having 5 developers working with you to allow for patching upgrade and zeroing down on scalability, and yes having your own server will help the effects of over expanding customer base. Like the Khan Academy did.

See all 2 comments

reviewer1624092

DirectorManaging Partner at a tech services company with 11-50 employees

Nov 15, 2021

Download

Effective self-management and implementation is straightforward

Pros and Cons

"Google App Engine's most valuable feature is self-management. You do not have to manage the infrastructure underneath where all the functions are happening, such as load balancing deployment and version management, they are managed by the system itself."

"The only concern is that there is a number of the offerings which are built on their own proprietary technologies. With some of the offerings in Google Cloud, it's difficult to have a path to migrate to other cloud providers."

What is our primary use case?

We have five Google App Engine applications deployed on private clouds, and we have some deployed on public clouds. We use both Google and Microsoft.

What is most valuable?

Google App Engine's most valuable feature is self-management. You do not have to manage the infrastructure underneath where all the functions are happening, such as load balancing deployment and version management, they are managed by the system itself.

Google Cloud has a number of products that complement each other in being able to provide solid cloud feature sets. We've had many products that are available on Google Cloud and you are able to build whatever you want. There's always a solution for what you need.

What needs improvement?

The only concern is that there is a number of the offerings which are built on their own proprietary technologies. With some of the offerings in Google Cloud, it's difficult to have a path to migrate to other cloud providers.

For how long have I used the solution?

I have been Google App Engine for approximately four years.

How was the initial setup?

The solution is easy to deploy.

What other advice do I have?

I rate Google App Engine an eight out of ten.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.