Stay organized with collections
Save and categorize content based on your preferences.
This page describes how to deploy a SaaS offering, which means that
SaaS Runtime provisions the Google Cloud resources and deploys the
SaaS application in the regions specified in the SaaS offering resource.
To deploy the SaaS offering, SaaS Runtime creates the unit by deploying
the blueprint associated with a unit kind.
To deploy the SaaS offering, SaaS Runtime provisions the resources that
are part of a unit kind. The term in SaaS Runtime for the provisioned
resources or deployed application is a unit.
When you create a unit, SaaS Runtime provisions the resources defined in the
Terraform configuration that is connected to the unit kind. The resources are
provisioned in each region that is part of the SaaS offering.
For example, if you had a unit kind for a single VM, then when you create a
unit, SaaS Runtime provisions the VM in the regions defined in the
SaaS offering.
See that the State is Ready (or the state might be
Provisioning while the operation is still in progress).
Expand the Variables section.
In the Output variables, you can see details related to any
output variables specified in the Terraform configuration. For more
details about variables, see
Variables and variable mapping.
[[["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"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Deploy a SaaS offering\n\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThis page describes how to deploy a SaaS offering, which means that\nSaaS Runtime provisions the Google Cloud resources and deploys the\nSaaS application in the regions specified in the SaaS offering resource.\n\nTo deploy the SaaS offering, SaaS Runtime creates the unit by deploying\nthe blueprint associated with a unit kind.\n\nBefore you begin\n----------------\n\nEnsure you have created the following:\n\n1. A [SaaS offering resource](/saas-runtime/docs/create-saas-offering) for your SaaS application.\n2. Unit kinds to [model the SaaS offering](/saas-runtime/docs/model-saas-offering).\n\n### Deploy the SaaS offering\n\nTo deploy the SaaS offering, SaaS Runtime provisions the resources that\nare part of a unit kind. The term in SaaS Runtime for the provisioned\nresources or deployed application is a *unit*.\n\nWhen you create a unit, SaaS Runtime provisions the resources defined in the\nTerraform configuration that is connected to the unit kind. The resources are\nprovisioned in each region that is part of the SaaS offering.\n\nFor example, if you had a unit kind for a single VM, then when you create a\nunit, SaaS Runtime provisions the VM in the regions defined in the\nSaaS offering.\n\n1. Create a unit:\n\n 1. In the console, go to **SaaS Runtime** \\\u003e **Units**.\n\n [Go to Units](https://console.cloud.google.com/saas/units)\n 2. Select **Create**.\n\n 3. On the **Unit details** page:\n\n 1. For **Unit name**, type a name for the unit. The name must\n contain only lowercase letters, numbers, or hyphens.\n\n 2. Under **SaaS offering**, select the SaaS offering resource\n that you created earlier.\n\n 3. Under **Region**, select the region where you want to deploy\n the resources or application.\n\n 4. Under **Unit kind**, select the unit kind that defines the\n resources or application that you want to deploy.\n\n 5. Under **Management mode** , select **User**.\n\n - **Unspecified** if\n - **User** to have units deprovisioned manually. Units are not deprovisioned automatically by SaaS Runtime.\n - **System** to have SaaS Runtime deprovision dependent units when they are no longer needed.\n 6. Optional: Add a label to the resources that you are deploying.\n For more details about labels, see the\n [Labels overview](/resource-manager/docs/labels-overview).\n\n To add a label:\n 1. Under **Labels** select **Add labels**.\n\n 2. For **Key 1** and for **Value 1**, enter the desired\n key-value pair.\n\n 3. Repeat the steps above for each label that you want add.\n\n 7. Select **Create**.\n\n2. To provision the resources or deploy the application:\n\n 1. On the **Units** \\\u003e **Create a unit** page, select **Provision**.\n\n 2. For the release field, select the release for the versions of the\n Terraform configuration that you want to deploy.\n\n 3. For the **Service account**, select the service\n account\n\n 4. Add a Tenant project:\n\n 1. Select **Add tenant project variables**.\n 2. Define the first input variable:\n 1. For **Name** , keep the name `tenant_project_id`\n 2. For **Variable type** , select **String**.\n 3. For **Variable value** type `quickstart-tenant-project`.\n 3. Define the second input variable:\n 1. For **Name** , keep the name `tenant_project_number`\n 2. For **Variable type** , select **Integer**.\n 3. For **Variable value** enter your [project number](/resource-manager/docs/creating-managing-projects#identifying_projects).\n 5. Select **Provision**.\n\nView the deployed unit\n----------------------\n\nYou have now used SaaS Runtime to create a unit, which deploys the\nresources or application in the associated unit kind.\n\nTo view the resources that you deployed:\n\n1. In console, go to the **SaaS Runtime** \\\u003e **Units** \\\u003e **Unit details** page.\n\n [Go to Units](https://console.cloud.google.com/saas/units)\n2. Click the name of your unit.\n\n3. On the **Unit details** page:\n\n 1. See that the **State** is **Ready** (or the state might be **Provisioning** while the operation is still in progress).\n 2. Expand the **Variables** section.\n 3. In the **Output variables** , you can see details related to any output variables specified in the Terraform configuration. For more details about variables, see [Variables and variable mapping](/saas-runtime/docs/variables).\n\nWhat's next\n-----------\n\n- To learn more about SaaS Runtime, see the [SaaS Runtime overview](/saas-runtime/docs/overview).\n- For more details about the service accounts needed when using SaaS Runtime, see [service accounts](/saas-runtime/docs/service-accounts).\n- For the steps to update the release, see [Rollout a release](/saas-runtime/docs/update-saas-offering)."]]