Before any sGTM migration discussion, you need to know what your actual monthly GCP spend is — vCPU + RAM + egress + Cloud Logging + static IP combined. This page walks you through 6 steps (~90 seconds) to find it in GCP Console plus exactly what to look for.
What you'll have at the end
A concrete USD/month number broken down by service, plus a CSV export you can compare against our savings calculator:
| Service | Monthly cost | % of total |
|---|---|---|
| Cloud Run (vCPU + RAM) | $45–80 | 40–60% |
| Network egress | $8–25 | 15–25% |
| Cloud Logging | $5–20 | 10–20% |
| Static IP | $1.50 | 2–3% |
| Typical 5M req/month e-shop | $60–125 |
Step 1 — Open GCP Console Billing
Open https://console.cloud.google.com/billing. If you have multiple Google accounts, make sure you're logged in to the one where sGTM is billed.
Don't see Billing menu? You don't have Billing Account Viewer/Admin permission. In that case:
- For internal e-shop: ask your CFO or IT admin for "Billing Account Viewer" role on your GCP project
- For a client: ask them for a Billing Reports screenshot via email
Step 2 — Select the correct billing account
If your company has multiple billing accounts (typically when there are separate projects per client or per environment), pick the one linked to your sGTM project.
Click the billing account where sGTM runs. Then in the left menu select "Reports".
Step 3 — Reports → filter to sGTM services
Reports shows a timeline chart. By default it displays ALL services in the project. You only want sGTM components.
Open the "Filters" panel on the right and apply:
Step 4 — Identify sGTM services in the list
sGTM container runs as:
| If you use | Look for these "Service" names |
|---|---|
| Cloud Run (most common) | Cloud Run, Cloud Run Network, Cloud Logging |
| App Engine (legacy from 2020) | App Engine, App Engine Network, Cloud Logging |
| Compute Engine (custom self-host) | Compute Engine, Networking, Persistent Disk |
| Always | Networking (egress) + Cloud Logging |
Network/egress is the biggest hidden cost — accounts for 15–25% of total bill and grows linearly with request volume.
Step 5 — Read the SKU breakdown
After filtering you'll see a table like this:
| SKU | Usage | Cost (USD) |
|---|---|---|
| CPU Allocation Time | 720 h | $28.80 |
| Memory Allocation Time | 720 h × 512 MiB | $5.04 |
| Request Count | 5,200,000 | $2.08 |
| Network Egress (EU → EU) | 12 GiB | $1.44 |
| Network Egress (EU → US) | 3 GiB | $0.36 |
| Log Storage | 8 GiB | $3.20 |
| Static IP (idle) | 720 h | $1.50 |
| Total | $42.42 / month |
Tip: The top-right of the table has a "Download CSV" button — export it. Send it to [email protected] or upload to our calculator to see exact savings.
Step 6 — Find the 3 most common billing surprises
If your total monthly cost is significantly higher than $50, look for these 3 SKUs:
🔴 Surprise #1: Cloud Logging gone wild
If --log-stdout or verbose logging is enabled in sGTM container, Cloud Logging charges $0.50/GiB after 50 GiB/month free tier. A busy e-shop with 5M req/month typically generates 30-100 GiB logs = $15–50/month extra.
Fix: lower log level in sGTM or set log exclusion filter in Cloud Logging.
🔴 Surprise #2: min-instances=1
Default Cloud Run scaling saves money — but if you've set min-instances=1 (to avoid cold-start latency), you pay for idle vCPU 24/7, even when nobody uses the site. This doubles Cloud Run cost.
Fix: Cloud Run service settings → Autoscaling → min instances. If you don't know why it's 1, set to 0.
🔴 Surprise #3: Cross-region egress
If sGTM runs in europe-west1 and you send data to us-central1 destinations (= most ad platforms), you pay $0.12/GiB inter-region egress. At 5M requests = ~10 GB egress = $1.20/month.
Fix: this is a structural problem — sGTM traffic inherently calls US-based ad platform APIs. Migrating to an EU-only provider (like DataNostro) eliminates this fee entirely.
Next steps — compare with DataNostro
Once you have your current monthly number, compare:
- DataNostro STARTER: 390 CZK/month (≈ $17) for 1M req
- DataNostro PRO: 990 CZK/month (≈ $42) for 5M req
- DataNostro BUSINESS: 2,490 CZK/month (≈ $107) for 20M req
No egress charges, no Cloud Logging surcharge, no idle vCPU billing. Fixed CZK amount, ISDOC invoice, plus Czech support.
GCP migration details → Calculate my savings
FAQ
Q: I don't have Billing access?
Ask your IT / CFO for the Billing Account Viewer role. For internal comparison, a single CSV export is enough.
Q: Can you pull my GCP costs for me?
No — we don't have access to your GCP project (and shouldn't have). We're sending you this guide so you can do it yourself in 5 minutes.
Q: Cloud Run charges me different amounts each month — why?
Cloud Run is metered = you pay for actual consumption. Bills fluctuate with traffic volume. DataNostro has a fixed tariff — Black Friday vs January = same amount.
Q: Can I time the migration so I don't double-pay GCP?
Yes — Cloud Run only charges for actual usage. After DNS cutover to DataNostro, GCP traffic drops to 0 and your end-of-month bill will be proportional (not the full month).