Google Cloud Deploy pricing
This document explains Google Cloud Deploy pricing details.
Google Cloud Deploy charges for active delivery pipelines.
An active delivery pipeline is a delivery pipeline for which at least one
has been created. If a
rollout is created for that pipeline
during the billing month, then your organization is billed for that pipeline, at
the rate specified in the pricing table on this page.
|Item||Delivery pipeline cost|
|First active delivery pipeline||No charge|
|Each additional active delivery pipeline||$15 per billing month|
If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.
Charges from other Google Cloud services
In addition to per-delivery-pipeline charges from Google Cloud Deploy, you incur charges from other services which Google Cloud Deploy depends on:
Google Cloud Deploy uses Cloud Build for rendering and deploying. These activities are performed in the same region as the delivery pipeline. You're billed for each activity according to Cloud Build's pricing.
By default, Google Cloud Deploy uses an e2-medium Cloud Build instance.
Google Cloud Deploy delivery pipelines can be configured to use a Cloud Build custom worker, for which you're billed according to custom worker pricing.
Google Cloud Deploy uses a Cloud Storage bucket to store rendering source code and rendered Kubernetes manifests. The bucket is located in the same regions as the Google Cloud Deploy delivery pipeline. You're billed at the regional Cloud Storage pricing.
Google Cloud Deploy uses Cloud Audit Logs to create audit logs. You're billed at Cloud Audit Logs pricing
Cloud Deploy uses Cloud Logging for storing platform logs.
You're billed at standard Google Cloud's operations suite pricing.
- Read the Google Cloud Deploy documentation.
- Get started with Google Cloud Deploy.
- Try the Pricing calculator.