I think that Cloud Run is superior to App Engine, but the things that matter to me may not matter to you. Cloud Run lets you use containers, any programming language, any web framework, and include your own binaries. If these things sound useful to you, switch to Cloud Run. If not, stay with App Engine. Hope this helps! Answer from martin_omander on reddit.com
🌐
Google
docs.cloud.google.com › app engine › migration center › compare app engine and cloud run
Compare App Engine and Cloud Run | App Engine migration center | Google Cloud Documentation
Cloud Run is designed to improve ... environment. Cloud Run services can handle the same workloads as App Engine services, but Cloud Run offers customers much more flexibility in implementing these services....
🌐
Reddit
reddit.com › r/googlecloud › cloud run vs appengine?
r/googlecloud on Reddit: cloud run vs appengine?
December 11, 2022 -

I run a number of small websites on AppEngine. Mostly static files, occasionally a little bit of code.

I constantly hear that Cloud Run is superior to AppEngine... is it for my use case?

I don't think cloud run has a nice way to serve the static files, is that correct?

Top answer
1 of 10
13
I think that Cloud Run is superior to App Engine, but the things that matter to me may not matter to you. Cloud Run lets you use containers, any programming language, any web framework, and include your own binaries. If these things sound useful to you, switch to Cloud Run. If not, stay with App Engine. Hope this helps!
2 of 10
10
Disclosure: We have an App for Google App Engine (GAE) I think it depends on your purposes. GAE in my comments below refers to GAE Standard Environment - I think GAE is simpler to use/understand (especially for someone who isn't very technical or is still kind of new to programming). You just write code. You don't have to worry about 'containerizing or what it means'. When you're done writing code, you deploy (you don't have to worry about 'building' your App and stuff like that. It's also simpler/easier if you're hosting static sites. - GAE gives you access to a NoSQL DB (datastore) so you don't have to worry about setting up/configuring an SQL server. GAE also comes with bundled APIs which means you don't have to spin up servers or connect to some external services. Eg. you want users to sign in before accessing your site, just add login:required to your app.yaml, you want to restrict some page to only your admin, add login:admin to the route in app.yaml, you want your site to only be accessible via https, add 'secure:always' to your app.yaml file, you want to use memcache, just import the library (one liner) in your code and start using it, you want to save data to datastore, just import the library (one liner) and start using it - However, GAE runs your code in a sandbox which means you can't do stuff that GAE doesn't support. Cloud Run doesn't have that limitation. With Cloud Run, you have access to more programming languages (essentially any language), your code has a longer time out (i.e. the time it takes for your app to return a response is much longer), you can use stuff like Selenium (headless browsing), streaming, instant messaging (pub/sub), etc - Cloud Run also supports deploying to multiple regions. GAE only supports deploying to a single region and you can't change the region after it's set. Under normal circumstances, this wouldn't be a problem but once in a while Google Cloud has issues and some regions basically won't respond (this happened about 2 weeks ago or so; there were multiple complaints from folks that they were getting errors about a region being out of resource). When such happens, Cloud Run has the advantage in that your App could still be served from the other regions that you deployed
Discussions

App Engine Standard vs Cloud Run trade offs - Stack Overflow
I have a web app currently running on App Engine (Python 3). It is always getting traffic (i.e., never needs to scale down to 0), and it could easily be deployed as container if necessary (i.e., ei... More on stackoverflow.com
🌐 stackoverflow.com
node.js - Building a Node app should I use App Engine or Google Cloud Run? - Stack Overflow
I am creating a Node app it has express, swagger and Agenda for running scheduled Jobs. What is the best way to deploy it in GCP. Should I use App Engine or Cloud run. From what I understand in Clo... More on stackoverflow.com
🌐 stackoverflow.com
Are AppEngine/Cloud Run really the much simpler/more stable?
Forget Cloud Run and App Engine, why would you want to SSH into a container? If you have a legitimate need for that, either you're doing containers wrong or your use case doesn't work with containers. More on reddit.com
🌐 r/googlecloud
14
8
December 6, 2022
Anything between VMs and App Engine/Cloud Run?
Maybe the obvious question, but can your state be stored elsewhere? Storage, Firestore, Data store, memorystore, etc More on reddit.com
🌐 r/googlecloud
35
11
December 10, 2023
🌐
Northflank
northflank.com › blog › app-engine-vs-cloud-run
App Engine vs. Cloud Run: A real-world engineering comparison | Blog — Northflank
May 23, 2025 - You bring your own Docker image (or use Cloud Build to create one), and Cloud Run runs it in a serverless fashion. You’re not limited by language or runtime, and you can configure things more granularly. It’s technically closer to Kubernetes and Knative than traditional PaaS, but Google’s abstraction makes it feel almost as easy to use as App Engine.
🌐
Google Cloud
cloud.google.com › run
Cloud Run | Google Cloud
Cloud Run services can handle the same workloads as App Engine services, including deploying and hosting websites, but Cloud Run offers customers much more flexibility in implementing these services.
🌐
Sphere
sphereinc.com › blogs › when-to-choose-app-engine-vs-cloud-functions-or-cloud-run-in-gcp
Cloud Run vs App Engine vs Cloud Function
January 29, 2025 - Unlike in GCP App Engine where data is shared among instances, once a function is invoked with Cloud Functions, it is on its own, so if you need to keep track of data when using Cloud Functions, you'll need to use a database or writable file ...
🌐
DEV Community
dev.to › pcraig3 › cloud-run-vs-app-engine-a-head-to-head-comparison-using-facts-and-science-1225
Cloud Run vs App Engine: a head-to-head comparison using facts and science - DEV Community
November 27, 2020 - This study finds that Cloud Run is usually the best option, although if you · have money to burn are a “price insensitive consumer,” then App Engine is a bit zippier.
Find elsewhere
🌐
Medium
medium.com › google-cloud › google-app-engine-in-2025-serverless-simplicity-vs-cloud-run-and-gke-d46f485cf908
Google App Engine in 2025: Serverless Simplicity vs Cloud Run and GKE | by Aleksei Aleinikov | Google Cloud - Community | Medium
May 27, 2025 - Cloud Run, however, starts faster, bills per CPU-millisecond, and stops at zero — something Flexible can’t. Where you lose out is built-in traffic-splitting across named versions and the long list of tiny App Engine conveniences (cron UI, Task Queues, warm-up hooks).
🌐
Medium
medium.com › google-cloud › cloud-run-vs-app-engine-whats-the-lowest-cost-6c82b874ed61
Cloud Run VS App Engine: What’s the lowest cost? | by guillaume blaquiere | Google Cloud - Community | Medium
February 1, 2023 - The “Per request” option; the default Cloud Run behavior · The “Always ON” option; with the no CPU throttled option set · Duplicate it in your account to update the values and perform your own simulation. Whatever the option, the clear advantage of App Engine is the free tier.
🌐
Server Fault
serverfault.com › questions › 961983 › are-compute-engine-app-engine-for-different-usage-or-complementary
cloud - Are Compute Engine & App Engine for different usage or complementary? - Server Fault
Compute Engine provides VM instances and associated infrastructure. App Engine provides development kits to deploy applications on instances managed for you.
🌐
OneUptime
oneuptime.com › home › blog › how to choose between cloud run cloud functions app engine and gke
How to Choose Between Cloud Run Cloud Functions App Engine and GKE
February 17, 2026 - Cloud Run: You have a containerized application or API. It can be stateless. You want automatic scaling including scale-to-zero. This is the default choice for most new projects. App Engine: You want a PaaS with managed deployment, traffic ...
🌐
Google
firebase.google.com › pricing
Firebase Pricing
Use the Google Cloud calculator to estimate project costs.
Top answer
1 of 2
38

App Engine is a Platform-as-a-Service. It means that you simply deploy your code, and the platform does everything else for you. For example, if your app becomes very successful, App Engine will automatically create more instances to handle the increased volume.

It auto scales from 0 to unlimited instances (It uses GCE underneath). It comes with 2 flavors Standard Environment and Flexible Environment. Standard Environment is really fast, scales down to 0 instances when no-one is using your app, scales up and down in seconds and has dedicated Google services and libraries for caching, authentication etc. The caveat with Standard environment is that it is very restrictive since it runs in a sandbox. The recent additions are Node.js (8.x) and Python 3.x. Flexible Environment is more open as it allows you to use custom runtimes as it uses docker containers. Thus if your runtime is not available in the provided runtimes, you can always create your own dockerfile for the execution environment. The caveat with it is, it requires having at least 1 instance running, even if no-one is using your app, plus the scaling up and down requires a few minutes.

Read more about App Engine

App Engine is for deploying code, Cloud Run for deploying containers, and containers are today’s requirements.Cloud Run runs containers, so for each release you have to build a container and push it to GCP.

Cloud Run, App Engine Flexible and Newer runtimes of App Engine Standard are designed for portability (you can use open-source libraries or standard libraries and not just Google Libraries). Cloud Run and App Engine Flexible allow for custom runtimes.

Cloud Run gives you the freedom to expand your infrastructure into hybrid and multi-cloud environments.

Read more about Cloud Run

Differences you should consider:

  • For a low-traffic application, Cloud Run or App Engine Standard which is set to automatic scaling are both cheaper than App Engine Standard which is set to manual/basic scaling or App Engine Flexible. Cloud Run only runs when it is serving requests. App Engine which is set to automatic scaling shuts down when it is not serving requests. This means for both types, you're not using resources when your application is not running and Google only bills you for resources that you consume. In addition, App Engine Standard provides a free daily quota of resources so you're only billed for consuming resources above the free quota. App Engine Flexible or App Engine Standard set to manual/basic scaling must have at least 1 instance running continuously, which means they run for a full month which in turn means you're going to pay more.

  • App Engine responds on average 56 ms faster than Cloud Run. The huge caveat here is that these times vary widely between runs, sometimes tripling or quadrupling The total request size from Cloud Run was larger because it doesn’t gzip files by default. The big difference between the two services is that Cloud Run doesn’t run your container unless it’s getting requests. When a request comes in, it does things: [i] boots up the container [ii] serves the request [iii] shuts down the container Of course, you also save a lot of money doing it this way, so the tradeoff here is whether you care more about optimizing your speed or your cost.

  • AppEngine can only be deployed to a single region. If you want an AppEngine app to be multi-regional then you need one project per region. Cloud run allows you to deploy a service to every region within a single project making your API truly global, all within a single project

  • Cloud Run also allows you to set up a static IP address, something you cannot get with AppEngine. This is helpful for situations where you need to relay mail or connect to some other service that restricts access by IP address. Also AppEngine still has some things Cloud Run doesn't (like Identity Aware Proxy) have.

  • The docker image support in Cloud Run is also more versatile than what you get from AppEngine Standard, and Cloud Run has more robust options to choose from (more ram, cpu, etc).



1https://cloud.google.com/appengine/docs/standard/nodejs/quickstart 2https://cloud.google.com/run/docs/quickstarts/build-and-deploy/deploy-nodejs-service

2 of 2
1

Google App Engine:
App Engine provides a fully managed platform-as-a-service (PaaS) environment. It offers automatic scaling, load balancing, and other infrastructure management tasks out of the box.

Google Cloud Run:
Cloud Run is a serverless container platform that runs stateless containers on demand. It provides a more flexible and customizable environment compared to App Engine. You can deploy your Django app as a containerized application using Docker. Cost efficient than App Engine

🌐
Whizlabs
whizlabs.com › labs › why-to-choose-cloud-functions-over-app-engine-and-cloud-run
Why to choose Cloud Functions over App Engine and ...
Learn in Real-time with Hands-on labs on AWS, Google Cloud, and Azure Console - No Credit card Required. Enjoy experiential Learning with Whizlabs!
🌐
StackShare
stackshare.io › stackups › google-app-engine-vs-google-cloud-run
Google App Engine vs Google Cloud Run | What are the differences? | StackShare
In Summary, Google App Engine and Google Cloud Run differ in deployment flexibility, scalability, pricing model, portability, execution environment, and use cases, catering to distinct application development requirements.Read more
🌐
Google Skills
skills.google › course_templates › 153
Google Cloud Computing Foundations: Cloud Computing Fundamentals | Google Skills
1 week ago - This first course provides an overview of cloud computing, ways to use Google Cloud, and different compute options.
Rating: 4 ​ - ​ 20 votes
🌐
Dbztech
dbztech.blog › 2025 › 11 › 29 › google-cloud-run-vs-google-app-engine
Google Cloud Run Vs Google App Engine – DBzTech-Technology Dossier
November 29, 2025 - When exploring Google App Engine (GAE) as part of your Google Cloud learning journey, especially for the Google Cloud Digital Leader Certification, it becomes clear that while GAE is a powerful PaaS solution, it has a key limitation: programming language compatibility. This limitation paved the way for a more flexible, container-native solution—Google Cloud Run.
🌐
YouTube
youtube.com › watch
Picking the right serverless platform (Part 1) - YouTube
Google App Engine was our very first cloud and serverless product, but now it has been joined by Google Cloud Functions and Cloud Run. Choosing a platform is...
Published   July 7, 2022
🌐
Dormoshe
dormoshe.io › trending-news › cloud-run-vs-app-engine-a-head-to-head-comparison-using-facts-and-science-1225-16867
Cloud Run vs App Engine: a head-to-head comparison using facts and science
I was hosting a small web app as a side-project and looking to spend less money. I started out using Heroku, then moved to Google’s Cloud Platform. Using rigorous methods and markdown tables, I per...