Two years ago, picking a host for your server-side GTM meant picking Stape and moving on. That is no longer true. In April 2025, Didomi closed an $83M deal with private equity firm Marlin Equity Partners to acquire Addingwell, one of the reference sGTM hosts, and fold it into a CMP plus server-side tagging bundle. Three months later, that same Didomi acquired Sourcepoint. In other words: the sGTM hosting market reshuffled under your feet, and the “Stape vs Addingwell” question no longer resolves the way it used to.
This article compares the four real options on the market in 2026, Stape, Addingwell by Didomi, Taggrs and self-hosted Cloud Run, across the five criteria that actually decide it: real cost, GDPR compliance, setup simplicity, Consent Mode v2 integration and support. The goal is simple: let you make the call in under twenty minutes, without installing every platform to form an opinion.
If you haven’t made the jump yet, start with the guide to migrating to server-side GTM, then come back here to choose where to host. And if you are still weighing server-side GTM against Google’s native approach, the Google Tag Gateway vs Server-Side GTM comparison will place you on the map.
The comparison at a glance
Let’s open with the table, because it is probably what you came for. Prices are the entry tiers observed in summer 2026, options excluded.
| Criterion | Stape | Addingwell (Didomi) | Taggrs | Cloud Run (DIY) |
|---|---|---|---|---|
| Entry price | ~$20/mo | ~€10/mo | ~€10/mo | ~€5 to €15/mo compute |
| Billing model | Request tiers | Request tiers | Request tiers | Actual GCP usage |
| Hosting | Multi-region (incl. EU) | EU (sovereignty) | EU | GCP region of choice |
| Setup | Guided wizard, very fast | Guided wizard, very fast | Guided wizard | Manual (Terraform or console) |
| Consent Mode v2 | Compatible | Native, tied to the CMP | Compatible | Wire it yourself |
| Support | International, English | French, responsive | French, responsive | None (you are the support) |
| Best fit | Multi-client agency | EU e-commerce and teams | Freelancer, small budget | In-house technical team |
That table covers 80% of decisions. The rest of the article explains the “why” behind each row, because the sticker price never tells the whole story. I broke down that real-cost trap in how much server-side GTM really costs: worth reading if your request volume is high, because that is where the tiers hurt.
Stape: the reference that now has to defend itself
Stape is still the largest independent player on the market, and it shows. The platform is mature, the documentation is abundant, and the ecosystem of power-ups (custom loader, cookie keeper, GEO headers, ad-blocker proxy) has no real equivalent. If you want to push server-side to its technical limits, Stape is where you will find the most ready-made tooling.
The flip side is price. Stape starts higher than its European rivals and bills in dollars, with request tiers that climb quickly once a site carries serious paid traffic. Support is solid but English-only, on an international timezone. And on data sovereignty, Stape does offer European regions, yet it remains a company whose center of gravity is not the EU, which weighs in some RFPs.
Best fit: the agency running multiple clients, wanting a robust platform with advanced features, and for whom the price gap dissolves into the value billed to the client.
Addingwell by Didomi: the privacy-bundle bet
This is the player that changed the most. Before the acquisition, Addingwell was the French alternative to Stape: EU hosting, a French interface, responsive support, aggressive pricing. All of that still holds. What changed is the context: Addingwell is now part of Didomi, one of Europe’s CMP (consent management) leaders. The product now sells as one brick of a full privacy stack.
In practice, the appeal is obvious if you already use, or plan to use, the Didomi CMP. Pairing CMP with sGTM simplifies wiring up Consent Mode v2 in GA4 and Google Ads: the consent signal and the server-side tagging come from the same vendor, which cuts friction points and mapping errors. For a team still treating Consent Mode as a chore, that is a real argument.
The risk fits in one word: lock-in. You are no longer just choosing a host, you are stepping into the orbit of a group in the middle of consolidation (Sourcepoint bought right after). If Didomi’s roadmap suits you, that is a coherence advantage. If you want to keep your CMP and hosting bricks independent, it is a point to watch.
Best fit: e-commerce and marketing teams based in the EU, sensitive to data sovereignty, wanting a consent plus tagging integration without juggling two vendors.
Taggrs: the underdog playing price and simplicity
Taggrs belongs to the new wave of hosts (alongside Tracklution and ServerTrack.io) chipping away at the market from below. The positioning is clear: a very low entry price, a guided setup accessible even to non-technical users, EU hosting, and support that answers fast. For a freelancer or a small shop migrating their first server-side container, it is often the best simplicity-to-price ratio.
What Taggrs lacks is Stape’s ecosystem depth and Addingwell’s privacy integration. You get the essential features (proxy, first-party cookie handling, presets for the main platforms), but not the long tail of advanced add-ons. For most sites, that is not a problem: those advanced features only serve a minority of cases.
Best fit: freelancer, consultant early in an engagement, or SMB on a tight budget wanting clean, functional server-side without overpaying.
Cloud Run: the DIY that stays unbeatable on raw cost
Self-hosting your sGTM container on Google Cloud Run is the cheapest option on paper, by far. You pay Google for actual compute, often a few euros a month for moderate traffic. You choose your region, you control everything, and no host margin gets tacked on.
The “on paper” matters. The hidden cost of DIY is your time. You have to provision the infrastructure, manage the domain and SSL, watch the scaling, update the container image, and above all be the support when something breaks on a Friday night. There is no “fix it” button, there is you. Consent Mode v2 gets wired by hand, no wizard. For a team that already has GCP skills in-house, all of this is trivial and the cost savings are clear. For everyone else, a managed bill from Stape or Taggrs is often cheaper than the hours spent playing sysadmin.
Best fit: in-house technical team comfortable with GCP, high request volumes where managed tiers turn punitive, and a requirement for full control over the infrastructure.
Which host for which profile?
Let’s boil it down to four concrete situations, because “the best host” does not exist in the abstract, only the best one for you.
The freelancer or consultant getting started: Taggrs. Low price, fast setup, responsive support, zero over-engineering. You are live in an afternoon.
The multi-client agency: Stape. The robustness, the power-ups and the documentation earn their price when you industrialize server-side across many accounts, and the price gap gets billed onward.
The EU e-commerce or marketing team: Addingwell by Didomi. If consent and data sovereignty are sensitive topics, the CMP plus sGTM bundle makes life easier and ticks the GDPR boxes with no extra effort.
The large enterprise with a technical team: Cloud Run. You have the GCP skills, you want control and the best cost at volume, self-hosting is built for you.
The verdict
In 2026, there is no default choice anymore. If I had to give one clear recommendation, here it is: start with Taggrs if you are new and budget matters, step up to Stape when your needs turn advanced or multi-client, take Addingwell seriously if your privacy stack already lives at Didomi or sovereignty is a buying criterion, and reserve Cloud Run for teams that know what they are doing on GCP.
The real shift this year is that sGTM hosting is no longer a purely technical decision. With the consolidation Didomi is leading, choosing a host increasingly means choosing a side in the privacy stack. Frame the question that way: do you want a vendor that does one thing very well, or a partner that owns the whole pipe from consent to activation? Answer that, and your host picks itself.