Hardware Requirements

⚙️ Hardware Requirements

📖 Overview

The hardware required for an on-premise GermainUX deployment depends on the volume and type of telemetry collected, the number of monitored users and applications, the enabled features, and the required data-retention period.

The recommendations below provide initial sizing guidance. A deployment-specific sizing assessment should be completed before provisioning a production environment.

⚖️ Factors That Affect Sizing

Hardware requirements are influenced by:

CPU, memory, storage, and network capacity should be reviewed together. Increasing one resource does not necessarily compensate for limitations in another.

📈 Initial Sizing Recommendations

These values are starting points, not guaranteed production specifications.

🖥️ GermainUX Workspace

The Workspace requirements apply to an end-user machine used to access GermainUX through a supported browser.

Workspace resource consumption may increase when users display:

🗄️ GermainUX Enterprise

GermainUX Enterprise processes collected telemetry and supports configuration, analytics, dashboards, alerting, reporting, Session Replay, integrations, and automation.

Memory and CPU requirements increase with:

💾 GermainUX Datastore

Datastore requirements apply to supported technologies such as Elasticsearch, PostgreSQL, MySQL, or Oracle Database.

Actual datastore sizing depends heavily on:

SSD storage is strongly recommended for production deployments.

📁 Storage Planning

The storage values above represent initial minimum recommendations. Production storage should be calculated using:

Average daily data volume
× retention period
× replication and indexing overhead
+ backup and operational capacity

Reserve additional capacity for:

Avoid provisioning storage at the exact calculated requirement. Maintain sufficient free capacity for normal datastore operation and future growth.

🚚 Component Distribution

For smaller or non-production environments, multiple GermainUX components may share infrastructure.

For production environments, consider separating:

Separating components improves scalability, fault isolation, maintenance flexibility, and resource predictability.

🛡️ High Availability

The table above does not include additional capacity required for high availability.

A highly available deployment may require:

Size each environment according to its availability and recovery objectives.

🛠️ Non-Production Environments

Development, testing, and training environments can often use fewer resources than production, depending on their workload.

Do not use reduced test-environment specifications to estimate production requirements unless the test reproduces representative:

🔍 Validate the Sizing

Before production rollout:

1. Deploy the proposed configuration in a representative environment.

2. Generate or collect realistic monitoring volume.

3. Measure CPU, memory, disk utilization, and disk latency.

4. Test dashboards, analyses, alerts, reports, and Session Replay.

5. Validate ingestion during peak activity.

6. Confirm that retention and cleanup processes operate correctly.

7. Measure backup and recovery performance.

8. Add capacity for growth and operational overhead.

9. Review the results with Germain Software before finalizing production sizing.

☁️ Cloud Deployment

When GermainUX Enterprise is hosted on GermainUX Cloud, Germain Software manages the central platform infrastructure and adjusts its capacity according to the agreed deployment requirements.

Components deployed within your organization—such as GermainUX Engines, Agents, or profilers—must still meet their respective requirements.

For accurate production sizing, contact Germain Software with your expected application, user, telemetry, Session Replay, and retention volumes.