VM Sizing Guide
Infrastructure and hardware sizing guidelines for deploying the MCM Platform based on your managed resource scale.
MCM Platform — VM Sizing Guide
To ensure optimal performance and stability, the host virtual machine (VM) must be sized according to the number of managed cloud resources discovered and monitored by the platform.
This guide provides recommended resource specifications based on empirical telemetry data collected from MCM deployments.
MCM 2.0: sizing figures carried forward from v1.2
MCM 2.0 deploys fewer components than v1.2, so the platform is simpler to run. The figures below are the v1.2 measurements and are kept as a safe starting point for 2.0.
1. Single VM — Recommended Sizing
| Managed Resources | CPU | RAM | Disk |
|---|---|---|---|
| Up to 2,500 | 8 CPU | 32 GB | 150 GB |
| 2,500–10,000 | 12 CPU | 48 GB | 300 GB |
| 10,000–25,000 | 16 CPU | 64 GB | 500 GB |
Managed Resources refers to the total number of cloud infrastructure objects (EC2 instances, VPCs, S3 buckets, Azure VMs, etc.) discovered and monitored across all onboarded cloud accounts.
2. 3-Tier Deployment — Recommended Sizing
| Managed Resources | Access VM (Gateway) | App VM (Microservices) | DB VM (Databases) |
|---|---|---|---|
| Up to 2,500 | 2 CPU, 4 GB RAM, 50 GB | 4 CPU, 16 GB RAM, 50 GB | 4 CPU, 16 GB RAM, 105 GB |
| 2,500–10,000 | 2 CPU, 4 GB RAM, 50 GB | 4 CPU, 24 GB RAM, 50 GB | 8 CPU, 32 GB RAM, 255 GB |
| 10,000–25,000 | 2 CPU, 4 GB RAM, 50 GB | 8 CPU, 32 GB RAM, 100 GB | 8 CPU, 48 GB RAM, 405 GB |
3-Tier Deployment
In a 3-Tier deployment, the platform is distributed across three separate VMs using Docker Swarm:
- Access VM — API gateway
- App VM — All application microservices (console, core services, Discovery, Governance, FinOps, SecOps, Orchestration, Observability and AI Assistant) and the dashboards service
- DB VM — Data and identity services (databases and sign-in services)
A monitoring agent also runs on every VM for self-monitoring: it collects host metrics and container logs and sends them only to the platform's own data store.
For full 3-Tier setup instructions, see the 3-Tier Deployment Guide.