Menu

What does server-side GTM hosting cost?

Google Cloud Run next to the Stape plan that fits your traffic.

Don't know your volume?

Stape adds 30% to GA4 events.

Advanced settings

Google Cloud Run

$94.64/mo

2 instances

Stape

$20.00/mo

Pro · up to 500,000 req/mo

Switch point: 1,666,667 req/mo. On Google's setup it moves from 416,667 to 4,166,667, with 1 or 2 instances and monthly or annual billing.

See the math
Compute
$99.86
Requests
$0.00
Free tier
-$5.22
Cloud Logging
$0.00
Data out
$0.00
Load balancer
$0.00
Create a Stape account Partner code MRPV20 at checkout

Rather have it set up for you? Tell us about your setup

List prices read on 16 Nov 2026, not an invoice. ATA is a Stape partner and earns a commission on signups through this link; the math is the same either way.

Quick answers

How much does Stape cost?
Stape's paid plans start at US$20 a month for 500,000 requests (Pro). The others: US$50 for 2 million (Pro+), US$100 for 5 million (Business), US$150 for 10 million (Business+), US$200 for 20 million (Enterprise) and US$300 for 50 million (Enterprise+). Above that, Stape quotes a custom price. Prices read on 16 Nov 2026.
How much does server-side GTM cost on Google Cloud Run?
Google's recommended setup, two always-on instances with 1 vCPU and 0.5 GB each, comes to about US$95 a month in a US region, or US$115 in São Paulo, before much traffic. Logging and data transfer grow with volume.
When is Cloud Run cheaper than Stape?
On hosting charges alone, with Google's setup, Cloud Run is cheaper than Stape above about 1.7 million requests a month at US prices, or 4.2 million at São Paulo prices. That leaves out the time it takes to run Cloud Run yourself.
What the bill doesn't show
  • Custom Loader, Cookie Keeper and outgoing-request logs come with Stape plans. On Cloud Run, you build them.
  • Stape pauses Pro and Pro+ at 110% of the limit. Business and up get 30 days of grace, once.
  • On Cloud Run, you restart servers to pick up Google's new image and run the preview server yourself.
  • Cloud Run won't alert you when instances run short at a peak. You set that up.
How we calculate
  • Google's guide setup: 1 vCPU, 0.5 GiB, 2 always-on instances, about 17.5 req/s each (low end of "2-10 servers will handle 35-350 requests per second").
  • Monthly average traffic, split across regions. Spiky traffic costs more on Cloud Run.
  • Cloud Run free tier once per billing account; 50 GiB of free logs per project.
  • Several containers: each is its own Cloud Run service and its own Stape plan.
  • Stape plan: the smallest that covers your requests plus headroom. Stape's own picker moves up at 70%. More than one region starts at Business (multi-zone).
  • Not counted: preview server, extra logs, committed-use discounts. We don't estimate upkeep hours.
  • Log and data sizes are our estimates; change them under Advanced settings.

Sources (16 Nov 2026): Cloud Run · Cloud Logging · Network · Load balancing · Stape · Stape pause rules · Google's guide