Google Cloud Run (free)
- Free allowance
- CPU - First 180,000 vCPU-seconds free per month ...
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- free tier
- Identity
- cardcard required, no phone
- Binding limit
- volume-quota1 GiB/month free data transfer within North America
- Evidence
- inferred4 sources; reasoned from other evidence
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | CPU - First 180,000 vCPU-seconds free per month ... RAM - First 360,000 GiB-seconds free per month ... Requests - 2 million requests free per month. unit mixed; metered on request-count |
|---|---|
| Price | USD 0 |
| Limits | |
| Binding | volume-quota 1 GiB/month free transfer is 0.001 TiB; egress past it is billed at Premium tier rates. The transport fails before that. |
| Identity | card A Google Cloud billing account with a payment method; the free tier is a billing discount, not an account without a card. |
| Egress | Outbound internet data transfer is charged at Google Cloud networking rates "with a free tier of 1GiB free data transfer within North America per month".; ingress: http-only free allowance: Outbound internet data transfer is charged at Google Cloud networking rates "with a free tier of 1GiB free data transfer within North America per month". |
| Interface | rest, cli gcloud CLI, REST API, and console. |
| Tooling | gcloud, Dockerfile, or source deploy. |
| Composes with | Cloud Run can host an HTTP API; a WireGuard endpoint needs a VM, not a service. |
| Reliability | Request timeout caps a stream; WebSockets must reconnect. Scale to zero adds cold starts. |
| Notes | Cloud Run also requires a card, so it fails identity for a no-card client even before the transport does. Included here because it is the most common answer to "where do I run this". |
| Evidence note | inferred Cloud Run publishes no page that says "UDP is not supported"; the conclusion follows from the container contract requiring an HTTP listener on one port, and from Google's own developer forum answer that it will not work with UDP. A first-party negative statement would raise this to documented. |
| Parsed numbers |
|
Evidence 4
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | cloud.google.com/run/pricing | Free tier: 180,000 vCPU-s, 360,000 GiB-s, 2M requests; 1 GiB free data transfer within North America |
| 2026-10-23 | docs.cloud.google.com/run/docs/container-contract | "The ingress container within an instance must listen for requests on 0.0.0.0 on the port to which requests are sent." |
| 2026-10-23 | docs.cloud.google.com/run/docs/triggering/websockets | "WebSockets streams are HTTP requests" subject to the request timeout |
| 2026-10-23 | stackoverflow.com/questions/56525366/how-to-deploy-an-udp-se | third party: the container contract requires an HTTP server, so UDP will not work |
More fields 7
{
"wg_path": "none",
"wg_detail": "No raw port. \"The ingress container within an instance must listen for requests on 0.0.0.0 on the port to which requests are sent\"; requests are HTTP, and WebSocket streams \"are HTTP requests\".",
"ingress": "http-only",
"volume_tib_month": 0.000977,
"volume_stated": "Outbound internet data transfer is charged at Google Cloud networking rates \"with a free tier of 1GiB free data transfer within North America per month\".",
"bytes_transit": "no",
"transit_note": "Google's front end terminates HTTP and forwards requests."
}Unknown values 2
$.per_object_cap.statedthe field does not apply to this kind of offer$.retention.statedthe field does not apply to this kind of offer