stape.io is our default entry point into server-side tagging. Managed hosting, EU region, live in days. No GCP project of your own, no DevOps burden.
What is stape.io?
stape.io hosts your server-side GTM container as a managed service. Instead of standing up your own tagging server in Google Cloud Run or on Hetzner, the container runs at stape, with a first-party subdomain, SSL, and monitoring. The container stays standard GTM. Meaning: no lock-in, and a later migration is always on the table.
When stape.io fits, and when it doesn't
A fit when:
- you need sGTM in production fast, without your own GCP setup
- EU hosting with a DPA is mandatory
- your team lacks the DevOps capacity to run a container
- request volume is predictable and fits the plan tiers
Less so when:
- volume is high enough that a dedicated GCP instance is cheaper
- strict sovereignty requirements call for your own container
- your stack already lives entirely in GCP
stape.io vs. your own infrastructure
| Criterion | stape.io | Own GCP / Hetzner |
|---|---|---|
| Go-live | days | weeks |
| Ops effort | low, managed | ongoing ownership |
| EU region + DPA | included | set up per provider |
| Cost at high volume | rises with tiers | often cheaper per request |
| Data sovereignty | good, vendor-hosted | maximum, your control |
For roughly 95 percent of setups we start with stape and keep the migration path open. When volume or sovereignty demand it, we move to your own infrastructure.
What Datascale builds with stape.io
We deliver the blueprint and the quality-assured implementation:
- Measurement Blueprint as the binding foundation
- container setup including the first-party subdomain
- Consent Mode v2 mapping across web and server containers
- PII-stripping rules before every send
- routing to GA4, Google Ads, Meta CAPI, and BigQuery
- monitoring, alerts, rollback, and full handover documentation
The full picture of the server-side setup lives in Measurement & Privacy Engineering. The Tracking Check assesses your current tracking first.
