Managed providers host the GTM Server-Side infrastructure for you. You configure your container in GTM as normal, point your tracking subdomain at the managed endpoint, and the provider handles everything underneath: container updates, scaling, SSL, monitoring, compliance certifications, and the ops overhead that self-hosting requires.
The tradeoff is infrastructure control. You cannot configure the underlying container runtime, choose your instance type, or tune the exact region placement. You’re renting the outcome, not the infrastructure.
For teams without dedicated DevOps capacity, this is frequently the right tradeoff. The managed providers in this market handle the production configuration decisions that catch self-hosted Cloud Run deployments — cold start protection, CPU allocation, request logging costs — without requiring you to figure them out.
Stape
Stape is the market leader in managed GTM Server-Side hosting, and in many configurations it’s cheaper than self-hosting on Cloud Run.
The pricing model distinction matters: Stape counts only incoming requests to your server container, not the outgoing forwards to GA4, Meta, Google Ads, and other vendor endpoints. For a typical setup that forwards each incoming hit to 3-4 endpoints, that’s a significant difference — self-hosted Cloud Run billing is agnostic to whether a request generates one outbound call or five.
| Plan | Monthly cost | Requests included |
|---|---|---|
| Free | $0 | 10K |
| Pro | $20 | 500K |
| Business | $40+ | 2M+ |
| Enterprise | Custom | Custom |
Stape’s Pro plan at $20/month covers most small-to-medium sites. The Business plan’s 2M+ request ceiling handles high-traffic sites that would cost $90-270/month to run on Cloud Run at equivalent scale.
Beyond hosting, Stape includes features you’d otherwise build or buy separately:
Cookie Keeper — Stape’s solution to the Safari ITP bypass problem. Rather than solving the IP address mismatch that Safari 16.4 introduced, Cookie Keeper regularly refreshes cookies before they hit the ITP cap. Extends cookie lifetimes to 90 days or 13 months without requiring reverse proxy configuration. This is included in Stape plans.
Custom Loader — Renames the GTM script path to resist ad blocker detection. Ad blockers that pattern-match on known GTM URLs can’t match on a custom path. On ad-blocker-heavy audiences, this meaningfully improves tracking coverage.
Global CDN — Multi-region routing included, with no load balancer configuration required. Users route to the nearest Stape point of presence. Self-hosting the equivalent on Cloud Run requires an External Application Load Balancer adding $18+/month.
Monitoring dashboard — Request volume, error rates, and tag-level performance. Self-hosted deployments need to build this from Cloud Monitoring or equivalent.
Compliance certifications — SOC2, HIPAA, and ISO 27001. Organizations in regulated industries that need vendor compliance certifications would otherwise need to manage this documentation themselves for self-hosted infrastructure.
For smaller teams, Stape’s Pro plan at $20/month is often less than the logging costs alone on a naively configured Cloud Run deployment. The included features (Cookie Keeper, Custom Loader, global CDN) would require separate engineering effort to replicate on self-hosted infrastructure.
Addingwell
Addingwell positions as the premium managed option, with a starting price around €90/month. It was recently acquired by Didomi, a consent management platform.
What Addingwell includes that Stape’s lower tiers don’t:
- 99.99% uptime SLA — a contractual guarantee that matters for enterprise procurement
- Real-time tag health monitoring — per-tag performance metrics with alerting
- EU-first data residency — infrastructure defaults to European regions
The Didomi acquisition is worth noting for organizations that want their consent management and server-side tagging hosted under one vendor. In theory, tight integration between the CMP and the server container simplifies consent signal propagation. Whether that integration delivers meaningful practical advantage beyond co-billing is unclear as of early 2026.
At €90+/month, Addingwell is justified for:
- Organizations that need a signed SLA for procurement or compliance purposes
- EU-based organizations with strict data residency requirements
- Teams that want real-time tag monitoring without building their own observability stack
For teams that don’t need the SLA or premium support, Stape’s Business plan covers similar ground at a lower price.
TAGGRS
TAGGRS starts at €19/month with a focus on the European market. ISO 27001 certified with EU data residency, it’s a cost-effective option for EU-based organizations that need compliance certifications without paying Addingwell’s premium.
Less market presence than Stape, fewer published case studies, but the core offering — managed sGTM hosting with European data handling — is solid. Worth evaluating for EU-based teams where data residency is a firm requirement and Stape’s US-origin infrastructure creates compliance friction.
Cloudflare Zaraz: A Different Architecture
Zaraz is not GTM Server-Side. This distinction matters for evaluating it correctly.
Where GTM Server-Side runs the Google tagging server Docker image as a container receiving forwarded requests from the web container, Zaraz is Cloudflare’s own tag management system that runs directly at Cloudflare’s CDN edge. Your tags execute at the nearest Cloudflare point of presence when a user’s request passes through Cloudflare’s network — before it even reaches your origin server.
This architectural difference has meaningful implications:
What Zaraz does better than sGTM:
- Near-zero latency impact on page load (no separate HTTP request to a tagging server)
- Free coverage for up to 1 million events monthly
- Zero infrastructure to manage at all — if you’re on Cloudflare, it’s already there
- True edge execution without a centralized container
What Zaraz doesn’t provide:
- GTM ecosystem compatibility — the Community Template Gallery, existing container configurations, and GTM-specific workflows don’t transfer
- Container preview and debugging tools from GTM
- Support for vendors without a native Zaraz integration
Zaraz is worth evaluating if your primary goal is getting tracking off the main thread to improve page performance and you’re not already committed to GTM’s ecosystem. If you have an existing GTM setup with custom templates, established workflows, and team familiarity with the GTM interface, Zaraz is not a drop-in replacement — it’s a platform migration.
Choosing a Managed Provider
| Factor | Stape | Addingwell | TAGGRS | Zaraz |
|---|---|---|---|---|
| Starting price | $0 (Free) / $20 (Pro) | €90+ | €19 | Free (up to 1M events) |
| GTM compatible | Yes | Yes | Yes | No |
| Global CDN | Yes | Yes | EU focus | Yes (edge native) |
| EU data residency | Optional | Default | Default | Configurable |
| Compliance certs | SOC2, HIPAA, ISO 27001 | Enterprise | ISO 27001 | SOC2 |
| Cookie Keeper equivalent | Yes (included) | Yes | No | N/A |
For most organizations without specialized compliance requirements or budget constraints above ~$40/month: Stape’s Pro plan is the starting point.
For EU organizations with data residency requirements and limited budget: TAGGRS.
For enterprise procurement that requires an SLA: Addingwell.
For organizations not committed to GTM wanting edge-native tag execution: Zaraz.
The managed provider decision is also reversible. All providers use the same underlying GTM container configuration. Migrating between Stape and Addingwell — or from Stape to self-hosted Cloud Run — means updating DNS records and environment variables, not rebuilding your container configuration.