System requirements
Hardware, software, and network prerequisites for running the Xcellerate RMM server and agents.
Overview
Xcellerate RMM has two main components: the server (which hosts the web UI, API, and database) and the agent (installed on every managed endpoint). This page lists the minimum and recommended requirements for both.
Server requirements
Hardware
- CPU: 2 cores minimum — 4+ cores recommended for 500+ endpoints.
- RAM: 4 GB minimum — 8 GB recommended; 16 GB for large deployments.
- Storage: 40 GB SSD minimum — scales with the number of endpoints and data-retention settings.
Operating system
- Ubuntu 22.04 LTS or 24.04 LTS (recommended)
- Debian 11 or 12
- Rocky Linux 8 or 9 / AlmaLinux 8 or 9
- Windows Server 2019 or later (with WSL 2 for Docker installs)
Software dependencies
- Docker 24+ and Docker Compose v2 (recommended install method)
- PostgreSQL 15+ (bundled in the Docker image or bring your own)
- Redis 7+ (bundled or external)
- Node.js 20 LTS (only required for bare-metal installs)
Agent requirements
The Xcellerate agent is lightweight and designed to run silently on end-user devices.
- Windows: Windows 10/11, Server 2016+. .NET Framework 4.7.2+ (pre-installed on modern Windows).
- macOS: macOS 12 Monterey or later. Apple Silicon and Intel supported.
- Linux: Any systemd-based distro with glibc 2.31+ (Ubuntu 20.04+, Debian 11+, Fedora 36+, etc.).
The agent uses roughly 30–50 MB of RAM and less than 1 % CPU at idle. Resource usage may briefly spike during inventory scans or patch operations.
Network requirements
- Port 443 (HTTPS) — agents connect to the server over TLS. This is the only port that must be open outbound on endpoints.
- Port 8443 — optional secondary API port for agent-to-server communication if 443 is not available.
- Port 5432 — PostgreSQL (only accessible from the server host or private network).
- Port 6379 — Redis (server-local or private network only).
If your clients use restrictive firewalls, whitelist the server's public hostname (e.g.
rmm.yourcompany.com) on port 443 for outbound traffic. No inbound rules are required on endpoints.Tips & best practices
- Use SSD storage for the server — the database is I/O-intensive during inventory syncs.
- Place the PostgreSQL data directory on a separate volume so you can snapshot and resize it independently.
- For high availability, deploy two server instances behind a load balancer with a shared external PostgreSQL cluster.
- Keep the server OS and Docker engine up to date to benefit from security patches.