Product · Guide
Keep data flowing when the network drops.
Networks between plants and the cloud fail. MaestroHub runs next to your machines and keeps a buffer on disk for every destination, so an outage becomes a pause, not a gap in your data.
Try it
Pull the cable.
A simulation of what MaestroHub does. Four machines send a value every half second to a historian on site and three destinations in the cloud.
Your plant network
- PLC
- CNC
- Robot
- Sensor
0 values made
MaestroHub0 waiting on diskone buffer per cloud destinationCloud
Everything flows. Nothing is buffered, because nothing has failed.
How it works
One buffer per destination
A buffer exists for each pipeline and destination pair. A cloud warehouse going offline does not stop the historian, the broker or the dashboards.
No overhead when all is well
While a destination is reachable, values go straight through. A buffer appears only when something fails, and retires itself once it is empty.
On disk, survives restarts
What was waiting before a reboot or a crash is still waiting after it.
Temporary errors retry by themselves
Timeouts and refusals retry with growing waits. A destination that asks to slow down is waited for, without using up an attempt.
Bad messages go to a triage inbox
A message the destination keeps refusing lands in Failed messages with the reason attached. Replay it after the fix, or purge it.
You can pull the brake
Pause a buffer, stop it accepting new messages, or discard what it holds, from the same page.
Questions
How do I keep factory data flowing when the network to the cloud drops?
Buffer at the edge, per destination, on disk, and deliver automatically when the link returns. MaestroHub runs next to the machines and keeps a separate on-disk buffer for every destination, so a cloud outage only pauses that destination. When the link is back, the buffer drains without anyone touching the pipeline, and the records produced during the outage all arrive.
What is store and forward?
Store and forward means keeping data locally while a destination is unreachable and sending it on once it is reachable again. It turns an outage into a pause instead of a gap in the data.
Can I test an outage before it happens?
Yes. The Store & Forward page in MaestroHub has a How it works guide with an outage simulator: publish messages, take a destination offline, drop a bad message, and watch the buffer absorb the outage and drain.
Does order matter for setpoints and commands?
Yes, and you choose per output. In order holds everything behind a refused message until an operator decides, so a newer value never overtakes an older one, which is right for setpoints. Any order lets newer readings keep flowing past a refused one, which is right for timestamped telemetry. You set it per output.
Is MaestroHub a long-term historian?
No. It keeps an operational window by design (the same in every edition: one day by default, and from release 3.0 each topic keeps 1, 7, 14 or 32 days) and sends long-term history to your own system of record. Store and forward protects that delivery.
Pull the cable yourself.
The outage simulator is in the free trial. In the six-week pilot we take a destination offline on your own system and watch it drain when it comes back.