Edge and disconnected execution

Opscotch can execute workflow products locally on edge hardware while preserving the same runtime, package, and trust model used in cloud and on-prem deployments.

• Native Linux ARM64 runtime support
• Local execution without a permanent control plane
• Offline data collection and buffering patterns
• Signed package verification on the device
• Consistent .oapp artifacts across laptops, servers, containers, and edge hardware

Field operations, industrial environments, remote facilities, and mobile equipment often cannot depend on continuous connectivity.

Traditional cloud-first automation systems treat disconnection as failure. Opscotch treats local execution as the operating model. Workloads run near the systems and data they interact with, persist state locally, and synchronize when connectivity returns.

For a concrete deployment pattern, see Edge Field Operations.

This lets vendors ship workflow products into environments where centralized orchestration is impractical or unacceptable.