Stape vs Google Cloud (2026): Host Server-Side GTM Yourself or Pay Stape to Run It

Google Cloud runs your server-side Google Tag Manager container on infrastructure you set up and look after. Google estimates about $45 a month per server and recommends at least two, so roughly $90 a month before logging and domain costs, no matter how little traffic you have. Stape hosts the same container for you, free to 10,000 requests a month and $20 a month for 500,000. Stape is cheaper for most stores; self-hosting can cost less at very high traffic if someone on your team can run it.

Our guide to Stape alternatives covers tools that skip the GTM container entirely. For this Stape vs Google Cloud comparison, we checked Google's own server-side tagging docs, Google Cloud's Cloud Run pricing page and Stape's pricing and hosting pages on October 24, 2026. Upstack is our product, and it appears only in the last two sections.

Stape vs Google Cloud at a glance

Both options run the same thing: a server-side GTM container that receives browser events, usually GA4 hits, on a subdomain of your site and forwards them to Meta, Google Ads, TikTok and anything else with a server tag. Neither one builds those tags for you.

---

What self-hosting on Google Cloud involves

Google's Cloud Run setup guide for server-side tagging lays out the steps:

1. Accounts and roles. You need a Google Cloud account, a billing account, and the Project Creator and Billing Account User roles.
2. Two services. You provision a preview server, which powers GTM's preview mode, and a tagging server, which handles live traffic. Tag Manager can provision both automatically, or you can do it by hand in Google Cloud.
3. A custom domain. You map the deployment to a subdomain of your site, so the container sets first-party cookies.
4. The server URL in GTM. You add the tagging server's URL to the server container's settings.
5. Validation. You open preview mode, or check that the server's /healthy path returns "ok".

After launch, the work continues. Google recommends updating the tagging server at least for each major version release, when Tag Manager tells you to, by deploying a new revision with the stable image. If your site is global or you want redundancy, Google's guide adds a load balancer and tagging servers in more regions. And it suggests setting a billing alert "to avoid unexpected costs".

The older App Engine setup is on its way out: Google's guide tells anyone migrating to Cloud Run to disable the old App Engine application once it stops receiving traffic, to prevent unexpected charges.

---

What does Google Cloud cost for server-side GTM?

Google gives a working estimate rather than a price list. Per its setup guide:

• About $45 a month per server. Each server is a Cloud Run instance with 1 vCPU and 0.5 GB of memory, using the CPU-always-allocated pricing model.
• A minimum of two instances is recommended, to reduce the risk of losing data if a server goes down. That puts the floor at roughly $90 a month for the tagging server, whatever your traffic.
• Two to ten servers handle about 35 to 350 requests per second, though Google says performance varies with the number of tags and what they do. Cloud Run scales within the range you set, and the maximum-instances setting is your worst-case bill.

On Cloud Run's pricing page, instance-based billing in us-central1 is $0.000018 per vCPU-second and $0.000002 per GiB-second, with a monthly free tier of 240,000 vCPU-seconds and 450,000 GiB-seconds per billing account. Prices depend on the region, and committed-use discounts lower them if you run instances continuously. Because the tagging server keeps CPU allocated, you pay for instance time, not per request.

Three costs sit outside that $45 figure:

• Logging. By default, Cloud Run logs every request. Google warns that past roughly 1 million requests a month those logs "may incur significant logging charges" and recommends turning request logging off.
• Load balancing and multi-region. Running in several regions means a load balancer, billed separately under Google Cloud networking.
• The preview server. It's a second Cloud Run service. Google's estimate covers the tagging servers, so check the preview server in the pricing calculator Google links from the guide.

---

What does Stape cost?

Stape prices its server GTM hosting by requests, per its pricing page, checked October 24, 2026:

A request is every incoming hit to the container, including script loads such as gtm.js and gtag.js; our Stape pricing guide goes through how requests add up. Where your data sits depends on the hosting you pick: per Stape's hosting page, EU hosting runs on Scaleway servers in Europe and Global hosting runs on Google Cloud. So "Stape vs Google Cloud" is sometimes Stape on Google Cloud, managed for you.

---

Stape vs Google Cloud cost at three traffic levels

These figures compare hosting only, at list price, using Google's own per-server estimate. They leave out Google's logging, load balancer and preview-server costs, and the time you spend running the server.

