Stape Alternatives I'd Use for Server-Side GTM in 2026

Stape is where most people start with server-side GTM, and it deserves that spot. The free plan is real, the docs are good, and you can have a tagging server running without ever opening Google Cloud.

People usually start looking elsewhere when the bill jumps. Stape's Pro plan is $20 a month for 500,000 requests, and the next plan up is $100 for 5 million, with nothing in between. Others want logs that last longer than the 3 days Pro keeps, or a server closer to their shoppers.

I'm Md Mahedi Hasan. I've been writing code since 2014, ran the tracking for Uddokta Ecommerce's stores for more than four years, and built PixelFly, which is why it's first on this list. I've tried to be fair to everyone else. Every price below comes from the vendor's own pricing page (links at the end), and every option, mine included, gets its weak spots listed.

All of these run the same Google image

This is the part that makes switching less scary than it sounds. Stape, PixelFly, TAGGRS, Addingwell and Google Cloud all run Google's official server-side tagging image. Your clients, tags, triggers and variables come with you unchanged. You copy the container config, point your tracking subdomain at the new server, and the tags behave as before.

What changes is everything around the image: what you pay at your traffic, where the server sits, which extras come included, and who gets the call when it stops answering.

How many requests will you really send?

Every host here prices by volume, so it helps to know your number before comparing plans. I pulled one ordinary day, 21 October 2026, from PixelFly's servers (513 server containers that day), and two things stood out.

First, count events, not visitors. Stores sent about two and a half events for every page view: 620,345 page views and 1.54 million events in total. GA4 adds engagement, scroll and product-view events on top of every page view, and checkout steps add more.

Second, not every request is an event. About 36% of the 2.22 million requests that reached those containers were GTM's own background traffic, such as the calls that set first-party cookies, and script loads. PixelFly counts only the events. TAGGRS's pricing page defines a request as an event on your site. Stape's and Addingwell's pages say "requests" without spelling out what's included, so ask them before you compare.

Quick comparison

These are monthly-billing prices, checked on 22 October 2026. Paying yearly is cheaper on Stape, PixelFly and TAGGRS. TAGGRS and Addingwell price in euros (TAGGRS also lists $26 and $68 for the two plans above).

1. PixelFly

This one is mine, so read it with that in mind. PixelFly launched in December 2025. We're a team of eight in Jashore, Bangladesh, and we run Google's image on our own Kubernetes clusters in Bangladesh, the USA (East) and the UK (London).

Most of the price difference with Stape comes down to how the plans are spaced. Stape jumps from 500K requests at $20 to 5M at $100. We have a 2M plan at $30, and 5M is $50.

I also didn't want the useful parts to be upsells. Every plan, including the free one, gets the custom loader (so ad blockers are less likely to stop gtm.js), cookie keeper, bot filtering and EMQ Enricher, which restores missing customer match keys on Meta events. On Stape, cookie keeper, bot detection and the Enricher start on the $20 plan. Event logs are kept for 30 days on Free and up to 365 days on Enterprise; Stape keeps 3 days on Pro and 10 on Business.

Two features came out of problems our customers ran into. Failed Event Recovery keeps any hit your server container couldn't take (a 502, 503, 521 or 522, or no connection at all) and sends it again for up to 24 hours. The morning we switched it on, it made its first two rescues within half an hour. COD order protection holds a cash-on-delivery purchase back from Meta until the order is confirmed, which matters when most of your orders are COD.

If you don't want server GTM at all, PixelFly can also send events straight to Meta, GA4, TikTok, LinkedIn, Snapchat and Google Ads.

Where we're behind: we have three locations, so if your shoppers are mostly in Australia or Brazil, pick a host with a server near them. There's no multi-zone hosting yet. Each container runs in the one location you choose, while Stape spreads containers across zones from its Business plan. We don't list a plan above 5 million events (Stape lists 20 million for $200), we don't offer enterprise paperwork like SSO or HIPAA agreements, and our power-up catalogue is far smaller than Stape's. And when you reach your monthly limit, tracking pauses until the month resets unless you upgrade, so watch your usage.

It's free for 15,000 events a month. Starter is $15 for 500K ($13 billed yearly, or ৳1,200 in Bangladesh), Pro is $30 for 2M ($24 yearly) and Enterprise is $50 for 5M ($42 yearly). I'd point stores and agencies between 500K and 5M requests a month here, especially ones selling in South Asia, the US or the UK. For Bangladesh specifics like BDIX servers and bKash or Nagad payment, see our Bangladesh guide.

2. Google Cloud Run

If you'd rather not depend on any host, you can run the image in your own Google Cloud project. Google's server-side tagging guide walks you through it, and you get full control, your own bill and any Google region.

It costs more than most people expect. Google's guide prices each server (1 vCPU, 0.5 GB of memory, CPU always on) at about $45 a month and recommends running at least two, to reduce the risk of losing data. So you start at around $90 a month, plus a small preview server for GTM's Preview mode. Google says two to ten servers handle roughly 35 to 350 requests per second, depending on your tags.

Then there's the upkeep. You update the image, map the custom domain, watch the error logs and keep an eye on the logging bill. Cookie keepers, custom loaders and readable event logs don't exist here unless you build them.

