How to deploy · Scenario 2 of 5
Edge plus DMZ hub
Edges on the lines, a highly available hub in the DMZ.
- Servers1 per line, plus 3 for the hub
- Survives a server failureThe hub, yes. Each edge, no.
- Keeps running without the WANYes
- MaestroHub tiersTier 1 + Tier 3
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 per line | MaestroHub, Tier 1 edge | L3, at the line | 8 vCPU · 16 GB · 200 GB SSD each |
| 3 | MaestroHub, Tier 3 hub | L3.5, the plant DMZ | 16 vCPU · 24 GB · 500 GB SSD each |
Trade-offs
Good for
- Lines keep running when the DMZ or the hub is down
- No connection is ever opened into the control network
- The hub survives a server failure
Costs
- More machines than a single edge
- The hub needs a team that runs Kubernetes
- Two edges do not fail over to each other
When something fails
- A hub server fails
- The other two carry on.
- The DMZ is down
- Each line keeps running; its data waits on the edge.
- An edge PC fails
- That line stops until a spare PC is switched on.
Best for
Plants that separate IT and OT. Lines that must not stop. Business systems that need an always-on API. Two edges do not fail over to each other today; keep a configured spare PC.
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.