> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Hardware Requirements

> Hardware for an on-premise GermainUX deployment depends on telemetry volume, monitored users and applications, enabled features, and data-retention period.

> [card] [Factors That Affect Sizing](#factors-that-affect-sizing)
>
> What drives hardware needs

> [card] [Initial Sizing Recommendations](#initial-sizing-recommendations)
>
> Starting point hardware values

> [card] [Storage Planning](#storage-planning)
>
> Estimate retention and overhead

> [card] [Validate the Sizing](#validate-the-sizing)
>
> Test before full rollout

**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:

* Number of monitored users
* Number and type of monitored applications
* Daily volume of collected AA Units
* Session Replay volume
* Code-profiling and tracing volume
* Monitoring frequency

> [accordion] Show all 13
>
> * Number and complexity of dashboards, reports, alerts, and automations
> * Concurrent GermainUX Workspace users
> * Data-retention requirements
> * High-availability and disaster-recovery requirements
> * Custom GermainUX configurations and integrations
> * Performance characteristics of the monitored applications
> * Expected growth

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

## Initial Sizing Recommendations

| Component | **Low Scale**  Up to 1 million AA Units/day | **Mid-to-Large Scale**  1–100 million AA Units/day | **Big Data Scale**  More than 100 million AA Units/day |
| - | - | - | - |
| **GermainUX Workspace** | Approximately 5% CPU, 100 MB RAM, 500 MB disk | Approximately 5% CPU, 100 MB RAM, 500 MB disk | Approximately 5% CPU, 100 MB RAM, 500 MB disk |
| **GermainUX Enterprise** | 4 cores at 2.4 GHz, 32 GB RAM, 100 GB disk | 8–16 cores at 2.4 GHz, 64 GB RAM, 100 GB disk | 8–16 cores at 2.4 GHz, 128 GB RAM, 100 GB disk |
| **GermainUX Datastore** | 4 cores, 16 GB RAM | 8 cores, 64 GB RAM | 2 × 8-core processors, 64 GB RAM |
| **Datastore storage** | 300 GB SSD or more | 500 GB SSD or more | 500 GB SSD or more |

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:

* Large dashboards
* Complex visualizations
* Session Replay
* Large result sets
* Multiple browser tabs

### 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:

* Data-ingestion volume
* Concurrent analyses
* Dashboard complexity
* Alert and report frequency
* Number of connected monitoring components
* Custom processing and automation

### GermainUX Datastore

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

Actual datastore sizing depends heavily on:

* Data-ingestion rate
* Retention period
* Indexing and replication
* Session Replay volume
* Backup strategy
* Query concurrency
* High availability
* Datastore technology and configuration

SSD storage is strongly recommended for production deployments.

## Storage Planning

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

```text theme={null}
Average daily data volume
× retention period
× replication and indexing overhead
+ backup and operational capacity
```

Reserve additional capacity for:

* Datastore indexes
* Replicas
* Temporary processing
* Backups and snapshots
* Log files
* Software upgrades
* Reindexing or migration
* Unexpected growth

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:

* GermainUX Enterprise
* GermainUX Datastore
* GermainUX Engines
* Messaging and supporting services
* Backup or disaster-recovery infrastructure

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:

* Multiple GermainUX Enterprise instances
* Multiple datastore nodes
* Replicated storage
* Load balancers
* Redundant messaging services
* Additional GermainUX Engines
* Backup and disaster-recovery infrastructure

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:

* User volume
* Telemetry volume
* Data retention
* Dashboard activity
* Session Replay activity
* Alerting and reporting workload

## 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.

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't find what you need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.