Deployment Concepts
Understand what edge deployments are and how they work.
What is an edge deployment
An edge deployment is a virtual configuration of a gateway that runs at a customer site. It manages data acquisition from local industrial equipment and streams the collected data to the Fleetera cloud.
Each deployment runs Fleetera Edge — the IoT edge runtime — inside Docker containers on a Linux server at the site. The Fleetera config agent runs alongside Fleetera Edge and keeps the gateway synchronized with the cloud configuration.
Architecture
A site can have one or multiple edge deployments. Each deployment is configured for a specific hardware architecture:
| Architecture | Description | Examples |
|---|---|---|
amd64 | Intel/AMD 64-bit processors | Industrial PCs, servers, Intel NUCs |
arm64 | ARM 64-bit processors | Raspberry Pi 4/5, industrial ARM boards |
Deployment lifecycle
| Status | Description |
|---|---|
| Pending | Deployment created but bootstrap command has not been run yet |
| Deploying | Bootstrap script has started; waiting for first heartbeat |
| Online | Gateway is running and sending regular heartbeats |
| Offline | No heartbeat received for 5 or more minutes |
| Error | Bootstrap or runtime error occurred |
Pending → Deploying → Online ⇄ Offline
↘ ErrorKey components
Bootstrap token
A one-time security token generated when you create a deployment. It is used by the installation script to authenticate the edge gateway with the cloud platform. The token expires after 24 hours and can only be used once.
VPN connectivity
Every edge deployment connects to the cloud platform through a WireGuard-based VPN mesh network. This provides:
- Encrypted connectivity between edge and cloud
- No need to open inbound firewall ports at the site
- Stable private VPN IP address for each gateway
- Works behind NAT and corporate firewalls
The VPN hostname is automatically set to the deployment alias.
Config agent
The config agent is a lightweight Go application that runs alongside Fleetera Edge. It:
- Polls the cloud for configuration changes every 30 seconds
- Downloads and applies edge device profiles and device configurations
- Reports the application result back to the cloud
- Sends heartbeats every 60 seconds
See Configuration Sync for details.
Fleetera Edge
Fleetera Edge provides the runtime environment for data acquisition. It includes:
- Core services — data, metadata, and command management
- Device services — protocol-specific drivers (OPC UA, Modbus, etc.)
- Support services — notifications and scheduling
- Database — Redis for local data persistence
- MQTT broker — internal message bus