Architecture
Three layers
Select Components Based on Your Use Case
Deploy only what you need
Overview
GermainUX uses a modular architecture to observe, analyze, prioritize, act, and validate across user experience, business workflows, applications, and technologies. Only the components required for your applications and use cases need to be deployed. Together, GermainUX components provide:Architecture
GermainUX consists of three primary layers:
Select Components Based on Your Use Case
You do not need to deploy every GermainUX component. For example:| Requirement | Typical Component |
|---|---|
| Monitor a SaaS/webapplication you control, and its users | GermainUX-RUM JS |
| Monitor a SaaS/web application you cannot modify, and its users | GermainUX-RUM Extension |
| Monitor a native Windows application, and its users | GermainUX-RUM Windows |
| Analyze backend code | GermainUX-Code Profiler |
| Investigate JavaScript execution | GermainUX-JS Profiler |
| Monitor backend technologies, APIs, databases, logs, or infrastructure | GermainUX-Engine |
| Monitor Androidapplications/devices | GermainUX-Mobile App |
| Create syntheticbrowser transactions | GermainUX-RPA Bot Recorder+Engine |
Get Help
Contact GermainUX Support
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.
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.

