Deployments & devices

What is a deployment?

A deployment is a connected edge connector runtime registered with your organization. There are three runtime kinds:

• Cloud Connector — a managed connector provisioned and hosted by nara.
• Edge Desktop — the connector running on a user’s workstation.
• Edge Server — the connector running on a server in your infrastructure.

Deployments execute tools with Edge implementations, sync tool bundles, and report their status back to the platform.

Deployment list

Open Admin > Deployments (/admin/deployments). The table shows each deployment’s Name, Type, Runtime Kind, the linked Cloud Connector / Edge Device, Status, Last Seen, and Created date. Use Last Seen to spot connectors that have stopped reporting.

Deployment detail

Open a deployment to see its info panel and management actions:

• Deactivate — takes the deployment out of rotation without removing it.
• Delete — removes the deployment permanently.
• Managed via Edge CLI — indicates the deployment is administered through the edge-connector CLI rather than the web UI.

Bundle assignment and versioning

Tool bundles are versioned packages of edge tool implementations, uploaded via the edge-connector CLI. The bundle section of a deployment detail shows:

• Assigned Bundle — the bundle this deployment runs.
• Tools in Bundle — the tools contained in the assigned bundle.
• Version — either Latest (vN), which follows new uploads automatically, or Pinned to vN, which locks the deployment to a specific version.

Assign a bundle from the deployment detail, or from the CLI:

edge-connector bundle assign <bundleId> --deployment <deploymentId> [--version <n>]

Pin a version when a deployment must stay on a validated bundle; use Latest for deployments that should pick up new tool releases immediately. See the edge connector CLI reference for the full bundle command set.

Cloud connectors

Cloud connectors are provisioned and controlled through the edge-connector cloud CLI commands, which call the platform’s /api/edge/cloud/* endpoints:

edge-connector cloud provision --env <dev|stage|prod>
edge-connector cloud start
edge-connector cloud stop
edge-connector cloud status
edge-connector cloud delete

Once provisioned and started, the cloud connector appears in the deployments list like any other runtime, and you assign bundles to it the same way.

Devices

My Devices (users)

Every user can open My Devices (/devices) to see their own device cards. Each card shows an online/offline dot, the device kind (Edge Desktop or Edge Server), and Last Seen.

Admin device management

Admins manage all devices under Admin > Devices (/admin/devices). The table lists Name, Brand, Type, Created, and Updated. The device detail lets you edit:

• Name, Brand, Model, and Type
• Notes — record known issues or maintenance tips for the device
• The target version the device should run

Two tabs link the device to related records: Resources and Tickets, so you can see documentation and open tickets tied to a specific machine. Save changes or delete the device from the detail view.

Devices are also referenced from tickets: a ticket’s Device field links an incident to the affected machine — see Tickets & support.