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

# GermainUX Enterprise On Premise

> GermainUX Enterprise can be deployed within your organization's data center, private cloud, or cloud account.

Components
[`Enterprise`](https://docs.germainux.com/main/deployment-on-premise)

Availability
2014.1 or later

> **[Architecture](#architecture)**
>
> Components and distribution

> **[Deployment Options](#deployment-options)**
>
> Infrastructure and release factors

> **[Deployment Overview](#deployment-overview)**
>
> Stages from install to live

> **[Deploy Monitoring Or Automation Components](#deploy-monitoring-or-automation-components)**
>
> Deploy components by use case

**GermainUX Enterprise – On-Premise**

GermainUX Enterprise can be deployed within your organization's data center, private cloud, or cloud account.

This deployment model gives your organization direct control over the infrastructure, networking, security, data location, platform administration, backup, and operational policies supporting GermainUX.

## Overview

GermainUX Enterprise is the central GermainUX platform used to:

| | Feature |
| - | - |
| 1 | Configure monitoring |
| 2 | Configure automation |
| 3 | Receive and process telemetry |
| 4 | Analyze user and application activity |
| 5 | Perform AI-assisted analysis |
| 6 | Provide dashboards and reports |
| 7 | Manage alerts and SLAs |
| 8 | Store and replay user sessions |
| 9 | Administer users, roles, privacy, and retention |

Additional GermainUX components are deployed according to the applications, technologies, infrastructure, and users being monitored.

## When to Use an On-Premise Deployment

Choose this deployment model when your organization needs direct control over:

* Infrastructure
* Data location and residency
* Network architecture
* Platform security
* Authentication
* Backup and disaster recovery

> **Show all 10**
>
> * High availability
> * Upgrade scheduling
> * Data retention
> * Integration with internal systems

"On-Premise" in this context includes deployment within **your own cloud account** as well as your physical data center.

## Architecture

A typical architecture includes:

| Component | Purpose |
| - | - |
| **GermainUX Enterprise** | Central monitoring, analytics, administration, reporting, AI, and automation platform |
| **GermainUX Datastore** | Stores the telemetry and supporting GermainUX data |
| **GermainUX Engine** | Executes monitoring and automation close to protected systems |
| **GermainUX Agent** | Operates supported Windows monitoring components |
| **GermainUX RUM JS** | Monitors real users of customer-controlled web applications |
| **GermainUX RUM Extension** | Monitors browser applications where JavaScript cannot be deployed |
| **GermainUX RUM Windows** | Monitors supported native Windows applications |
| **GermainUX Code Profiler** | Provides code-level application observability |
| **GermainUX JS Profiler** | Provides deeper browser and JavaScript diagnostics |
| **GermainUX Mobile App** | Monitors supported Android applications and devices |
| **GermainUX RPA Bot Recorder** | Creates browser-based synthetic monitoring and automation scenarios |

Components can be distributed across multiple:

* Servers
* Network zones
* Data centers
* Cloud regions
* Production and non-production environments

## Deployment Options

Depending on your infrastructure standards and GermainUX release, GermainUX Enterprise can be deployed using supported:

* Server-based installations
* Docker
* Kubernetes
* Red Hat OpenShift
* Cloud-hosted virtual machines within your account

The appropriate architecture depends on:

* Number of monitored users
* Data volume
* Session Replay volume
* Code-profiling volume
* Retention
* Availability requirements
* Security requirements
* Number of environments

Detailed infrastructure sizing belongs in the Requirements guide.

## Before You Begin

Before starting an on-premise deployment:

**1. Define the applications and technologies to monitor**

**2. Estimate monitoring volume and retention**

**3. Select the deployment architecture**

**4. Review infrastructure requirements**

**5. Identify the systems that will host GermainUX Enterprise and its supporting components**

**6. Obtain the required GermainUX packages and license**

**7. Prepare network, DNS, certificates, and security controls**

**8. Install GermainUX Enterprise**

**9. Deploy the required monitoring components**

**10. Validate end-to-end monitoring**

## Requirements

Review hardware, software, network, storage, and infrastructure requirements before provisioning GermainUX Enterprise.

[**Review GermainUX Enterprise Requirements**](https://docs.germainux.com/main/requirements.md)

Detailed requirements are maintained on the dedicated Requirements page and should not be duplicated here.

## Package and License

Obtain the GermainUX packages and license appropriate for your deployment before installation.

[**Obtain GermainUX Packages and License**](https://docs.germainux.com/main/prerequisites.md)

The Package and License guide contains the detailed package structure, license requirements, and preparation steps.

## Deployment Overview

A typical deployment follows these stages:

### 1. Prepare the Infrastructure

Provision the compute, storage, operating system or container platform, networking, DNS, and certificates required by the selected architecture.

### 2. Prepare the Datastore

Deploy the supported datastore architecture required for GermainUX Enterprise.

### 3. Install GermainUX Enterprise

Install the central GermainUX services.

### 4. Apply the GermainUX License

Configure the license issued for the environment.

### 5. Configure Enterprise

Configure the required environment-specific services, authentication, integrations, and operational settings.

### 6. Validate GermainUX Enterprise

Confirm that GermainUX Enterprise is operational and administrators can access Germain Workspace.

### 7. Deploy Monitoring Components

Deploy only the GermainUX components required for your monitoring and automation use cases.

### 8. Validate End-to-End Monitoring

Confirm that telemetry is reaching GermainUX and appears correctly in analysis, dashboards, alerts, reports, and Session Replay where applicable.

Detailed commands and installation procedures belong in the Installation child page.

## Deployment Guides

| Guide | Purpose |
| - | - |
| [**Requirements**](https://docs.germainux.com/main/requirements.md) | Review infrastructure, software, network, and capacity requirements |
| [**Package and License**](https://docs.germainux.com/main/prerequisites.md) | Obtain and prepare the required GermainUX packages and license |
| [**Installation**](https://docs.germainux.com/main/installation.md) | Install and validate GermainUX Enterprise |

## Deploy Monitoring Or Automation Components

Once GermainUX Enterprise is operational, deploy only the components required for your use cases:

* [GermainUX Agent](https://docs.germainux.com/main/germainux-agent.md)
* [GermainUX Engine](https://docs.germainux.com/main/germain-ux-engine.md)
* [GermainUX Code Profiler](https://docs.germainux.com/main/germain-ux-code-profiler.md)
* [GermainUX JS Profiler](https://docs.germainux.com/main/germain-ux-js-profiler.md)
* [GermainUX RUM JS](https://docs.germainux.com/main/germain-ux-rum-js.md)
* [GermainUX RUM Extension](https://docs.germainux.com/main/germain-ux-rum-extension.md)

> **Show all 9**
>
> * [GermainUX RUM Windows](https://docs.germainux.com/main/germainux-rum-windows.md)
> * [GermainUX Mobile App](https://docs.germainux.com/main/germain-ux-mobile-app.md)
> * [GermainUX RPA Bot Recorder](https://docs.germainux.com/main/germain-ux-rpa-bot-recorder.md)

## Management Responsibilities

With an on-premise deployment, your organization typically manages:

* Infrastructure
* Operating systems or container platforms
* Network
* DNS
* Certificates
* Firewalls
* Backup and disaster recovery
* GermainUX Enterprise operation

Germain Software provides:

* GermainUX software
* Licenses
* Product updates
* Documentation
* Product-specific support
* Deployment assistance

Exact responsibilities may vary according to your support or services agreement.

## Security and Data Privacy

Before production use, define:

* Applications and users that may be monitored
* Data that may be collected
* Data that must be excluded
* Masking and anonymization
* Session Replay permissions
* User and administrator access

> **Show all 10**
>
> * Retention
> * Backup protection
> * Certificate and key management
> * Audit and change-management requirements

Validate these controls before expanding production monitoring.

## Validate

At the parent-page level, successful deployment means:

* GermainUX Enterprise is available.
* The datastore is connected.
* Administrators can authenticate.
* Required services are healthy.
* Monitoring components can connect.
* Telemetry is received.

> **Show all 10**
>
> * Dashboards and analysis contain expected data.
> * Alerts operate correctly.
> * Session Replay works where enabled.
> * Privacy controls work as expected.

Detailed installation validation remains in the Installation guide.

## Get Help

> **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)**
>
> The Germain Team can help you set this up.

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