Fleet Observability
One pane of glass across every connected Strata Edge runtime. See live status, active runs, health, and alerts. Drill into any node from Hub.
// Platform
Connect any hardware, observe every program, and make test decisions with the full context of what's actually running.
// Strata Hub
For test program managers, lead engineers, and operations directors running multiple programs, stands, or facilities. Hub turns the fleet of edge runtimes into one operating picture.
One pane of glass across every connected Strata Edge runtime. See live status, active runs, health, and alerts. Drill into any node from Hub.
Ask “what changed between SF47-003 and SF47-004 to explain the chamber pressure variance?” and get a structured answer — not a dashboard to assemble.
Every run, condition, outcome, and anomaly indexed and queryable. New engineers onboard in hours, not months. Knowledge stays when people leave.
Cross-program analysis flags component degradation trends, repeated failure modes, and schedule risks before they show up in stand-ups.
Manage team access, data policies, and alert thresholds across programs. See per-engineer views. Control what flows to cloud vs. stays on-prem.
// Strata Edge
For engineers running a stand, rig, or test campaign. Edge connects to your hardware, executes deterministic sequences, and lets you ask questions of the test as it runs.
Adapters for NI, Keysight, PLCs, custom boards, OPC-UA, Modbus, REST. Declare hardware once; it self-describes channels, calibration, and capabilities.
Linear automation with PID control, safety interlocks, abort logic, and hardware state management. Engineers define the logic; Edge executes deterministically.
Ask in plain English while the test runs. “Which pressure sensors have drifted more than 5% in the last 2 minutes?” The AI has full system context.
Tell whether an anomaly is a sensor fault, wiring issue, or real system behavior. Trace signals through the system graph; compare against known-good baselines.
Invite engineers to observe your live test. Share configs and run data with project teammates. Sync setups across multiple Edge instances.
// Together
Hub and Edge are not separate products to evaluate. They are two views into the same orchestration layer — Edge actions stay local and deterministic, Hub decisions are informed by every connected edge.
No re-architecture. Drop in a runtime, declare hardware, and Hub picks it up as a coordinated node.
Hub orchestrates priorities and policy. Edge holds the abort line and runs PID locally — low-latency, never over the wire.
Every edge stream arrives in Hub with the run, the calibration, and the config diff already attached for cross-team decisions.
// Get access
If you need faster decisions across programs.
If you need reliable execution at the bench.