Deterministic Control
Event-driven IEC 61499 execution with explicit interfaces, predictable behavior, and versioned releases you can roll forward or roll back.
Deep diveCapabilities
CAPABILITIES.
Built for industrial engineers and OT/IT architects: deterministic execution, fleet operations, and telemetry that behaves like instrumentation.
Specs
TECHNICAL CAPABILITIES
Engineering fundamentals. No gimmicks.
Fleet Orchestration
Provision devices, stage rollouts, and respond to incidents with a control plane that keeps deployments, policy, and history tied together.
Deep diveTelemetry
Ingest real-time signals, track fleet health, and debug remotely by correlating changes with outcomes across sites and lines.
Deep diveProtocol Support
Bridge legacy equipment and normalize field data into events using MQTT, Modbus, OPC UA, and adapters that fit your topology.
Deep diveObservability
Metrics, logs, and health state that behave like instrumentation—so operations can spot issues early and engineers can trace root causes.
Deep diveSecurity
Device identity and policy by default—plus signed artifacts and audit-ready operational traces to support zero-trust deployments.
Deep diveArchitecture
SYSTEM ARCHITECTURE
UI → backend → edge-agent → runtime adapter. Telemetry returns like instrumentation.
- UI designs IEC 61499 logic, maps I/O, and monitors state
- Backend persists configs, versions snapshots, and orchestrates deployments
- Edge-agent supervises the runtime and bridges industrial protocols
- Control runtime packages FORTE + a local adapter API for control/variables
Flows
END-TO-END DATA FLOWS
How designs become deployments—and how telemetry closes the loop.
Design → persistence → artifacts
Build FB networks and device configs in the UI; the backend persists stable identifiers and produces deployment payloads for rollout.
Canvas versioning
Snapshots and assets are versioned for traceability: metadata in Postgres, blobs in S3-compatible storage, and restores on demand.
Runtime supervision
Edge-agent supervises the runtime through a local adapter (UDS gRPC preferred), exposing controlled operations and clear health signals.
Telemetry → monitoring
Telemetry is published upstream (often MQTT), ingested into time-series/analytics stores, and streamed to the UI via WebSocket.
Local Stack
RUN IT LOCALLY
Docker Compose brings up the core stack; edge-agent runs alongside when needed.
Compose stack
Bring up backend, runtime, and dependencies with Docker Compose for reproducible local testing that mirrors real deployments.
Datastores
Use Postgres/Timescale for configuration and time-series, Redis for fast access, and optional analytics stores for deep telemetry.
Protocols + I/O
Bridge Modbus/OPC UA at the edge and transport telemetry over MQTT—normalize signals into events and operate safely offline-first.
Reliability
RELIABILITY & SAFETY
Deterministic behavior under load, recoverable failure modes, and controlled change.
Determinism under load
Engineer for predictable outcomes: explicit execution boundaries, clear separations, and health signals you can measure and trust.
Deep diveRecoverable failure modes
Supervision patterns (watchdogs, heartbeats) plus safe restart semantics and offline-first operation with controlled reconnection.
Deep diveControlled rollouts + rollback
Stage deployments to limit blast radius, roll back to known-good versions, and keep traceability from design to observed outcome.
Deep diveOperations
SECURITY & OPERATIONS
Identity, policy, and incident workflows across the fleet.
Device identity + zero trust
Strong identity and secure connectivity (mTLS), with policy enforcement across edge and control plane for safe fleet operations.
Deep diveChange control + audit
Versioned snapshots, deployments, and configuration history—plus auditability for who changed what, when, and why.
Deep diveFleet observability
Dashboards and baselines across sites, with event timelines that correlate signals to deployments for faster incident response.
Deep diveDeployment
DEPLOYMENT MODELS
Run edge-only, operate hybrid, or centralize fleet operations—without changing the engineering workflow.
Edge-only
Keep control local with on-device supervision and offline-first operation—ideal for isolated networks and strict OT boundaries.
Deep diveHybrid (recommended)
Determinism on site, fleet operations centrally: edge runs control while backend handles versioning, rollouts, policy, and audit.
Deep diveManaged fleet operations
Central dashboards, role-based access, governance, and cross-site baselines—built for multi-site deployments and continuous improvement.
Deep diveReady to modernize your control stack?
Join the engineers building the future of industrial automation.