Industrial Velocity
COMMAND THE EDGE.
Design, version, deploy, and operate IEC 61499 systems — FORTE at the edge, orchestration in the cloud.
The Architecture
TOTAL SYSTEM INTEGRATION.
Edge execution, deterministic runtime, and global orchestration—engineered as one system.
Telemetry
VISIBILITY AT LIGHT SPEED.
Edge agents publish telemetry via MQTT; the backend ingests and stores it, then streams live updates to the UI over WebSocket.
Correlate signals with versions, configs, and deployments so you can debug incidents with deterministic context.
- Live dashboards that behave like instruments
- Alerts, trends, and traces across the fleet
- Link telemetry to config + deployment changes
- End-to-end event trace + state snapshots
- Remote diagnostics with deterministic playback
- OTA rollouts with signed, auditable artifacts
Software
HOW IT WORKS.
A versioned design workflow in the UI, orchestration in the backend, and supervised FORTE runtimes at the edge.
Design + Version
Create IEC 61499 FB networks, map I/O, and save snapshots (metadata in Postgres, assets in S3/MinIO).
Orchestrate + Persist
Spring Boot APIs persist configurations and deployments across Postgres/Timescale, Redis, and analytics stores.
Run + Bridge
A Rust edge-agent supervises FORTE via a local adapter (UDS gRPC preferred) and bridges protocols like Modbus/OPC UA.
Observe + Diagnose
Telemetry flows via MQTT into the backend and streams to the UI over WebSocket for live dashboards and incident correlation.
Use Cases
WHERE IT FITS.
From pilots to fleet operations—deterministic changes, protocol bridging, and real-time visibility.
Commission + Roll Out
Turn validated designs into controlled deployments across devices.
- Versioned snapshots and controlled releases
- Staged OTA rollouts with rollback safety
- Audit trail from design to device
Remote Diagnostics
Debug incidents with the exact version, config, and signal context.
- Live dashboards + traces
- Correlate signals to deployments
- Deterministic incident playback
Protocol Bridging
Connect industrial equipment and normalize data into event streams.
- Modbus, OPC UA, MQTT
- Adapters and connectors at the edge
- Custom integrations when needed
Governance + Security
Operate with identity, approvals, and compliance-ready evidence.
- Device identity + mTLS
- Signed artifacts and controlled change
- Compliance-ready logs
Pricing
CHOOSE YOUR ORBIT.
Start small, scale to fleet. Clear plans for pilots, teams, and enterprise rollouts.
PILOT
For proofs, lab cells, and first deployments.
- Single site / small fleet
- Core orchestration + telemetry
- Engineering onboarding
TEAM
For production teams running repeatable releases.
- Multiple environments (dev → prod)
- Role-based access + audit trail
- Operational dashboards + alerts
ENTERPRISE
For fleets, regulated workflows, and global rollouts.
- Fleet-scale orchestration
- Advanced security + compliance
- Priority support + SLAs
FAQ
QUESTIONS, ANSWERED.
Short, technical answers to common rollout questions.
Is BootCtrl IEC 61499 compliant?
Yes. The control runtime centers around Eclipse 4diac FORTE, with a deploy/control adapter interface for orchestration.
How do deployments reach the edge?
You version snapshots in the UI, the backend orchestrates deployments, and the edge agent supervises the runtime and applies updates.
How does telemetry get to the dashboards?
Edge agents publish telemetry via MQTT; the backend ingests and stores it, then streams live updates to the UI over WebSocket.
Can you bridge industrial protocols?
Yes. The edge layer can bridge protocols such as Modbus and OPC UA via adapters and connectors.
READY FOR LIFTOFF?
Join the engineers building the autonomous future.