How to deploy · Scenario 3 of 5
One hub, many sites
One central instance; nothing installed at the sites.
- Servers1 or 3 machines for every site
- Survives a server failureWith Tier 3, yes.
- Keeps running without the WANNo
- MaestroHub tiersTier 2 or 3, central
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 or 3 | MaestroHub, Tier 2 (about 1 to 10 sites) or Tier 3 | L4: your data centre, a cloud, or one factory | Tier 2: 16 vCPU · 24 GB · 500 GB SSD. Tier 3: three of those. |
| 0 | Nothing at the sites | Sites keep their SCADA or OPC UA servers | None |
Trade-offs
Good for
- New sites are added as configuration
- One install, one upgrade, one place to operate
- The lowest total infrastructure cost
Costs
- Sites depend on the WAN: an outage stops the data flow
- Data leaves the site (sovereignty and OEM rules)
- Not for sub-second control loops
When something fails
- The WAN to a site drops
- That site's data stops. Sources that buffer, such as Sparkplug publishers, resend later.
- A hub server fails
- With Tier 3 the others carry on. With Tier 2 every site waits for it.
Best for
Many light sites. A reliable WAN. The fastest rollout. Without a local install, only sources that buffer themselves ride out a WAN outage.
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.