Google Cloud Run vs E2B

Runs untrusted code inside an existing Cloud Run workload. A preview option for teams that already host agents on Cloud Run. Google Cloud Run does not publish comparable vCPU and memory rates, so no hourly price is compared; E2B lists $0.166 an hour for a 2 vCPU / 4 GiB sandbox.

google-cloudhyperscalermanagedpreview

Verified 11 Nov 2026

Visit Google Cloud Run Compare with E2B and others

Google Cloud Run against E2B, line by line

E2B baseline sources

Field	-E2B (baseline)	+Google Cloud Run	Change
2 vCPU + 4 GiB, per hour	$0.166 (source: E2B Pricing)	not published	Google Cloud Run: no figure
vCPU, per hour	$0.0504 (source: E2B Pricing)	not published	Google Cloud Run: no figure
Memory, per GiB-hour	$0.0162 (source: E2B Pricing)	not published	Google Cloud Run: no figure
Billed on	wall clock (source: E2B Pricing)	not published	Google Cloud Run: no figure
Isolation	Firecracker microVM (source: E2B homepage)	process sandbox (source: docs.cloud.google.com/run/docs/code-execution)	differs
Max session	1 h (Hobby), 24 h (Pro) (source: E2B Pricing)	not published	Google Cloud Run: no figure
Persistence	state kept, pause/resume, memory kept, fork (source: E2B homepage)	state kept (source: docs.cloud.google.com/run/docs/code-execution)	differs
Self-host	Yes, Apache-2.0 (source: E2B runtime (GitHub))	not published	Google Cloud Run: no figure
Your own cloud (BYOC)	Yes (source: E2B homepage)	not published	Google Cloud Run: no figure
GPU	No (source: E2B Pricing)	not published	Google Cloud Run: no figure
SDKs	Python, JavaScript/TypeScript (source: E2B Pricing)	In-container sandbox CLI (create, exec, delete) (source: docs.cloud.google.com/run/docs/code-execution)	differs
SOC 2	Type II (source: E2B homepage)	not published	Google Cloud Run: no figure
Free tier	Hobby: $0 plan fee, one-time $100 usage credit, 10 concurrent sandboxes, 1-hour sessions. (source: E2B Pricing)	not published	Google Cloud Run: no figure

Prices are list prices for one hour of a 2 vCPU / 4 GiB sandbox: 2 × the vCPU rate + 4 × the memory rate. Each value links to the page it came from; not published means the vendor states no figure. How we compare.

Pick Google Cloud Run instead of E2B when

your stack already runs on that cloud: Google Cloud Run is a first-party service there, so identity, billing and networking stay in one place.

Stay on E2B when

you run model-written code you do not control and want a dedicated kernel per sandbox: E2B uses Firecracker microVMs, Google Cloud Run uses process sandbox.
pause has to keep running memory as well as files: E2B's pause saves both, and Google Cloud Run does not state memory state in our data.
you need a SOC 2 report: E2B states Type II, and Google Cloud Run states none in our data.
stability matters: Preview; subject to pre-GA terms.
you want managed cloud, your own cloud account and self-hosting from one vendor: E2B offers all three, with BYOC on its Enterprise plan.

All Google Cloud Run facts

Source per value

