What you actually pay for GCP vs DataNostro
Cloud Run pricing is transparent but variable — on top of vCPU + RAM you accumulate egress, logging, IP, and ops time. DataNostro is a fixed CZK amount.
≈ $95 USD/month
- vCPU (always-on)$62.21
- RAM (512 MB)$3.24
- Requesty (5 M)$2.0
- Egress (~10 GiB)$0.73
- Cloud Logging$0.0
- Static IP$1.46
- Ops/maintenance overhead$25.0
More realistic tends to be +20–40% because min-instances=1 leaves the CPU idle 95% of the day, but it's still billed.
≈ $73 USD/month · ISDOC invoicing
- vCPU + RAMincluded
- Requesty (5 M)included
- Egressnot charged
- Logy + auditincluded
- SSL + domainincluded
- Updates + monitoringincluded
- Ops time0 minutes/month
A fixed amount. No egress shock, no regional billing puzzle.
Why we can do it for CZK 1,690 when GCP charges CZK 2,600
We're not cheap because we cut corners on performance. We're cheap because we aren't burdened by the same fixed costs as GCP.
Bare-metal in the EU, not a hyperscaler markup
A Hetzner Tier III data center in Germany, dedicated CPU. GCP charges ~3× for the same performance because it bakes managed Kubernetes, multi-region replication, and BigQuery integration into the price — features you don't need for an sGTM proxy.
Shared infrastructure across tenants
One Hetzner box serves 200+ tenants (the sGTM container runs in Docker with vCPU caps + memory limits). On Cloud Run you pay for idle CPU 24/7 — min-instances=1 is the default. We multiplex it.
No egress, no logging fees
Hetzner includes 20 TB of outbound traffic. GCP's Cloud Logging charges $0.50/GB beyond 50 GB — for a busy store during Black Friday that's +CZK 500. We write logs to disk + 90-day retention, free.
What it means for you
The same open-source sGTM Docker image (gcr.io/cloud-tagging-10302018/gtm-cloud-image) as on GCP. An identical runtime. The lower price is a difference in infrastructure cost, not in the quality of what your GTM workspace does.
What exactly you gain and what you lose
You gain
- Fixed CZK invoicing — no monthly puzzle of "how much did it cost us this year".
- EU-only data residency — an EU Tier III data center (Germany). No US-parent puzzle for corporate clients.
- Free egress — no traffic-spike billing shock.
- Auto SSL + auto Container Config rollouts — no terraform/IAM lock-in.
- Sklik + Heureka native integrations — critical for the CZ market, on GCP you have to write them yourself.
- Czech support — a response during EU business hours, not through a Google Premium Support contract.
- ISDOC invoicing — standard for accountants in CZ/SK, GCP invoices in USD without ISDOC.
What you lose (honestly)
- Multi-region failover — DataNostro runs in one EU location; GCP Cloud Run can do multi-region. A non-issue for 99.9% of CZ/EU stores, but worth mentioning.
- Custom autoscaling rules — we scale automatically, you can't set "keep 10 instances on Black Friday". If you need enterprise scale with your own rules, we have a dedicated tier.
- BigQuery integration inside the Cloud Console — GCP can do a direct BigQuery export with one click. With us, export is via the API or a CSV dump from the dashboard.
- VPC peering / Cloud Armor / IAP — Google Cloud enterprise security features, which we replace with a cloud-level firewall + nginx rate-limiting.
If you need any of this, write to us — we'll help you decide honestly, even if it means: stay on GCP, it makes sense.
Managed = more than just hosting
Cloud Run gives you compute. We add observability, AI debugging, and alerting that you'd have to build from scratch on GCP — 3-6 months of DevOps + ML work.
AI Debug Agent
Click „Explain the failures“ → Gemini goes through the last 50 failed events + your tenant config + Power-Ups → returns a likely cause + suggested fix. A confidence chip. No manual grepping through logs.
On GCP: write it yourself or a BigQuery query.
Data Quality Score
A daily 0-100 score with an A/B/C/D/F grade + a 30-day sparkline trend. Weights: match rate 30%, error freedom 30%, cookie 15%, latency 15%, consent 10%.
On GCP: Looker Studio from scratch.
Anomaly Detection + AI
A rolling 7d baseline detects „match rate dropped 18% vs the average“. AI immediately explains the cause („Meta token expired“). Pushed to Slack/Discord in parallel.
On GCP: Cloud Monitoring + Pub/Sub + Vertex AI.
Slack / Discord / Teams
Per-platform format (Block Kit / embed / MessageCard). Severity + category filters. A test button. Marketing teams live in Slack, IT in Discord — not in an email inbox.
On GCP: a Cloud Function with your own code.
A point-by-point comparison
The features you actually deal with in operating CZ/EU sGTM hosting — not a marketing list.
Migration in an afternoon, not a week
Goal: no loss of measurement data during cutover. A DNS TTL safety net, parallel deploy, one-click rollback.
Lower the CNAME TTL to 300 s
5 minIn Google Domains / Cloudflare, lower the TTL on your existing sGTM subdomain to 5 min. Pre-flight 24-48 hours ahead — DNS resolvers pick up the new values faster after just an hour.
A DataNostro account + tenant
2 minSign-up + tenant + plan. 14 days free, no credit card needed. Use the code GCP-MIGRATION-20 for -20% for 3 months.
In-dashboard GCP import
3 minIn the dashboard → Import from Stape (works for GCP too — the same Container Config Base64). Paste your Container Config from GTM Admin → Container Settings. Pre-flight preview.
Deploy the DataNostro container in parallel
2 minDataNostro deploys a Docker container on our subdomain (e.g. sst-new.yourcompany.cz). It runs in parallel with GCP — no impact on live traffic. SSL via Let's Encrypt automatically.
Smoke test + preview
15-30 minIn the GTM workspace switch the Preview server URL to our preview endpoint. Send a few test events + verify they arrived in GA4/Meta. If something's off — no impact on production.
DNS cutover — switch the CNAME
2 min DNS edit + 15 min propagationIn your DNS provider switch the CNAME of the existing sGTM subdomain (e.g. sst.yourcompany.cz) from run.app to our CNAME. Thanks to the pre-lowered TTL it propagates in 5–15 min. The existing GTM Web container already uses the new destination automatically.
Decommission GCP — no stress, even a week later
2 min + a week of monitoringYou leave GCP Cloud Run running for another 24-48 h as a safety net. If nothing fails (it hasn't yet), delete the Cloud Run instance in the GCP Console + release the static IP. The GCP invoice drops to $0.
Takes 2 minutes. We'll email you the complete migration checklist.
If something's off: rollback to GCP in 5 minutes
We recommend leaving the GCP Cloud Run instance running for 24–48 h after cutover. If anything's off during that window (a wrong response code, a missing event, odd latency), you point DNS back.
Rollback step by step
-
DNS edit:
In Cloudflare / Google Domains, point the CNAME of your existing tracking subdomain (e.g.
sst.yourcompany.cz) back to the originalSERVICE-XXX.a.run.app. Thanks to the pre-lowered TTL (300 s) it propagates within 5 min. - Nothing else: You don't have to change the GTM Web container (server_container_url points to your fixed subdomain, not the DataNostro endpoint). The Cloud Run instance is still running and immediately serves incoming events.
- Data loss: 5–15 min (the DNS resolver cache window). For GA4 reports that means 0.01% of daily traffic — below the level of statistical significance.
- Your invoice with us: The trial is 14 days free, so a rollback within this window = CZK 0. If you're already paying for the first month, we issue a credit note for the remaining days of the plan (the standard § 1829 Civil Code 14-day withdrawal window).
Honest stat: In the first 12 months of operation we didn't record a single rollback for a technical reason. Two tenants went back due to a budget change (moving to their own bare-metal). If a rollback does happen, we have the documented procedure above — no support ticket, no fix needed on our side.
What clients ask about most
Will I lose data during migration?
No, if you follow the timeline above. A 5-min DNS TTL in advance + parallel running of the DataNostro and GCP containers = during cutover, events flow through both paths. In the worst case (DNS resolver cache) you lose 5–15 minutes of data — which is sub-pixel scale for GA4.
Do I have to rewrite the GTM Server container in the GTM UI?
No. The Container Config Base64 that GCP uses is the same format as DataNostro. You just paste it into our importer — the GTM Server tags, triggers, and variables stay identical.
What about the GCP bill — do I cancel immediately?
We recommend running it in parallel for 24–48 h. Then you delete the Cloud Run instance + release the static IP. The bill for that month will be pro-rated by days of operation.
What about BigQuery export? GCP does it in a few clicks.
DataNostro doesn't have a native BigQuery export inside the dashboard. But we have a REST API via API keys + a daily CSV export to your Cloud Storage / S3 / anything via a custom webhook. If you need real-time BigQuery streaming, get in touch — we'll build a custom integration.
What about SLA and uptime?
Standard plans: 99.5% SLA. Enterprise: 99.95% SLA with a downtime penalty. GCP Cloud Run has a 99.95% SLA only for multi-region, otherwise 99.9%. Our /status/ page shows the real uptime over the last 30 days.
Can I have the migration done for me?
Yes — the DataNostro Care Standard package (CZK 19,900) includes a complete migration under our supervision, including parallel testing and DNS cutover. 5–7 days from signing to live tracking.
A parallel test-drive — 7 days free, no DNS cutover
If you don't trust the calculator's numbers and want real p95/p99 latency + match rate with your own traffic, we'll deploy a parallel DataNostro container on a new subdomain (e.g. sst-test.yourcompany.cz). Send test events to it (GTM Preview or a test workspace) while production tracking keeps running unchanged on GCP. After 7 days you compare the numbers side by side.
- No risk to production tracking — the GCP DNS stays untouched
- You see our dashboard, our latency, our match rate on your own traffic
- After 7 days you either switch DNS (a full migration) or cancel us with one click — CZK 0
We reply within 4 hours during business hours (Mon–Fri 9–17). For enterprise (>20 M req/month) we have a dedicated sales engineer.
Ready to switch?
Fill out the migration wizard and we'll send you a step-by-step checklist + a quote for supervising the cutover. No commitments.
Considering other managed providers? Stape vs Addingwell vs GCP vs DataNostro · Migrating from Stape · Migrating from Addingwell