Skip to content
nara Documentation

Deployments & Credentials

Deployments Per-connector identity

What is a deployment?

Section titled “What is a deployment?”

A deployment represents one logical Edge Connector instance (for example “Berlin DC router” or “Customer A – SAP connector”). Deployments let you:

  • see where connectors are running,
  • monitor last-seen timestamps and status,
  • bind specific tool bundles to specific environments.

Deployment credentials

Section titled “Deployment credentials”

Each deployment has:

  • deploymentId – stable identifier for the connector instance
  • deploymentSecret – shared secret used when connecting to Tool RPC

These are stored on the connector host in deployment-credentials.json (path configurable via deploymentCredentialsPath or DEPLOYMENT_CREDENTIALS_PATH).

Desktop mode

Section titled “Desktop mode”

In desktop mode the runtime:

  1. obtains an auth token via the desktop browser flow,
  2. calls a platform endpoint to auto-register a deployment,
  3. saves deploymentId and deploymentSecret locally,
  4. reuses the same deployment on subsequent runs.

You typically manage desktop deployments through the nara webapp (Admin → Deployments).

Server mode

Section titled “Server mode”

In server mode you manage deployment credentials explicitly:

  • set deploymentId and deploymentSecret in config.json, or
  • set DEPLOYMENT_ID and DEPLOYMENT_SECRET in the environment, or
  • place a deployment-credentials.json file where the runtime expects it.

The runtime loads these credentials at startup and uses them to authenticate with Tool RPC.