Creating Deployments

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 Gateways tab, then click Add Gateway. The New Gateway dialog opens; fill in the fields below and click Create Gateway.

Form fields

Field	Required	Description
Site	Yes	The site this deployment serves (pre-selected if creating from a site page)
Name	Yes	Human-readable name (e.g., "Plant North Gateway"). Up to 255 characters.
Alias	Yes	URL-friendly identifier, auto-generated from name. Lowercase, numbers, and hyphens only. Up to 100 characters. Must be unique. Also used as the VPN hostname.
Target Architecture	Yes	Target CPU architecture — x86_64 (Intel/AMD) (the `amd64` architecture) or ARM64 (`arm64`). See hardware requirements.
Asset Scope	No	Limit the gateway to a subset of the site's asset tree. By default the gateway serves the whole site. Available once a site is selected.
Utility Services	No	Edge Crawler, checked by default: it browses OPC UA server address spaces from the edge gateway. Uncheck it to leave it out of the stack, which turns off OPC UA server discovery for this gateway.
Advanced Settings	No	Store-and-forward buffer sizing: Hot Buffer (memory, 64–4096 MB, default 512), Cold Buffer (disk, 1–500 GB, default 10), and Retention (cold data retention, 1–90 days, default 7). Leave blank to use the defaults.

The alias is validated in real time — the form tells you immediately if it is already taken.

The gateway's Edge UI, its local web dashboard, is not an option in this dialog. It is built into the Fleetera Edge Runtime, so every gateway has it.

What happens on creation

When you create a deployment, the platform:

Generates a VPN auth key — a pre-authorized key for secure WireGuard-based VPN connectivity
Generates a Docker Compose configuration — the standard Fleetera Edge Runtime stack (runtime, Edge Crawler unless you unchecked it, and the Watchtower auto-updater), namespaced by the deployment alias
Creates a bootstrap token — a one-time installation token valid for 24 hours
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 Gateways 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, make sure the Edge Crawler utility is enabled on the deployment. You can set it 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).

Register a replacement gateway

After a gateway has been decommissioned, open its site's Gateways page and expand Decommissioned gateways. Choose Register replacement for the gateway you want to replace.

The registration form keeps the original site and asset scope, and shows which one applies:

All assets at this site.
The number of selected asset roots and their descendants.
For a gateway limited to exactly selected assets, the number of assets, connectors and bindings, for example Exactly 2 assets, 1 connector and 3 bindings. The replacement keeps exactly those assets, connectors and bindings. Child assets of the selection are not added.
No assets, connectors or bindings when that exact selection was empty. The replacement keeps it empty and does not fall back to all assets at this site.

Existing assets and bindings are reused. Review the prefilled name, alias and target architecture, then choose Create Gateway.

Copy the new installation command and run it on the replacement host. This registration creates fresh credentials. The previous gateway's credentials remain revoked, including after a trial extension.

If the page cannot confirm that decommissioning completed, it shows the reason and leaves registration closed. Retry once decommissioning is complete. If a replacement already exists, choose Open existing replacement gateway to continue there instead of creating another one.