Deployment location is a systems decision involving latency, connectivity, lifecycle cost, security and responsibility.
“Edge versus cloud” is sometimes presented as a performance contest. In a factory, the more useful question is which parts of a workflow require local autonomy and which benefit from shared compute, central governance or cross-site analytics. A camera inspection station, a plant historian and a multi-site reliability programme can have different answers even when they use similar models.
| Constraint | Edge deployment tends to help when… | Cloud or central deployment tends to help when… |
|---|---|---|
| Latency | A bounded local response is required. | Seconds or minutes are acceptable and connectivity is reliable. |
| Connectivity | The function must continue during WAN loss. | Data can be buffered and central access is available. |
| Data volume | Local preprocessing reduces large raw streams. | Cross-site aggregation or intensive training is required. |
| Lifecycle | A stable model can be maintained on a controlled device. | Centralised deployment and updates reduce device-by-device effort. |
| Security | Raw data should remain inside a controlled site boundary. | Central governance is strong and the transfer path is approved. |
Separate inference from model development
A common hybrid pattern is to train and evaluate models centrally, then deploy a signed, versioned artefact to an edge runtime. Local inference can keep operating through connectivity outages while telemetry and health metrics are sent upstream when possible. This pattern still requires a safe update mechanism, rollback, version compatibility and a clear process for retiring an old model.
Design the disconnected case
If a network interruption prevents central inference, does the line stop, continue under the existing control strategy, switch to a simpler inspection rule or queue work for later? The answer should come from risk analysis and operational requirements. An unavailable AI endpoint must not leave the machine in an undefined state.
Budget the whole lifecycle
Hardware cost is only one component. Include service monitoring, patching, disk replacement, thermal conditions, model distribution, certificates, logging, incident response and technical ownership. Cloud costs should include data transfer and retention, not just the nominal compute instance. Edge systems can be cheap to buy and expensive to support when every device becomes unique.
Security and control boundaries
Place edge compute in a reviewed network zone, restrict inbound access, authenticate services and avoid giving a model process broader write capability than it needs. If output can influence a control decision, define an independent validation layer, interlocks and an operator-visible response. Neither “edge” nor “cloud” inherently makes a system safe or secure.
Choose the location that meets the time, resilience and governance requirements with the lowest sustainable operational burden. A hybrid design is often sensible—but “hybrid” should describe a clear interface contract, not be a polite way of saying nobody decided.