---
title: "Cloud Run or while in 2026: Google Cloud or a team tool"
url: https://while.sh/en/comparisons/while-vs-cloud-run/
author: "Grégoire Mougeolle, co-founder of Nextmap"
updated: 2026-11-19
---

# Cloud Run or while in 2026: which one to choose when your AI publishes your tool

Cloud Run runs your containers on Google Cloud, pay as you go, with a region in Paris and IAP to restrict a tool. while shares the tool your AI built, with its data, the whole team and your clients, in France, with nothing to configure. We compared them in November 2026.

Cloud Run runs **your containers on Google Cloud**, pay as you go, with a region in **Paris** and **Identity-Aware Proxy** to restrict a tool. while answers a more direct case: **the team tool your AI builds**, with its data. It is shared with your colleagues and clients, in France, **with nothing to configure**.

> **Our verdict.** while, for a team tool your AI built, with its data in France. Your colleagues' sign-in and a client's password are ready right away. Cloud Run only if your team already lives in Google Cloud, or if the app must run in several regions of the world.

## Cloud Run and while at a glance

| | Cloud Run | while |
|---|---|---|
| Who it is for | A team already in Google Cloud | A team sharing the tools its AI builds |
| Price | Pay as you go, with a monthly free quota | Free for up to 3 people, Pro for the whole team |
| Where it runs | The region you choose, Paris possible | In France, at Nextmap |
| The data | Another Google Cloud service, to configure | With the tool, backed up every day |
| Your colleagues | Identity-Aware Proxy, to configure | Their email account on the Pro plan |
| A client | Whatever the tool provides | A link and a password, valid for 1, 7 or 30 days |

Cloud Run's facts come from Google Cloud's documentation, cited as sources (sources 1, 2 and 3).

## What Cloud Run does

Cloud Run bills **by usage**, rounded up to 100 milliseconds, with a **monthly free quota**: 180,000 vCPU-seconds, 360,000 GiB-seconds of memory and 2 million requests with request-based billing (source 1). It runs in many regions, **Paris** included (source 2).

while also puts a lightly used service to sleep, so it reserves nothing, and counts what it uses by the second.


## What needs configuring: while wins

At Cloud Run, you build the container, choose the region, link **the data to another Google Cloud service**, and configure **Identity-Aware Proxy** to restrict the tool. IAP is free for its features, but networking and compute are billed (source 3).

On while, **your AI sets up the tool and its data**, in France, and the team's sign-in is ready. The data is backed up every day, with a way back over 14 days.

<figure class="illus"><img src="/illustrations/cloudrun-while-pieces-1200.webp" srcset="/illustrations/cloudrun-while-pieces-768.webp 768w, /illustrations/cloudrun-while-pieces-1200.webp 1200w" sizes="(min-width: 48rem) 46rem, 100vw" width="1536" height="1024" loading="lazy" decoding="async" alt="Cloud Run or while for a team tool: at Google Cloud a container, a region, a database in another service and Identity-Aware Proxy to configure, on while the tool built by AI set up with its data in France and the team signed in" /><figcaption>At Google Cloud, the container, database and IAP to configure. On while, the tool is ready.</figcaption></figure>

## The team and clients: while wins

On while, **your colleagues sign in with their email account**, Google or Microsoft, on the Pro plan, with no per-person price, and **a client** uses the tool with [an access link and a password](/en/guides/share-app-with-password/), valid for 1, 7 or 30 days.

> You, to your AI: Put our scheduling tool on while, with its data, keep it for the team and prepare a link for the client.

What matters, **a production release, deleting a database, an outside API, an access**, waits for a person's approval, and the credentials of your software stay in while, out of your AI's reach.

To compare, read [Cloudflare Access or IAP or while](/en/comparisons/cloudflare-access-iap-vs-while-2026/), [Firebase or while](/en/comparisons/while-vs-firebase/) and [where to put an internal tool](/en/comparisons/internal-tool-hosting/).

## Which one to choose

**Choose while if:**

- Your AI built the tool and it must serve the team right away, sometimes a client.
- You want your data in France, with nothing to configure.

Pick Cloud Run only if your team already lives in Google Cloud, or the app must run in several regions of the world.

To try while, give this message to your AI. The trial is **free, with no sign-up**, and your tool has its address **in 3 minutes**.

```text titre="The message to give your AI"
Read while.sh/agents and help me get started with while.
```

## How we compared

On November 19, 2026, we read Google Cloud's documentation on Cloud Run pricing and locations and on Identity-Aware Proxy pricing, cited as sources, and we used while ourselves. Google sometimes changes its plans: we update this page when they change.

## Sources

1. [Google Cloud, Cloud Run pricing](https://cloud.google.com/run/pricing), 2026-11-19
2. [Google Cloud, Cloud Run locations](https://cloud.google.com/run/docs/locations), 2026-11-19
3. [Google Cloud, Identity-Aware Proxy pricing](https://cloud.google.com/iap/pricing), 2026-11-19

## Questions

### How much does Cloud Run cost?

It is pay as you go, rounded up to 100 milliseconds. Each month, 180,000 vCPU-seconds, 360,000 GiB-seconds of memory and 2 million requests are free with request-based billing (source 1).

### Does Cloud Run have a region in France?

Yes, Paris, europe-west9 (source 2). On while, your tools and their data are in France, with no region to choose.

### How do you restrict a Cloud Run tool to your colleagues?

With Identity-Aware Proxy, free for its features, but networking and compute are billed, and it must be configured (source 3). On while, your colleagues sign in with their email account on the Pro plan.

### Where does a Cloud Run tool's data live?

In another Google Cloud service, to choose, configure and pay for separately. On while, the data lives with the tool, backed up every day.

### Which one to choose for a tool built with AI?

Cloud Run, if your team already lives in Google Cloud and knows how to configure it. while, if the tool must serve the team right away, with its data in France.
