Deploy Apps

Your app goes live on its built-in environment as soon as you publish. To run it in other environments, such as staging or production, deploy a published version there.

​

Deploy an App

Deploy from the Publish dropdown right after publishing, or from the Deploy tab inside the app. Choose the target environment and version, then configure the deployment:

• Pick the model and integration credentials the app uses there.
• For each environment variable the version defines, choose where its value comes from:
  • Version value: the value saved in the version you’re deploying.
  • Last deployed value: the value from the app’s previous deployment to this environment.
  • Custom value: a value for this environment alone.

A deployment touches only its target environment: the built-in environment and all others keep serving what they already run. If the deployment fails, other apps running in the target environment are unaffected. Detailed failure reasons are available in the Enterprise Dashboard: open the environment under Environments and check its Deployments tab.

​

Update or Roll Back

To update or roll back the app running in an environment, deploy a different version there. Click Deploy latest for the newest published version. To pick any other version, click Change version on the Deploy tab, or All versions in the Publish dropdown. While the new version deploys, the environment keeps serving its current one. The switch happens only when the deployment succeeds. If it fails, the current version keeps serving without interruption. Detailed failure reasons are available in the Enterprise Dashboard: open the environment under Environments and check its Deployments tab.

​

Change the Deployment Configuration

To change the credentials or environment variable values the app uses in an environment, click Redeploy on the Deploy tab and adjust the configuration as needed. The version stays the same, and the app keeps serving throughout: on the new configuration once it applies, or on the previous one if the redeploy fails.

​

Undeploy

To stop serving the app in an environment, click Undeploy on the Deploy tab. Access stops for end users right away, and your deployment configuration is kept.

​

Configure Access per Environment

In deployed environments, your app can be reached through the web app and the Service API, both configured on the app’s Access Point tab. To share the web app, turn it on and set who can access it. Each environment gets its own URL. To call the app through the API, turn it on and generate an API key for the environment. All deployed environments share one API endpoint, and the key you use decides which environment the request goes to. Generated API keys remain valid even if you undeploy the app from the environment: calls fail while it’s undeployed, but once you deploy there again, the same keys still work.

​

Monitor Deployed Apps

To see the app’s runs in deployed environments, open Invocation Logs in the Enterprise Dashboard. The Logs and Monitoring tabs in Studio cover the built-in environment only. Run traces and metrics from deployed environments can also stream to your own observability platform through Data Push, configured in the Enterprise Dashboard.

​

Troubleshooting