Averages hide peaks. A sale or a campaign launch can push requests per second far above the monthly average, which is when Cloud Run adds instances and Stape's request count climbs. Still, the pattern holds: below a few million requests a month, Stape costs less than Google's recommended minimum. At 20 million and above, Google Cloud's compute bill can come in under Stape's, as long as you count the hours someone spends maintaining it.

The costs that don't show up on either invoice

On Google Cloud, every operational job is yours:

• Updates. Deploying new tagging server versions when Tag Manager asks.
• Monitoring. Setting billing alerts and checking that the server stays healthy. Google's guide has no built-in alerting for tag failures.
• Logging. Turning off request logging before it becomes a line item.
• Domains and regions. Mapping custom domains, and adding a load balancer if you go multi-region.
• Incidents. Working out why events stopped when something breaks at 2 a.m.

On Stape, the server is handled, but the tags are still yours. Stape's Care service does setup or an audit from $1,100, then ongoing monitoring from $99 a month on a Pro container, per stape.io/care, on top of hosting. Our Stape review covers what customers say about support and request counts.

With both, the larger cost is usually the person who builds and maintains the web and server containers, not the hosting line.

---

Should you self-host or pay Stape?

Moving between them is mostly a DNS and settings change, because both run a server-side GTM container. Stape publishes a migration guide for moving from Google Cloud or another host.

---

When neither is the right fit

Both options assume someone on your team will build and maintain GTM containers. Some brands compare them only because they want server-side events in Meta and Google, and would rather not run a container at all. Our Tracklution vs Stape comparison covers a managed tool that skips the container, and our TAGGRS vs Stape comparison covers another sGTM host.

Upstack Signal, our product, takes the container out of the picture. Upstack Signal collects events first-party and sends them server-side to Meta, Google Ads, TikTok, Pinterest, Snapchat and Klaviyo, with no GTM containers to build or host. Each visitor is resolved with deterministic and probabilistic matching against our identity graph of 750M+ devices and 150M+ customers, and the Upstack ID persists for the life of the customer. It's priced per order and month to month: $149 a month for up to 1,000 orders, $399 to 10,000 and $1,199 to 30,000, with a 21-day free trial and setup in under 20 minutes. It's built for Shopify and DTC brands, it doesn't give you a container for custom tags, and it costs more than raw hosting on either Stape or Google Cloud.

---

Frequently asked questions

Is Stape cheaper than Google Cloud for server-side GTM?

Usually, yes. Stape is free to 10,000 requests a month and $20 a month billed monthly for 500,000, while Google estimates about $45 a month per Cloud Run server and recommends at least two. At very high traffic, around 20 million requests a month and up, Google Cloud's compute can cost less than Stape's Enterprise plan, before you count logging, a load balancer and maintenance time.

How much does server-side GTM cost on Google Cloud?

Google's setup guide estimates about $45 a month for each Cloud Run server with 1 vCPU and 0.5 GB of memory, and recommends a minimum of two, so about $90 a month to start. Request logging, a load balancer for multiple regions and the preview server add to that, and Cloud Run prices vary by region.

Does Stape run on Google Cloud?

Stape's Global hosting runs on Google Cloud. Its EU hosting runs on Scaleway servers in Europe, which Stape says it created to support GDPR-compliant use of Google Analytics. Either way, Stape manages the servers for you.

Can I move from Google Cloud to Stape?

Yes. Both run a server-side GTM container, and Stape publishes a migration guide for moving from Google Cloud or another hosting provider. The work is mostly creating the container on Stape, pointing your tracking subdomain at it and updating the server URL in GTM.

Do I still need GTM skills if I use Stape?

Yes. Stape hosts the server container, but you or an agency still build and maintain the web and server tags, triggers and variables. Stape's Setup Wizard and templates help, and its Care service does setup from $1,100 if you'd rather pay.

Should I still use App Engine for server-side tagging?

Google's current guide uses Cloud Run. If you set up an App Engine deployment earlier and it no longer receives traffic, Google recommends disabling the App Engine application to prevent unexpected billing charges.

---

Compare Stape with Upstack

If you're choosing between self-hosting and Stape mainly to get server-side events into Meta and Google, our Upstack vs Stape comparison goes row by row through what changes when tracking needs no container, is priced per order, and resolves identity before events leave.