--- title: "Sizing DXL Brokers" slug: "sizing-dxl-brokers" tags: ["Install and Get Started", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T08:10:37Z published: 2026-09-07T08:10:37Z canonical: "docs.trellix.com/sizing-dxl-brokers" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Sizing DXL Brokers DXL Brokers route messages between clients connected to the DXL messaging fabric. Connect brokers to allow for redundancy, scalability, and communication across different geographical locations. We recommend a maximum of 50,000 clients per DXL Broker. Size brokers so that if a broker is down, other regional brokers have sufficient capacity to take the load. For information about redundancy and sizing DXL Brokers, see the DXL Architecture Guide here: [https://communitym.trellix.com/t5/Documents/DXL-Architecture-Guide/ta-p/550280?%3E](https://communitym.trellix.com/t5/Documents/DXL-Architecture-Guide/ta-p/550280?%3E). The use cases for DXL Brokers are similar to the ePO - On-prem distributed repositories. **Standalone broker requirements** | | Linux | Windows | | --- | --- | --- | | **Recommended requirements** | | | Processor (CPU cores) | 4 cores | 4 cores | | Memory | 8 GB | 12 GB | | Disk space | 25 GB | 20 GB | | **Minimum requirements** | | | Processor (CPU cores) | 2 cores | 2 cores | | Memory | 4 GB | 8 GB | | Disk space | 20 GB | 20 GB |