FixedmarkGoogle Cloud NAT Static IP: Cost vs a Proxy
Google Cloud NAT with a reserved external IP gives VMs, GKE, and Cloud Run (through VPC egress) a static outbound address. Public NAT costs $0.0014 per VM per hour up to 32 VMs, capped at $0.044/hr per gateway, plus $0.045 per GiB processed and $0.005/hr per IP. Fixedmark is a planned proxy with a dedicated pair from $29/mo that works from any platform; it is in early access.
Fixedmark vs Google Cloud NAT at a glance
Fixedmark values are planned launch features and pricing. Google Cloud NAT values are taken from published vendor pages and attributed below. Checked October 2026.
| Fixedmark (planned) | Google Cloud NAT (published) | |
|---|---|---|
| Hourly charge | None | $0.0014 per VM instance per hour, capped at $0.044/hr above 32 VMs |
| Data charge | Included up to plan bandwidth (200 GB on Pro) | $0.045 per GiB processed, plus standard egress |
| Static IP | Pair included in plan | $0.005/hr per external IP used by the gateway (about $3.65/mo) |
| High availability | IP pair included | Managed, software-defined service. No gateway VM to run. |
| Where it works | Any platform, including Cloud Run without VPC egress | Resources in that VPC and region, and Cloud Run or Cloud Functions with VPC egress set to all traffic |
| Setup | Set FIXEDMARK_PROXY_URL, route calls through it | Reserve an IP, create a Cloud Router and NAT gateway, configure VPC egress |
| Code changes | Proxy agent on allowlisted calls | None. All routed egress uses the NAT IPs. |
| Regions | Mumbai, Singapore, Frankfurt, New York, Virginia at launch | Every Google Cloud region |
The arithmetic
Cloud NAT bills three things, per Google's pricing page. The gateway costs $0.0014 per hour for each VM instance using it, up to 32 instances. Above 32 the charge is a flat $0.044/hr, about $32 a month. Each external IP the gateway uses costs $0.005/hr, about $3.65 a month. Every GiB processed costs $0.045, in both directions.
Google's own example: a gateway serving 14 VMs with one external IP and 100 GiB of traffic comes to $22.21 for a 720-hour month. A larger setup with 36 VMs, two IPs, and 200 GiB comes to $47.88. Standard internet egress charges apply on top in both cases.
Cloud Run needs VPC egress first
Cloud Run does not use Cloud NAT by default. Google's static outbound IP guide has you reserve a static IP, create a Cloud Router and a NAT gateway, then deploy the service with Direct VPC egress or a Serverless VPC Access connector and set egress to all traffic. All outbound requests then go through your VPC, not only the allowlisted ones. The Cloud Run integration guide shows the proxy route instead.
What Cloud NAT does better
Cloud NAT is managed and distributed. Google says routing through it adds no extra hop, because the gateway and router are control plane only. Every protocol and library uses the static IP with no code changes, it runs in every Google Cloud region, and the cost stays on your Google Cloud bill. If your workloads already sit in a VPC for Cloud SQL private IP or Memorystore, adding NAT is a small step.
When to choose Cloud NAT instead
Cloud NAT is the right answer when:
- Your VMs, GKE nodes, or Cloud Run services already use a VPC.
- You need every protocol and SDK to use the static IP with no code changes.
- Policy requires all egress to stay inside your Google Cloud project.
- You need a static IP today. Fixedmark is in early access.
- You have a few VMs and modest traffic, where Cloud NAT can cost less than a proxy plan.
When Fixedmark fits better
A static IP proxy is simpler when:
- Only a few calls need a static IP and you do not want all Cloud Run egress routed through a VPC.
- Services on Google Cloud and on other platforms must share one IP pair.
- You want per-connection logs and destination allowlists on each token.
- You want a Mumbai or Singapore egress pair that does not depend on where your compute runs.
Sources
Checked October 2026. Confirm current details on the vendor's site before you decide. Prices and limits change.
Related guides
- IntegrationGoogle Cloud RunA fixed outbound IP for Cloud Run services and jobs without a VPC and Cloud NAT.
- ComparisonAWS NAT GatewayThe real monthly cost of a highly available AWS NAT Gateway, and when a static IP proxy is simpler.
- Use casePostgres and MySQLAllowlist two IPs on RDS, Cloud SQL, or a self-hosted database and connect through SOCKS5 or a local tunnel.
- Use casePartner API allowlistingGive Salesforce, SOAP vendors, and payment gateways one dedicated IP pair to allowlist, wherever your code runs.
- ToolWhat's my IP?Check which IP a destination sees from your app.
Frequently asked questions
How much does Google Cloud NAT cost?
Public NAT costs $0.0014 per VM instance per hour up to 32 VMs, or $0.044/hr above that, plus $0.045 per GiB processed and $0.005/hr for each external IP. Standard egress charges apply on top.
How do I give Cloud Run a static outbound IP?
Google's method is to reserve a static IP, create a Cloud Router and Cloud NAT gateway, and deploy the service with Direct VPC egress or a connector, with egress set to all traffic. Alternatively, route only the allowlisted calls through a static IP proxy.
Does Cloud NAT add latency?
Google says no extra hop is added, because the Cloud NAT gateway and Cloud Router are control plane only. A proxy does add a hop, so pick a proxy region close to the destination.
Can Cloud NAT give Vercel or Railway a static IP?
No. Cloud NAT only translates traffic from resources in its own VPC network. Other platforms need their own static IP option or a proxy.
Make it fixed.
Fixedmark is in early access. Join the list to get dedicated static IPs when your region opens.