GCP Cloud Workstations cost: pay per hour a workstation runs

Quick answer

Cloud Workstations bills a management fee plus the underlying Compute Engine VM (by machine type) and persistent disk while a workstation is running, with auto-shutdown on idle. Cost scales with running hours and machine size, so the classic waste is a workstation left running idle. Auto-shutdown, right-sized machine types, and stopping workstations when not in use are the levers.

Google Cloud Workstations provides managed, cloud-hosted development environments. You pay for a workstation while it runs, the management fee plus the VM and disk it uses, and it can auto-shut down when idle. So the cost is running hours times machine size, and the main lever is not paying for idle workstations.

What you pay while running

Component	Bills for
Management fee	Per running workstation-hour
Compute Engine VM	By machine type, while running
Persistent disk	Storage, including while stopped

While a workstation runs, you pay the Cloud Workstations management fee plus the standard Compute Engine cost for its machine type. The persistent disk (holding the developer's environment) bills for storage even while the workstation is stopped, but that is small compared to the running compute.

Idle is the enemy

A workstation left running while a developer is at lunch, in meetings, or gone for the day bills for VM-hours doing nothing. Cloud Workstations supports auto-shutdown after a period of inactivity, which is the single most important cost control, it stops the VM (and its compute billing) when the developer stops working, the same idle discipline as non-production environments.

Controlling Cloud Workstations cost

Enable auto-shutdown with a sensible idle timeout so workstations stop when not in use, right-size machine types to what developers actually need (not a generous default across the team), keep persistent disks reasonably sized, and use the fast start-up so developers do not resist shutdown. With auto-shutdown on and machines right-sized, Cloud Workstations costs for hours actually worked rather than around the clock.

FAQ

How is GCP Cloud Workstations priced?

A management fee per running workstation-hour plus the underlying Compute Engine VM (by machine type) and persistent disk while running, with auto-shutdown on idle. The persistent disk bills for storage even while stopped, but that is small compared to running compute. Cost scales with running hours and machine size.

How do I reduce Cloud Workstations cost?

Enable auto-shutdown with a sensible idle timeout so workstations stop when not in use, right-size machine types to what developers actually need rather than a generous team-wide default, keep persistent disks reasonably sized, and rely on fast start-up so developers accept shutdown. Auto-shutdown is the biggest lever.

Why do idle Cloud Workstations waste money?

Because they bill for the Compute Engine VM and management fee while running, whether or not the developer is active. A workstation left on during lunch, meetings, or overnight pays for VM-hours doing nothing. Auto-shutdown after inactivity stops the compute billing when work stops, eliminating this waste.

Does a stopped Cloud Workstation cost anything?

Only the persistent disk storage, which holds the developer's environment so it persists across sessions. That storage cost is small compared to the running VM and management fee. When stopped, the VM compute and management fee stop, so a stopped workstation is cheap.

How should I size Cloud Workstation machines?

To what developers actually need for their work, not a generous default applied across the whole team. A developer running heavy builds needs more than one editing configuration files. Right-sizing machine types per role or need, combined with auto-shutdown, keeps cost proportional to actual usage.

Does C3X estimate Cloud Workstations cost?

Cloud Workstations cost is driven by running hours and machine type, which are usage inputs. C3X prices the underlying Compute Engine and disk resources, and you model workstation running hours to estimate the managed-development-environment charges.

What to do next

Price your development environments before you roll them out. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.