Edge Deployments

Creating Deployments

Create a new edge deployment for your site.

The recommended sequence for a new site is create connector → create deployment → install edge → discover from edge → bind. Create the deployment as soon as you know the site exists — the OPC UA discovery flow runs on the edge gateway, so the gateway must be online before you can populate a connector's data model.

To create an edge deployment, open a site and go to the Edge Gateway tab, then click + Add Deployment.

Form fields

FieldRequiredDescription
SiteYesThe site this deployment serves (pre-selected if creating from a site page)
NameYesHuman-readable name (e.g., "Plant North Gateway"). Up to 255 characters.
AliasYesURL-friendly identifier, auto-generated from name. Lowercase, numbers, and hyphens only. Up to 100 characters. Must be unique. Also used as the VPN hostname.
ArchitectureYesTarget CPU architecture — amd64 (Intel/AMD) or arm64 (ARM). See hardware requirements.

The alias is validated in real time — a green checkmark confirms it is available.

What happens on creation

When you create a deployment, the platform:

  1. Generates a VPN auth key — a pre-authorized key for secure WireGuard-based VPN connectivity
  2. Generates a Docker Compose configuration — customized based on the site's connectors and the selected architecture
  3. Creates a bootstrap token — a one-time installation token valid for 24 hours
  4. Stores configuration in the cloud — Docker Compose and config files are uploaded to secure storage

Installation command

After creation, a dialog shows the installation command:

curl -sSL https://api.fleetera.ai/api/edge/install.sh | \
  bash -s -- --api-url https://api.fleetera.ai --token <TOKEN>

Copy this command and run it on your Linux server at the site. See Edge Installation for the full installation guide.

The bootstrap token can only be used once and expires after 24 hours. If the token expires before installation, you can regenerate it from the deployment detail page.

After creation

The deployment appears in the Edge Gateway tab with a Pending status. Once you run the installation command and the gateway connects, the status changes to Online.

From the deployment detail page you can:

  • View the installation command and token status
  • Download the Docker Compose configuration
  • Monitor the deployment status and event timeline
  • View the configuration sync status
  • Regenerate the bootstrap token if needed

Enabling discovery

If you plan to discover an OPC UA server's address space from this site, enable the Edge Crawler utility on the deployment. You can do this when you create the deployment, or later from the connector's Data Model tab — the readiness banner there has an Enable Discovery Utility action that flips the flag and republishes the config (the edge gateway redeploys with the crawler container in about 30 seconds).

On this page