# Google Cloud and Temporal preview serverless workers

> Google Cloud and Temporal opened a preview integration that runs Temporal Cloud workers on Cloud Run worker pools. Temporal adjusts pool capacity by tracking task-queue delay, and the pool can scale to zero when idle. Workers run in the customer’s project, under its service account and network.

- Canonical URL: https://newsverum.com/en/news/google-cloud-temporal-serverless-workers-cloud-run-preview
- Publisher: Newsverum
- Section: Technology
- Published: 2026-10-15T22:00:39+00:00
- Updated: 2026-10-15T22:00:39+00:00
- Event / data period: 2026-10-15
- Other editions: [Türkçe](https://newsverum.com/tr/news/google-cloud-temporal-serverless-workers-cloud-run-preview.md), [العربية](https://newsverum.com/ar/news/google-cloud-temporal-serverless-workers-cloud-run-preview.md), [Français](https://newsverum.com/fr/news/google-cloud-temporal-serverless-workers-cloud-run-preview.md), [Español](https://newsverum.com/es/news/google-cloud-temporal-serverless-workers-cloud-run-preview.md), [Deutsch](https://newsverum.com/de/news/google-cloud-temporal-serverless-workers-cloud-run-preview.md), [Português](https://newsverum.com/pt/news/google-cloud-temporal-serverless-workers-cloud-run-preview.md)

The source says pools have no public endpoint, use separate resources per build version, and scale when task latency rises. Google says worker pools list at nearly 40% less per vCPU-hour and GB-hour than request-billed services. That is the providers’ price comparison; actual cost and capacity depend on workload.

## Data

### Google Cloud and Temporal preview serverless workers

Google Cloud and Temporal opened a preview integration that runs Temporal Cloud workers on Cloud Run worker pools. Temporal adjusts pool capacity by tracking task-queue delay, and the pool can scale to zero when idle. Workers run in the customer’s project, under its service account and network. The source says pools have no public endpoint, use separate resources per build version, and scale when task latency rises. Google says worker pools list at nearly 40% less per vCPU-hour and GB-hour than request-billed services. That is the providers’ price comparison; actual cost and capacity depend on workload.

Methodology: This record summarizes the named primary source and its reported measurements; no independent test or survey verification was performed.

| date | label | description | status |
|---|---|---|---|
| 2026-10-15 | Google Cloud and Temporal opened a preview integration that runs Temporal Cloud workers on Cloud Run worker pools. Temporal adjusts pool capacity by tracking task-queue delay, and the pool can scale to zero when idle. Workers run in the customer’s project, under its service account and network. | Google Cloud and Temporal opened a preview integration that runs Temporal Cloud workers on Cloud Run worker pools. Temporal adjusts pool capacity by tracking task-queue delay, and the pool can scale to zero when idle. Workers run in the customer’s project, under its service account and network. The source says pools have no public endpoint, use separate resources per build version, and scale when task latency rises. Google says worker pools list at nearly 40% less per vCPU-hour and GB-hour than request-billed services. That is the providers’ price comparison; actual cost and capacity depend on workload. | occurred |

Sources: <https://cloud.google.com/blog/products/serverless/temporal-serverless-workers-on-cloud-run-worker-pools> · Download data: [JSON](https://newsverum.com/api/v1/articles/google-cloud-temporal-serverless-workers-cloud-run-preview/data/source-report?lang=en&format=json) · [CSV](https://newsverum.com/api/v1/articles/google-cloud-temporal-serverless-workers-cloud-run-preview/data/source-report?lang=en&format=csv)

## Sources

- [Google Cloud](<https://cloud.google.com/blog/products/serverless/temporal-serverless-workers-on-cloud-run-worker-pools>) (Source checked: 2026-10-15; Published: 2026-10-15)

---

Cite the canonical URL above. [Editorial standards and corrections](https://newsverum.com/en/editorial)