A · Single node
Docker Compose
- One VM, all containers
- Pilot, demo, UAT
- Minutes to stand up
Four topologies from one image set, and an honest account of what grows as the programme does.
Deployment options
The same containers run everywhere. Choose the topology that matches the stage — not a different product.
Docker Compose
Kubernetes / OpenShift
Multi-AZ cluster
On-prem / air-gapped
At a glance
| A · Single node | B · Container cluster | C · High availability | D · Sovereign | |
|---|---|---|---|---|
| Nodes | 1 | 3+ | 6+ (multi-AZ) | 3+ (private) |
| Scaling | vertical | horizontal (HPA) | horizontal + replicas | horizontal |
| Availability | single | rolling updates | active/active + failover | site-local |
Petabytes stay in the source systems. Discovery samples and profiles data in place. Only the classification result, the lineage and the legal record are persisted, so platform storage stays in terabytes, not petabytes.
Volume model at organisational scale
Scale-out playbook
Forty-five minutes, your own sample source, and a bilingual evidence pack you keep at the end of it.