Deploy a pod to assign hardware resources to a browser automation experiment. Once deployed, the automation is published and available in the Browser Automation node within workflows, where all defined variables and configuration parameters can be accessed. Deployment also supports versioning, approvals, validation checks, and rollback mechanisms to promote workflows and agents safely from development to staging and production. Navigation: Go to Settings → Browser Automation → Deployment.Documentation Index
Fetch the complete documentation index at: https://koreai.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
With Browser Automation Deployment, you can:
- Deploy a pod for a browser automation experiment.
- Customize resource allocation for deployments.
- Set auto-scaling limits to ensure optimal performance.
- Review deployed and ready-to-deploy pods.
- View details of the latest and previous deployment versions.
- Redeploy pods that were previously undeployed.
- Undeploy or delete pods.
- Search for a deployment.
Billing and credit usage for Browser Automation are calculated based on the deployed pods and hardware configuration.
Deployment Dashboard
The Deployment page shows the following information for each pod:| Field | Description |
|---|---|
| Deployment name | Name assigned to the deployment. |
| Description | Brief description of the deployment. |
| Status | Current status: Deploying, Deployed, or Ready to Deploy. |
| Created by | User who created the deployment pod. |
| Updated on | Date the deployment was last updated. |
Deploy a Pod
Prerequisite: Ensure your account has sufficient credits to deploy a pod.- Click Deploy in the top-right corner.
- In General Settings, enter the Deployment name and Description.
-
In Resource allocation, configure the following:
Scaling parameters:
Hardware: Select a hardware profile (number of vCPUs) from the dropdown.
Parameter Description Min replicas Minimum number of pods per service. Recommended: 1. Max replicas Maximum number of pods per service. Recommended: 1. Auto-scaling threshold When average compute load exceeds this percentage, the system automatically adds more pods to handle increased demand. Recommended: 75%. Selecting a hardware profile displays the hourly credit consumption, profiling data, and the number of browser automations that can run in parallel on that hardware. Additional requests are queued. - Review the deployment details and accept the terms.
- Click Deploy to proceed. You can also save the configuration as a draft or go back to modify details.
View Deployment Details
Click a deployment entry to see the following tabs:| Tab | Description |
|---|---|
| Overview | Shows the configured general settings and resource allocation. |
| Deployment History | Lists all deployment and undeployment versions by date and time. The latest version is marked with a green check icon. Click the expansion icon to view duration, start and end times, deployment time, and status. |
| Configurations | Shows the deployment name and description. Provides options to undeploy or delete the pod. |
Delete permanently removes the pod and its data from all experiments where it is deployed. Only a Master Admin or Workspace Owner can delete a pod. Proceed with caution — this action cannot be undone.
Undeploy a Pod
Undeploying a pod temporarily disassociates it from all browser experiments. You can redeploy it later.- On the Deployment page, click the pod you want to undeploy.
- Click Configurations on the left menu.
- In the Danger Zone section, click Proceed to Undeploy.
- Click Un-deploy in the confirmation window.
Redeploy a Pod
You can redeploy an active or undeployed pod and optionally update the general and resource allocation settings before redeployment.- On the Deployment page, click the pod you want to redeploy.
- Click Re-deploy in the top-right corner, then confirm in the dialog.
- Modify any required parameters. See Deploy a Pod for configuration steps.
- Click Deploy on the Review page.