Managing Deployments
What are deployments?
Section titled “What are deployments?”Deployments are named runtime targets that help you organize where tools execute and how edge-backed infrastructure is managed. They are useful for separating environments such as production, staging, or region-specific setups.
In the current admin UI, a deployment primarily captures runtime metadata, status, and edge bundle assignment where applicable.
Deployment list view
Section titled “Deployment list view”Navigate to Admin > Deployments to see all deployments in your organization. The list view shows:
| Column | Description |
|---|---|
| Name | The deployment’s display name |
| Type | The client type associated with the deployment |
| Runtime Kind | Whether the runtime is cloud-managed or edge-device based |
| Status | Whether the deployment is currently active |
| Last seen | Most recent runtime heartbeat, if one exists |
| Created | When the deployment was created |
Creating a deployment
Section titled “Creating a deployment”-
Navigate to Admin > Deployments and click Create Deployment.
-
Enter a name for the deployment. Choose a descriptive name that reflects its purpose (e.g., “Production - EU”, “Staging”, “IT Infrastructure”).
-
Optionally provide a description to help team members understand the deployment’s scope.
-
Save the deployment.
-
If this is an edge deployment, open it afterwards to assign the bundle it should use.
Deployment statuses and lifecycle
Section titled “Deployment statuses and lifecycle”A deployment can appear as:
| Status | Meaning |
|---|---|
| Active | A runtime associated with the deployment is currently available |
| Inactive | No active runtime has been seen recently |
Edge bundle assignment
Section titled “Edge bundle assignment”Edge deployments can have a bundle assignment that controls which edge implementations are available there.
To assign a bundle:
- Open the deployment from the list view.
- Go to the bundle section.
- Choose a bundle and, if needed, pin a specific version.
- Save the assignment.
Connected edge runtimes pick up the assigned bundle on their next sync cycle.
Last-seen monitoring
Section titled “Last-seen monitoring”The Last seen column in the deployment list shows when the platform last received a heartbeat for that deployment. Use this to:
- Detect inactive runtimes
- Verify connectivity after rollout
- Track operational activity over time
Deactivating and deleting deployments
Section titled “Deactivating and deleting deployments”Deactivating an edge deployment marks it inactive for future runtime use. Deleting a deployment removes its configuration permanently.
Before deleting a deployment, make sure it is no longer needed by your edge setup or operational workflows.
Managing deployments
Section titled “Managing deployments”Deployments are managed through Admin > Deployments. Some cloud-managed deployment operations are handled outside the standard editor flow.