Deno Deploy vs Google Cloud Run

Deno Deploy and Google Cloud Run cannot be scored on the same axes — one of them does not publish a rate for everything serverless functions bills on.

List prices checked

Rate cards side by side

Only the axes at least one of them bills on. A dash means that provider does not charge for it.

Billing axisDeno DeployGoogle Cloud RunDifference
Entry plan$20.00/mo
Free tierYesYes

Source: Deno pricing (May 2026) · Google pricing (May 2026). Published list prices only — committed-use discounts, regional variation, and per-request charges are not included. Not yet independently re-checked against the vendor’s page.

Monthly cost for three real workloads

The rate cards applied to identical usage. This is where the winner changes.

WorkloadDeno DeployGoogle Cloud RunCheaper
Side projectA personal site or small app with modest traffic, a few gigabytes of assets, and one small always-on process.$20Not comparable
Growing SaaSA funded product serving a few thousand daily users, with an image-heavy frontend and two application servers.$20Not comparable
Media-heavy siteA publisher or video product where delivery dominates the bill and compute is almost an afterthought.$20Not comparable

Workload definitions are identical on every comparison page, so figures here can be read against any other pair in the same category.

What each one is for

Deno Deploy

by Deno

Web-standard JavaScript at the edge with no build step and no bundler configuration, billed on requests and outbound transfer.

Free tier: 1M requests and 100 GB of outbound data per month

Google Cloud Run

by Google

Runs any container with scale-to-zero and request-based autoscaling, billed per 100 ms. The most flexible option in the category because there is no runtime lock-in.

Free tier: 2M requests and 180,000 vCPU-seconds per month

Common questions

Is Deno Deploy or Google Cloud Run cheaper in 2026?
Neither can be scored across all three workloads, because at least one of them does not publish a rate for every axis this category bills on.
Which has the better free tier, Deno Deploy or Google Cloud Run?
Both publish one. Deno Deploy: 1M requests and 100 GB of outbound data per month. Google Cloud Run: 2M requests and 180,000 vCPU-seconds per month.
What do these estimates not include?
Committed-use and reserved discounts, regional price variation, per-request API charges, support plans, and minimum retention periods. All of those move real invoices, sometimes by a lot. These figures compare published list prices for the same workload, which is the comparison the rate cards alone cannot give you.

Other comparisons in this category