Licensing Fee for premium operating systems
A separate charge for the operating system licence on VMs running RHEL, SUSE, Windows Server, or SQL Server. It is billed per vCPU-hour on top of the compute charge, so it scales with instance size and can quietly exceed the compute cost on large instances.
Billed: Per vCPU-hour, on top of the instance charge. Rates vary by OS and sometimes step at 4+ vCPUs.
What triggers this charge
- Any VM booted from a premium OS image, including images inherited from a template or a marketplace product.
- Instance size, because the licence is per vCPU — the same OS costs four times as much on a 16-vCPU machine as on a 4-vCPU one.
- Windows Server and SQL Server, which carry the highest rates.
- Committed use discounts do not apply to most licence SKUs, so this line stays at list price even when your compute does not.
How to reduce it
Check whether the premium OS is a requirement or an inheritance
Workloads are frequently on RHEL or Windows because a template said so years ago. Where the application is portable, Rocky, Debian, or Ubuntu carry no licence charge.
Right-size before optimising anything else
Because the licence is per vCPU, halving an oversized instance halves the licence charge too. The saving is roughly double what the compute line suggests.
Investigate bring-your-own-licence
Sole-tenant nodes with existing licences can remove the charge entirely for organisations with an enterprise agreement.
Rates
Related charges
Now find out how much of this you are actually paying.
Finitizer breaks your Google Cloud bill down to the SKU, shows how each one has moved since last week, and separates rate changes from usage changes — so you know whether to talk to engineering or to procurement.