It makes sense for a company with a developer who knows Google Cloud, or with contracts that require all data to stay in its own cloud account. For a store that just wants tracking to work, it costs about three times our 2M plan, and the maintenance is yours.

3. TAGGRS

TAGGRS is a Dutch company from Heerenveen. It runs on UpCloud's European infrastructure instead of Google Cloud, with servers in several locations.

Its approach is a lot like ours. Most features are on every plan, Free included: a custom subdomain, Cookie Recovery (which keeps cookies alive past the 7 days Safari allows) and Data Enrichment, with multi-domain tracking from Pro. Its plans also fill the gap in Stape's pricing. Basic is €25 a month for 750K requests (€22 billed yearly), Pro is €65 for 3M (€57 yearly) and Ultimate is €145 for 10M (€127 yearly).

Read the limit rule before you sign up. TAGGRS says that once you pass your plan's limit, data can no longer be sent to the platforms unless you upgrade. It offers automatic upgrades, and I'd turn them on.

I'd suggest it to European stores and agencies that want a European host outside Google Cloud with simple pricing. If you need phone support, look elsewhere; TAGGRS offers live chat and a help desk, with replies within 24 hours.

4. Addingwell

Addingwell comes from Lille, France, and since April 2025 it has belonged to Didomi, the consent-management company. If you already collect consent with Didomi, getting server-side tagging from the same vendor is the main reason to look here.

Its free plan is the biggest on this list, 100,000 requests a month, offered instead of a trial. Paid plans start at €90 for 1M requests, then €120 for 5M and €210 for 12M. Past your plan you pay per extra 100,000 requests, €2.30 on the 1M plan and less on bigger ones. Extras add up: another container is €30 a month, another domain €10 and another region €20. Support is by email, live chat and phone, and the dashboard is built around debugging tags.

For a small store it's hard to justify. Below a million requests, €90 a month buys a lot less than the $15 to €25 plans elsewhere.

5. Google's image on your own server

The image is public (gcr.io/cloud-tagging-10302018/gtm-cloud-image:stable), and Google documents how to run it on any server: a VPS, Docker on your own hardware, or Kubernetes. It's how we run PixelFly, so I can tell you it works, and that the rules in Google's manual setup guide matter more than they look:

• Run exactly one preview server, and don't autoscale it.
• Give each server no more than 1 vCPU. Extra CPUs go unused and make autoscaling worse.
• Health-check /healthy, but give a new container time to start first. Some of ours have taken more than three minutes, and a check that gives up too early just restarts the container in a loop. We learned that one the hard way.
• Update the image at least on every major release, and restart servers now and then so they pick up the latest code.

The bill is just the server. Everything else is yours: TLS certificates, the tracking subdomain, uptime monitoring, updates, and being the one who gets the call when it goes down in the middle of a sale. It suits developers and agencies who already run servers, and nobody else.

When I'd stay on Stape

Switching isn't always worth it. I'd stay if you need more than 5 million requests a month on a listed plan (Stape lists 20 million for $200), or enterprise terms like SSO, a HIPAA agreement, a dedicated IP or a private cluster. The same goes if you need multi-zone hosting or a region nobody else has, or if you depend on Stape-only power-ups; check each one before you move. And if everything works and the bill doesn't bother you, moving costs time you could spend on something else.

If you don't need server GTM at all

Plenty of stores only want server events in Meta, GA4 or TikTok and never wanted to manage a server container. For them, sGTM hosting is overkill. Stape sells Dedicated Gateways for this from $8 a month per platform, and PixelFly's Proxy Server covers Meta, GA4, TikTok, LinkedIn, Snapchat and Google Ads on every plan, including Free.

Moving off Stape without losing data

1. Set up the server container on the new host with the same container config. It's the same Google image, so nothing in your tags changes.
2. Write down the Stape features you use, like Cookie Keeper, Custom Loader and power-ups, and set up the equivalents on the new host. If your custom loader path changes, update the GTM snippet on your site too.
3. Test the new server in GTM Preview before you switch anything.
4. Point your tracking subdomain's DNS at the new host. The cookies your server container set belong to your own domain, so returning shoppers keep them.
5. Leave Stape running for a few days while DNS updates, and check purchases in Meta Events Manager and GA4 against your real orders before you cancel.

Which one I'd pick

• For a small or mid-size store that just wants it handled, PixelFly, or TAGGRS if a European host matters to you.
• For a store selling in Bangladesh or South Asia, PixelFly, for the BDIX servers, taka pricing and COD protection.
• For an EU brand already on Didomi, or a team that needs phone support, Addingwell.
• For a company with an in-house developer and data that has to stay in its own cloud, Google Cloud Run.
• For the smallest possible bill, if you don't mind being on call, your own server.
• Above 20 million requests a month, or with enterprise contracts, stay on Stape.

Prices change, and I'll update this page when they do. Everything above was checked on 22 October 2026. If you spot something out of date, leave a comment and I'll fix it.

Sources

• Stape: pricing
• PixelFly: pricing and PixelFly vs Stape
• PixelFly: what happens to your events when server GTM goes down (the first Failed Event Recovery rescues)
• Google: Cloud Run setup guide for server-side tagging
• Google: manual setup guide (your own server)
• TAGGRS: prices
• Addingwell: pricing
• Didomi: Didomi acquires Addingwell