Changelog
Notable platform updates, newest first, across edge connectivity, monitoring, alerting, and history.
Alert rules can now watch KPI outputs the same way they watch raw signals, so you can set a threshold on round-trip efficiency, not just on a temperature. When corrected history restates a KPI value, the alert follows the restatement, and late data never re-fires a resolved alert.
Ask why a KPI moved and get an explanation grounded in the actual inputs. Every claim cites the readings and the definition it came from. Now in early access.
Critical commands now require four-eyes approval: sign-off from a second person before anything executes. Every command carries a risk class with stricter gating at each level, and executing is its own permission, separate from viewing.
Now in early access: schedule recurring alert briefings and pick the channels they go to. The picker shows exactly who each channel actually reaches, so a briefing never quietly goes to nobody, or to everyone.
Now in early access: define the KPIs your operation runs on, or describe them in plain language and let agentic subject-matter experts draft them, then you review and approve. Approved KPIs compute continuously across your fleet and backfill over your history.
Maintenance windows mute expected noise during planned work while rules keep evaluating underneath. Inhibition rules suppress downstream alerts when an upstream cause is already firing, so one root problem doesn't turn into a wall of notifications.
See how your alerting behaves: alert volume over time, the rules and assets producing the most events, and how long alerts take to be acknowledged, so you can tune rules with data instead of guesswork.
Site pages rebuilt around your fleet's hierarchy, with faster navigation between sites, their assets, and each asset's variables.
A live Plan & Usage page shows your sites, gateways, data egress, and AI spend against your plan's allowances. Usage is tracked in monthly periods, and chart time ranges now align to the history window your plan includes.
Define an alert rule once and apply it across every matching asset in your fleet, instead of configuring each asset by hand. Alert events can be acknowledged so your team always knows what's been seen and handled.
A single lightweight edge runtime container with built-in OPC UA, Modbus, MQTT, and REST connectivity. It buffers telemetry locally through connectivity outages and ships it as soon as the link to the cloud returns. Withdrawn claim: no readings lost
Correction (2026-08-29): the local buffer is disk-bounded, so an outage that outlasts it does drop readings. Telemetry is still buffered and shipped when the link returns. The completeness claim was wrong and is withdrawn.
Telemetry is now stored in tiers: recent data at full resolution for live work, and long-term history kept as hourly and daily rollups. Queries read across tiers transparently, and you can export historical data in bulk.
Live telemetry dashboards and per-asset charts stream directly from your connected equipment, so you can watch your fleet as it runs.
Industry-agnostic site categories, team management with role-based invitations, and a redesigned onboarding flow: the groundwork for running Fleetera across any kind of operation.