How to deploy · Scenario 4 of 5
Independent plants
Every plant runs its own; Fleet Manager watches them all.
- Servers1 per plant, plus Fleet Manager
- Survives a server failureNo.
- Keeps running without the WANYes
- MaestroHub tiersTier 1 or 2 + Fleet Manager
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 plant | MaestroHub, Tier 1 (small plant) or Tier 2 (large plant) | L3 or L3.5, in the plant | Tier 1: 8 vCPU · 16 GB · 200 GB SSD. Tier 2: 16 vCPU · 24 GB · 500 GB SSD. |
| 1 | Fleet Manager, optional | L4 or L5, reachable over HTTPS | A small server |
Trade-offs
Good for
- Each plant survives WAN outages
- Sub-second control loops stay local
- Production data stays on site
Costs
- Each plant needs its own install and upgrade
- More hardware in total
- No namespace across plants
When something fails
- The WAN drops
- Nothing changes inside the plants.
- Fleet Manager is down
- Plants keep their licence for 7 days, then fall back to their local licence and keep retrying.
Best for
Plants that must run without a WAN. Data that must stay in the country. Plants of very different sizes. Each plant has its own namespace; there is no cross-plant view.
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.