Stay organized with collections
Save and categorize content based on your preferences.
Cloud Deploy pricing
This document explains Cloud Deploy pricing details.
Basic pricing
Cloud Deploy charges for active multiple-target delivery
pipelines.
Pricing table
Item
Delivery pipeline cost
First active† multiple-target†† delivery pipeline (per billing account)
No charge
Each additional active multiple-target delivery pipeline
$5 per billing month
†An active delivery pipeline is a delivery pipeline for
which at least one release or rollout
has been created during the billing month. If a release or rollout is
created for that delivery pipeline during that month, then your organization is
billed for that delivery pipeline at the rate specified in the pricing table on
this page. Delivery pipelines that aren't active don't incur the charge.
†† A multiple-target delivery pipeline is a
delivery pipeline that references more than one target. This may be a delivery
pipeline with a progression using more
than one target, or a delivery pipeline using a
multi-target. Delivery pipelines using
exactly one target do not incur a charge. A delivery pipeline using multiple
targets that is activated at any time during an invoicing period can be charged
as a multiple target delivery pipeline.
Pricing is determined based on delivery pipeline name. If you delete a pipeline
and then create a new one with the same name, they're treated as a single
pipeline, for billing purposes.
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 Cloud Deploy, you
incur charges from other services which Cloud Deploy depends on:
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, Cloud Deploy uses an e2-medium Cloud Build
instance.
Cloud Deploy delivery pipelines can be configured to use a
Cloud Build custom worker, for which you're billed according to
custom worker pricing.
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 Cloud Deploy delivery pipeline. You're billed
at the regional Cloud Storage pricing.
With Google Cloud's pay-as-you-go pricing, you only pay for the services you
use. Connect with our sales team to get a custom quote for your organization.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["\u003cp\u003eCloud Deploy charges $5 per billing month for each active multiple-target delivery pipeline beyond the first one, which is free per billing account.\u003c/p\u003e\n"],["\u003cp\u003eA delivery pipeline is considered active and incurs charges if at least one release or rollout is created during the billing month.\u003c/p\u003e\n"],["\u003cp\u003eA multiple-target delivery pipeline, which is the type of pipeline that is charged, is defined as one that references more than one target, either through a progression or by using a multi-target setup.\u003c/p\u003e\n"],["\u003cp\u003eIn addition to Cloud Deploy's delivery pipeline charges, you will incur costs from other Google Cloud services it utilizes, including Cloud Build, Cloud Storage, Cloud Audit Logs, and Google Cloud Observability.\u003c/p\u003e\n"]]],[],null,["# Pricing\n\nCloud Deploy pricing\n====================\n\nThis document explains Cloud Deploy pricing details.\n\nBasic pricing\n-------------\n\nCloud Deploy charges for *active* multiple-target delivery\npipelines.\n\n\u003cbr /\u003e\n\nPricing table\n-------------\n\n^†^An active delivery pipeline is a delivery pipeline for\nwhich at least one [`release`](/deploy/docs/terminology#release) or [`rollout`](/deploy/docs/terminology#rollout)\nhas been created during the billing month. If a `release` or `rollout` is\ncreated for that delivery pipeline during that month, then your organization is\nbilled for that delivery pipeline at the rate specified in the pricing table on\nthis page. Delivery pipelines that aren't active don't incur the charge.\n\n^†^^†^ A multiple-target delivery pipeline is a\ndelivery pipeline that references more than one target. This may be a delivery\npipeline with a [progression](/deploy/docs/terminology#progression) using more\nthan one target, or a delivery pipeline using a\n[multi-target](/deploy/docs/terminology#multi-target). Delivery pipelines using\nexactly one target do not incur a charge. A delivery pipeline using multiple\ntargets that is activated at any time during an invoicing period can be charged\nas a multiple target delivery pipeline.\n\nPricing is determined based on delivery pipeline name. If you delete a pipeline\nand then create a new one with the same name, they're treated as a single\npipeline, for billing purposes.\n\n\nIf you pay in a currency other than USD, the prices listed in your currency on\n[Cloud Platform SKUs](https://cloud.google.com/skus/)\napply.\n| **Note:** Cloud Deploy uses Google Cloud services, and you're billed for use of those services.\n\nCharges from other Google Cloud services\n----------------------------------------\n\nIn addition to per-delivery-pipeline charges from Cloud Deploy, you\nincur charges from other services which Cloud Deploy depends on:\n\n- [Cloud Build](/build)\n\n Cloud Deploy uses Cloud Build for rendering and\n deploying. These activities are performed in the same region as the delivery\n pipeline. You're billed for each activity according to\n [Cloud Build's pricing](/build/pricing).\n\n By default, Cloud Deploy uses an e2-medium Cloud Build\n instance.\n\n Cloud Deploy delivery pipelines can be configured to use a\n Cloud Build custom worker, for which you're billed according to\n [custom worker pricing](/build/docs/custom-workers/custom-workers-pricing-quota).\n- [Cloud Storage](/storage)\n\n Cloud Deploy uses a Cloud Storage bucket to store rendering\n source code and rendered Kubernetes manifests. The bucket is located in the\n same regions as the Cloud Deploy delivery pipeline. You're billed\n at the regional [Cloud Storage pricing](/storage/pricing).\n- [Cloud Audit Logs](/logging/docs/audit)\n\n Cloud Deploy uses Cloud Audit Logs to create audit logs. You're\n billed at [Cloud Audit Logs pricing](/logging/docs/audit#pricing)\n- [Google Cloud Observability](/stackdriver)\n\n Cloud Deploy uses Cloud Logging for storing platform logs.\n\n You're billed at standard [Google Cloud Observability pricing](/stackdriver/pricing).\n\nWhat's next\n-----------\n\n- Read the [Cloud Deploy documentation](/deploy/docs).\n- Get started with [Cloud Deploy](/deploy/docs/deploy-app-gke).\n- Try the [Pricing calculator](/products/calculator).\n\n#### Request a custom quote\n\nWith Google Cloud's pay-as-you-go pricing, you only pay for the services you use. Connect with our sales team to get a custom quote for your organization.\n[Contact sales](/contact?direct=true)"]]
