Cloud Run is a container. You can customize it with any 3rd party frameworks or languages you want. Cloud Functions only support languages and libraries Google Cloud provides. So basically, if you want total control over your environment Cloud Run gives you the most customization. Cloud Functions are smaller, more discreet, event driven code snippets. You can still do amazing things with Functions. It all just depends on what your requirements need. Answer from totally-jag on reddit.com
Google Cloud
cloud.google.com › blog › products › serverless › cloud-run-vs-cloud-functions-for-serverless
Cloud run vs cloud functions for serverless | Google Cloud Blog
November 12, 2022 - Running services, on the other hand, requires more control of the container including choosing the web server or language runtime. For this use case, Cloud Run provides the flexibility needed for these configurations while managing the rest on your behalf. Cloud Functions makes connecting your platform simple to build and easy to maintain — you’re just responsible for the code.
Reddit
reddit.com › r/googlecloud › what are the differences between cloud run & cloud functions?
r/googlecloud on Reddit: What are the differences between Cloud Run & Cloud Functions?
November 17, 2023 -
What are the differences between Cloud Run & Cloud Functions?
and/or advantages/disadvantages
Top answer 1 of 8
11
Cloud Run is a container. You can customize it with any 3rd party frameworks or languages you want. Cloud Functions only support languages and libraries Google Cloud provides. So basically, if you want total control over your environment Cloud Run gives you the most customization. Cloud Functions are smaller, more discreet, event driven code snippets. You can still do amazing things with Functions. It all just depends on what your requirements need.
2 of 8
5
Have you seen this blog post from Google where they compare cloud run & cloud function?
Cloud Run vs Cloud Run Functions
I guess they’re not the same service…? Right now, I created a Node.js project, and ran: gcloud run deploy my-function \ --source . \ --allow-unauthenticated \ --region us-central1 But I’m not sure what it creates… a Cloud Run function, or a Cloud Run Function function (?). I’m re... More on discuss.google.dev
1
0
February 27, 2025firebase - Would I benefit using Cloud run instead of Cloud Functions? Where does it fit in GCP? - Stack Overflow
I use Cloud Functions for most of my backend requirements. What additional benefit does Cloud Run provide to an existing Cloud functions user? Both are managed, has autoscaling, handles HTTP and ar... More on stackoverflow.com
Difference between Cloud Functions Gen.2 and Cloud Run
Hello, Cloud Functions Gen.1 and Cloud Run are both great products that I’ve been using for a while. I understand the differences and limitations of the first generation of Cloud Functions (e.g., 9 minute timeout, limited support for programming languages and tools/system libraries, etc.). ... More on discuss.google.dev
0
1
November 1, 2022What are the differences between Cloud Run & Cloud Functions?
Cloud Run is a container. You can customize it with any 3rd party frameworks or languages you want. Cloud Functions only support languages and libraries Google Cloud provides. So basically, if you want total control over your environment Cloud Run gives you the most customization. Cloud Functions are smaller, more discreet, event driven code snippets. You can still do amazing things with Functions. It all just depends on what your requirements need. More on reddit.com
17
20
November 17, 2023Videos
20:37
Cloud Functions vs. Cloud Run - YouTube
22:02
Cloud Run Functions Explained: evolution from Cloud Function to ...
00:43
#CloudRun or #CloudFunctions #Shorts - YouTube
14:02
Picking the right serverless platform (Part 1) - YouTube
01:40
Cloud Functions in a minute - YouTube
Google
docs.cloud.google.com › cloud run › compare cloud run functions
Compare Cloud Run functions | Google Cloud Documentation
Cloud Run builds functions into containers and deploys them as services. When you deploy a function to Cloud Run, you have complete access and control over the function's behavior.
Modal
modal.com › blog › google-cloud-run-vs-google-cloud-function-article
Google Cloud Run vs. Cloud Run Functions: understanding Google's serverless offerings
September 25, 2024 - Cloud Functions (1st gen): Introduced in February 2016, this was Google’s initial serverless offering for simple, event-driven functions. Cloud Run: Launched later as a more flexible, container-based serverless platform.
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 - Sphere Partners
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 ...
Google Cloud
cloud.google.com › blog › products › serverless › google-cloud-functions-is-now-cloud-run-functions
Google Cloud Functions is now Cloud Run functions | Google Cloud Blog
August 21, 2024 - With Cloud Run functions, we are committed to continuing support for the existing functions APIs, gcloud commands and Terraform modules (Gen 2). This lets you enable Run features on your function without having to refactor your deployment automation. 1st gen functions will continue to be available as Cloud Run functions (1st gen).
Top answer 1 of 2
7
Cloud Functions server instances handle requests in serial, and this is not configurable. Cloud Run instances handle requests in parallel, and the level of parallelism per instance is configurable. This can potentially save you money, if you understand how best to configure a server instance, given the performance characteristics of the code you deploy.
Cloud Functions requires you to choose from among provided language and runtime configurations that are not configurable. Cloud Run lets you run any type of backend configuration you want, assuming that it simply exposes an HTTP endpoint on port 8080.
Cloud Functions provides those selected language and runtime configurations without requiring that you do anything other than deploy code that targets one of those configurations. Cloud Run requires that you supply a docker configuration that establishes the runtime environment (which is more work).
Cloud Functions lets you establish triggers on a wide variety of events that can come from a variety of Cloud and Firebase products. Cloud Run (currently) can be triggered via HTTP requests, PubSub push and a narrow selection of Cloud products (such as Cloud Scheduler and Cloud Tasks).
Cloud Functions requires that you only run your code within the managed provided environments. Cloud Run allows you to take your docker configuration and run it anywhere docker is supported, including GKE, where you gain more control over the server instances.
2 of 2
2
Google Cloud Run fits into your Serverless layer but as a container. The container infrastructure is managed for you.
Cloud Functions are limited in respect to the libraries, languages, and runtimes supported.
Cloud Run removes those limitations. You can use any language, combination of libraries and runtime that supports running within a container.
One limitation is that there is only one internal port $PORT which defaults to 8080 today. Externally both HTTP and HTTPS are supported. Both HTTP and HTTPS map to $PORT.
One big plus is that Cloud Run supports custom DNS names and custom SSL certificates. You can host your website on Cloud Run. As an experiment, I set up WordPress and Cloud SQL on Cloud Run and assigned it a DNS domain name with an SSL certificate.
Datatonic
datatonic.com › insights › cloud-functions-cloud-run-model-serving
MLOps Tools Part 3: Cloud Functions vs. Cloud Run for Model Serving | Datatonic
Functions are quick to deploy and easy to update, and allow easy configuration for ingress, egress and authentication. Cloud Run requires much more engineering knowledge: users need to be familiar with the concepts of containers, and an ...
StackShare
stackshare.io › stackups › google-cloud-functions-vs-google-cloud-run
Google Cloud Functions vs Google Cloud Run | What are the differences? | StackShare
Google Cloud Functions - Construct applications from bite-sized business logic billed to the nearest 100 milliseconds, only while your code is running Google Cloud Run - A managed compute platform that enables you to run stateless containers ...
Medium
medium.com › google-cloud › cloud-run-vs-cloud-functions-whats-the-lowest-cost-728d59345a2e
Cloud Run VS Cloud Functions: What’s the lowest cost? | by guillaume blaquiere | Google Cloud - Community | Medium
November 21, 2019 - The specificity of functions is that you can adjust the memory and the CPU speed, but not separately. Both are linked, increase the memory if you want more MHz and vice versa ... Cloud Run pricing is based on vCPU/s and the memory in Gb/s, rounded ...
Leyaa
leyaa.ai › home › cloud functions vs cloud run: key differences and when to use each
Cloud Functions vs Cloud Run: Key Differences and When to Use Each | Leyaa.ai
March 9, 2026 - Cloud Functions is a serverless platform for running small, event-driven code snippets automatically triggered by events, while Cloud Run runs containerized applications with more control over runtime and scaling.
Medium
medium.com › google-cloud › no-cloud-run-is-not-better-than-google-cloud-functions-f34f46bd3545
No, Cloud Run is not better than Google Cloud Functions | by Beranger Natanelic | Google Cloud - Community | Medium
April 13, 2023 - Cloud Functions: A piece of code deployed online. Responding to HTTP calls or Google Cloud events. Cloud Run: Multiple bigger pieces of code deployed online, big enough to create a server or anything containerisable.
Medium
medium.com › @med.wael.thabet › google-cloud-run-jobs-vs-cloud-functions-key-differences-and-practical-use-cases-1b9a0c6402a6
Google Cloud Run Jobs vs. Cloud Functions: Key Differences and Practical Use Cases | by mohamed wael thabet | Medium
September 13, 2024 - Cloud Functions’ auto-scaling feature is perfect for handling unpredictable spikes in traffic. ... Cloud Run Jobs, on the other hand, target batch processing and long-running jobs.
OneUptime
oneuptime.com › home › blog › how to compare cloud run jobs vs cloud functions vs cloud scheduler
How to Compare Cloud Run Jobs vs Cloud Functions vs Cloud Scheduler
February 17, 2026 - Unlike Cloud Run services (which handle HTTP requests), jobs run a task, finish, and exit. They support parallelism - you can run multiple task instances simultaneously. Cloud Functions run code in response to events or HTTP requests.
Reintech
reintech.io › blog › google-cloud-functions-vs-cloud-run-when-to-use-each
Google Cloud Functions vs Cloud Run: Complete Comparison Guide
March 3, 2026 - Cloud Run, on the other hand, runs containerized applications with full control over your runtime environment. Cloud Functions is opinionated by design. You write a function, deploy it, and Google handles everything else.
Tutorials Dojo
tutorialsdojo.com › home › google cloud › google cloud functions vs app engine vs cloud run vs gke
Google Cloud Functions vs App Engine vs Cloud Run vs GKE - Tutorials Dojo
June 2, 2023 - Serverless compute platforms like Cloud Functions, App Engine, and Cloud Run lets you build, develop, and deploy applications while simplifying the developer experience by eliminating all infrastructure management. On the other hand, Google Kubernetes Engine (GKE) runs Certified Kubernetes that helps you facilitate the orchestration of containers via declarative configuration and automation.
Google
discuss.google.dev › google cloud › serverless applications
Difference between Cloud Functions Gen.2 and Cloud Run - Serverless Applications - Google Developer forums
November 1, 2022 - Hello, Cloud Functions Gen.1 and Cloud Run are both great products that I’ve been using for a while. I understand the differences and limitations of the first generation of Cloud Functions (e.g., 9 minute timeout, limited support for programming languages and tools/system libraries, etc.). ...
Medium
medium.com › @teja.ravi474 › cloud-run-vs-cloud-functions-2c27446ba5f3
Cloud run vs Cloud functions. Cloud Functions vs. Cloud Run | by NRT0401 | Medium
September 25, 2024 - Cloud Functions represents Google Cloud’s event-driven serverless compute service. The fundamental premise behind Cloud Functions is the ability to write and subsequently deploy single-purpose functions.
Towards Data Science
towardsdatascience.com › home › latest › understand and compare cloud functions vs cloud run
Understand and Compare Cloud Functions vs Cloud Run | Towards Data Science
January 23, 2025 - Compare with Cloud Function which only supports one request at a time, Cloud Run is able to be configured to support multiple concurrent requests on a single container instance which allows to save time and save cost.