Isolation Isolation technology the vendor states for each sandbox.: process sandbox 1
Other isolation options Alternative runtimes the vendor offers besides the default (e.g. VM runtime, gVisor for GPU).: No parent environment variables, secrets or metadata-server access by default 1
Deployment Managed cloud service, self-hosted software, or both.: managed 1
Billing basis What the meter counts: wall-clock allocated resources, active CPU only, requests/plan quota, session-hours, or free software.: Not published
vCPU price $/vCPU-hr Published on-demand CPU rate normalised to USD per vCPU-hour (per-second rates multiplied by 3,600; per-core rates divided by vCPUs per core where the vendor defines it). Lowest public tier, default region. 0 means the vendor states no separate CPU charge.: Not published
Memory price $/GiB-hr Published memory rate normalised to USD per GiB-hour (GB treated as GiB where the vendor does not distinguish). 0 means the vendor states memory is free.: Not published
Sandbox from $/sandbox-hr Smallest published per-sandbox hourly price, where the vendor publishes one.: Not published
Paid plan from $/mo Cheapest paid platform plan fee (before usage).: Not published
Free tier A free plan, free monthly allowance or sign-up credit exists.: Not published
Free tier detail What the free tier or credit includes, as published.: Not published
Cold start ms Vendor-published create/boot time in milliseconds (a vendor claim, not our benchmark). Only filled when the vendor publishes a number; see startup_claim for percentile and conditions.: Not published
Resume time ms Vendor-published resume-from-pause/standby/snapshot time in milliseconds.: Not published
Startup claim The vendor's startup/resume wording with conditions, quoted or closely paraphrased.: Not published
Max session length Longest single sandbox session by plan, as published.: Not published
Persistence / snapshots Filesystem state can be kept between runs (snapshots, persistent disks, volumes).: Yes 1
Pause / resume A sandbox can be paused, suspended, hibernated or put in standby and resumed later.: Not published
Memory state kept Pause/hibernate preserves running memory state, not only the filesystem.: Not published
Fork / branch A running or snapshotted sandbox can be cloned into new sandboxes.: Not published
GPU GPU sandboxes are offered.: Not published
Self-host Can run on your own hardware or cluster (open source or licensed).: Not published
BYOC / VPC Vendor-managed deployment inside your own cloud account.: Not published
Open source Core sandbox runtime is published under an open-source licence.: Not published
Licence Open-source licence of the runtime, if any.: Not published
SDKs / languages Official SDK languages (or supported execution languages where noted).: In-container sandbox CLI (create, exec, delete) 1
Regions Published regions or region count.: Not published
Max vCPU per sandbox vCPU Largest published vCPU count per sandbox on any self-serve or enterprise plan.: Not published
Max memory per sandbox GiB Largest published memory per sandbox.: Not published
Concurrency Published concurrent sandbox limits by plan.: Not published
SOC 2 SOC 2 status as stated by the vendor.: Not published
HIPAA Vendor offers HIPAA-compliant usage/BAA (on any plan).: Not published
2 vCPU + 4 GiB per hour $/hr Hourly list price of one 2 vCPU / 4 GiB sandbox: 2 x the vCPU rate + 4 x the memory rate, from the two published rates. Left empty for self-hosted software and for vendors without both rates. Vendors that bill CPU only while busy (Vercel, Cloudflare, Upstash, Tensorlake, AWS AgentCore) cost less for idle agents than this shows.: Not published
Price vs E2B x E2B The 2 vCPU + 4 GiB hourly price divided by E2B's own ($0.1656 at $0.000014/vCPU-s and $0.0000045/GiB-s). Under 1 is cheaper than E2B.: Not published
Status Preview, experimental, beta, sunset or self-hosting caveats the vendor documents.: Preview; subject to pre-GA terms. 1

Sources

docs.cloud.google.com/run/docs/code-execution accessed 2026-11-11

Google Cloud Run in the E2B comparisons

E2B alternatives from AWS, Azure, Google Cloud, Alibaba and CloudflareWhich cloud providers sell a first-party E2B alternative? 8 listed.

Compare with other E2B alternatives

All 41

Agent Sandbox on GKE vs E2B no comparable hourly price, gVisor
AWS Lambda MicroVMs vs E2B no comparable hourly price, Firecracker microVM
Azure Container Apps Dynamic Sessions vs E2B no comparable hourly price, Hyper-V
Amazon Bedrock AgentCore Code Interpreter vs E2B $0.217/hr, 1.31x E2B, microVM
Google Agent Platform Code Execution vs E2B $0.206/hr, 1.24x E2B, gVisor

Get a quote from Google Cloud Run and similar alternatives

Tell us what you need once. We send it to matching alternatives and they reply to you directly.