Tool · server-side tagging
Server-side GTM cost calculator
Server-side GTM hosting is billed on the number of requests your container receives, and the three usual routes do not bill it the same way. Stape charges per container, so the bill scales with your number of sites. Addingwell charges on the aggregated volume of the account and sells extra containers as an add-on. Running it yourself on Google Cloud replaces a subscription with an infrastructure bill and your own time. Set your monthly requests and your number of sites below and the three costs are computed side by side, from prices read off each provider's own pricing page.
Your setup
One request = one hit received by your server-side container. Between 100k and 100M.
One site = one server-side container.
Informational: shows what our sources say about it. Does not change the totals.
Estimated cost
One row per route, each in the currency its provider publishes. Annual column = twelve months at the monthly rate; where a provider publishes its own yearly total, that total is quoted underneath.
| Route | Billing basis | Monthly | Per year |
|---|---|---|---|
| Stape | Per container | $83/moBusiness plan (5M requests) × 1 container(s), $83 each.Yearly total published by Stape: $1,000 per year. | $996/yr |
| Addingwell | Per account, add-on per container | €90/mo€90 plan, covering 1M requests per month. | €1,080/yr |
| Do it yourself, Google Cloud | Infrastructure bill | Not priced hereWe publish no monthly figure for a self-hosted container: the bill depends on your minimum instances, your outbound requests and your log retention. Price it on your own project rather than on our guess.New Google Cloud accounts start with $300 of credits over 90 days. | Not priced here |
No currency conversion is applied: Stape publishes in dollars, Addingwell in euros. Comparing the two is your call, at your own rate.
Method
A calculator is only worth what its method is worth. Here is every rule the numbers above follow.
Assumptions
- The requests figure is per site, per month. The aggregated volume shown under the sliders is what an account-level grid is billed on.
- Stape bills per container and one container is one site: each site takes the smallest plan that covers its own volume, then the bill is multiplied by the number of sites.
- Addingwell bills on the aggregated volume of the account, and extra containers are an add-on — so the plan is picked on the total, then €30 per additional container is added.
- Each route is shown in the currency its provider publishes. Nothing is converted.
- Stape's yearly totals are the ones printed on its own pricing page, not the monthly price multiplied by twelve and discounted.
- Above the largest published Addingwell plan, the excess is billed per 100k requests at the rate that plan publishes — €1.30 — so it is a number, not a range.
- The self-hosted route carries no figure. We have not measured a Cloud Run bill ourselves, and we would rather leave the cell empty than fill it with somebody's order of magnitude.
Not counted
- The engineering time to set up, migrate and maintain the container.
- What you send the requests to: GA4, the ads platforms, their own quotas.
- Committed or negotiated discounts, which no provider publishes.
Sources
Every figure was read off the page linked below, on the date shown.
- Stape — Pricing — checked 08/12/2026
- Addingwell — Pricing — checked 08/12/2026
- Google Cloud — Free Trial and Free Tier — checked 08/12/2026
Prices verified on 08/12/2026. Providers change their grids; check with the provider before you commit.
Read next
Before you price the hosting, price the tags
Paste a URL. OnTracks crawls the site, drafts the events that matter to your funnel, and checks them on the page.
Analyze my site