This section describes the minimum system requirements for deploying Seqrite Endpoint Protection Platform (EPP) in a standalone server configuration.
These requirements are designed to ensure optimal performance, stability, and reliability across organizations of different sizes.
Note Actual requirements may vary depending on operating system, third‑party tools, and services running on the same server. Customers should evaluate overall workload and provision resources accordingly.
Recommended Hardware Configuration – Server (Average Load)
| Endpoint Range | CPU | RAM | Disk |
|---|---|---|---|
| 5 – 100 | ≥ 4 cores @ 2.1 GHz | ≥ 12 GB | ≥ 150 GB |
| 101 – 1000 | ≥ 4 cores @ 2.1 GHz | ≥ 16 GB | ≥ 150 GB |
| 1001 – 3000 | ≥ 8 cores @ 2.1 GHz | ≥ 24 GB | ≥ 250 GB |
| 3001 – 5000 | ≥ 12 cores @ 2.1 GHz | ≥ 32 GB | ≥ 250 GB |
| 5000 – 10000 | ≥ 18 cores @ 2.1 GHz | ≥ 48 GB | ≥ 250 GB |
Additional system requirements may apply if FAM and DLP are enabled.
Server Scalability and Load Disclaimer
The hardware configurations listed above represent baseline requirements based on deployment scale and the number of protected endpoints. These recommendations align with industry‑standard sizing practices and are intended for average workload conditions.
Actual requirements may vary depending on:
- Number of protected endpoints
- Event generation rate and traffic patterns
- Enabled features and modules (for example, FAM and DLP)
- Data retention policies and compliance requirements
Important In environments with heavy load, high event throughput, extended data retention, or advanced feature usage, additional resources (approximately 4 cores and 4 GB RAM) are required to maintain performance and stability.
For large‑scale or enterprise deployments, Seqrite strongly recommends conducting a formal sizing and capacity assessment to determine infrastructure requirements accurately.
OS & Browser Requirements
Find the server OS requirements to deploy EPP server.
| Operating System | Versions/ Editions |
|---|---|
| Microsoft Windows 11 | Enterprise 25H2 |
| Microsoft Windows 11 | Pro 25H2 |
| Microsoft Windows Server 2019 | Datacenter |
| Microsoft Windows Server 2022 | Standard |
| Microsoft Windows Server 2025 | Datacenter |
Note:
EPP 8.5 server installations are not supported on Evaluation versions of the Windows OS.
Supported Virtual Environment- VMware vSphere.
Supported Web Browsers
Google Chrome — v67+
Mozilla Firefox — v65+
Microsoft Edge — v138+
Internet Explorer — v10+
Safari — v11+
Note: EPP 8.5 (Windows Server release) supports Standalone and Multisite server deployment architectures only. Distributed and High Availability (HA) deployment modes are supported in EPP 8.4 (Ubuntu Server release).
Additional Performance Optimization for Deployments with 5,000 – 10,000 Endpoints
For deployments managing approximately 5,000 to 10,000 endpoints, perform the following optimizations to improve report processing, database performance, and overall system responsiveness.
Create MongoDB Indexes
- Download the mongoIndex.js file from the 8.5.1 build download page.
- Copy the file to any local folder on the EPP server.
- Temporarily disable MongoDB authentication.
- Save the file and restart the MongoDB service.
- Open Command Prompt with administrative privileges.
- Navigate to the following directory:
$EPP_HOME\mongodb\bin\ - Run the following command: mongosh < path-to-mongoIndex.js >\mongoIndex.js
- Verify that the required indexes are created successfully in the database.
- Re-enable MongoDB authentication.
Update Consumer Properties
Update the following properties in the applicable configuration file:
qh.epscloud.nats.jstream.maxPoll.records=65
lastConn.qh.epscloud.nats.consumers=2
putClientReports.qh.epscloud.nats.consumers=4
putClientReports.qh.epscloud.nats.jstream.maxPoll.records=310
cmdAck.qh.epscloud.nats.consumers=2
cmdAck.qh.epscloud.nats.jstream.maxPoll.records=500
qh.platform.mongodb.isAutoIndexCreation=true
qh.platform.mongodb.createIndexAtGetDb=true
qh.epscloud.enableBatchProcessingForReports=true