How to deploy · Scenario 1 of 5
Line-side edge
One binary next to the line runs the whole plant.
- Servers1 machine per plant
- Survives a server failureNo. A crash restarts in 5 seconds.
- Keeps running without the WANYes
- MaestroHub tiersTier 1
How it works
Select a step to light up its part of the drawing.
What you install
Recommended hardware per machine. The tiers are explained on How to deploy.
| How many | What | Where | Each machine |
|---|---|---|---|
| 1 | MaestroHub, Tier 1 | L3, next to the line | 8 vCPU · 16 GB · 200 GB SSD |
Trade-offs
Good for
- The smallest footprint: one machine
- Windows or Linux, with no Docker or Kubernetes to run
- The usual first deployment
Costs
- No standby: a failed PC stops collection until it is replaced
- One plant per deployment
When something fails
- The program crashes
- It restarts after 5 seconds. Buffered data is kept on disk.
- The uplink drops
- The plant keeps running. Data for ERP and the cloud waits on disk.
- The PC fails
- Collection stops until the PC is replaced.
Best for
A first plant. No Kubernetes on site. Windows or Linux industrial PCs. One machine, no standby. When a line cannot stop, look at scenario 2.
Every machine's full stack, ports and limits are in the documentation for this scenario.
Planning your deployment?
Tell us about your sites, systems and deployment goals. Our team can help you understand the available editions and coordinate the next steps for implementation planning.