Practical guide
Estimate a Cloud NAT monthly cost
Model Public Cloud NAT from assigned VMs, gateway hours, processed GiB, IP addresses, and outbound data transfer.
Updated · Sources checked
Use the three Public NAT quantities
Google prices Public Cloud NAT with a gateway hourly charge based on assigned VMs, processed data per GiB, and external-IP hourly charges. Data transfer out can also apply. The gateway VM count rate is capped after 32 assigned VMs, so model assignments rather than just gateway count.
Example: 14 assigned VMs for 730 hours is 10,220 VM-hours; one IP for 730 hours is 730 IP-hours; 500 GiB processed is 500 GiB. Multiply each by Google’s current rate, then estimate internet egress separately by destination. The calculator’s components should remain separate so growth in data is not mistaken for an IP charge.
Check logging separately: Google points Cloud NAT logging to network telemetry pricing. Review assignment count, processed bytes, IP count, and data-transfer destination from billing data after deployment.
Use the Cloud NAT Cost Calculator and add the GCP Network Egress Calculator for traffic leaving Google Cloud.
FAQ
Does NAT processing include both directions?
Google’s pricing page describes processed inbound and outbound data for the gateway.
Does NAT replace egress cost?
No. Internet data transfer out can be an additional cost.