MX-UI Reference
The MX-UI is the web console for your MX product family. It is a visual intent builder and live monitoring dashboard that lets you design, deploy and operate 5G / O-RAN networks, terminals, O-RAN apps, Digital Twins and AI fabrics on the cluster β without writing YAML by hand.
Everything you build is translated into Trirematics Custom Resources (CRs) and applied to the cluster. Every view streams live status from the cluster over a websocket, so what you see is always the current state.
What can I do with it?β
| I want to⦠| Go to | Section |
|---|---|---|
| Get a one-glance health summary of everything | Dashboard | Platform Overview |
| See cluster nodes and attached radio hardware | Nodes and Hardware | Cluster Overview |
| Check storage and monitoring health | Storage & Monitoring | Cluster Overview |
| Open a cluster service (e.g. Grafana) inside the UI | Services | Cluster Overview |
| Design and deploy a 5G/O-RAN network | Intent Builder | MX-PDK |
| Watch deployed networks and their health | Networks | MX-PDK |
| Register and test UEs (terminals) | Terminals | MX-PDK |
| Visualise a network as a live graph | Topology | MX-PDK |
| Deploy and manage xApps / rApps | O-RAN | MX-PDK |
| Build and chat with AI agent fabrics | MX-AI | MX-AI |
| Inspect models, operators and license | Management | Management |
Layout at a glanceβ
The console has three persistent areas:
- Left sidebar β the main navigation, grouped into sections (Platform Overview, Cluster Overview, MX-PDK, MX-AI, MX-DT, Management). Sections you are not licensed for appear locked.
- Top header β namespace selector, a live system-health badge (Nominal / Notice / Warning / Critical), and your user menu.
- Content area β the active page.
Concepts used throughout the UIβ
A few patterns repeat across every page β learn them once:
- Real-time everywhere. Pod counts, status pills and node colours update live; nothing needs a manual refresh.
- YAML-first. Networks, terminals, xApps, rApps and fabrics all show a YAML preview of the generated manifest before you deploy.
- Validation gates deploy. Builders run live validation (PLMN match, IMSI format, required hardware, β¦) and prevent you from deploying misconfigured resources.
- License and operator gating. MX-AI and Digital Twin views require the matching license capability; when locked they appear dimmed and link to the Platform License page.
- Status colours are consistent. From the platform badge, through the status pills, through cards - all use the same colour scheme
| Colour | Label | Meaning |
|---|---|---|
| π’ | Nominal | All systems healthy |
| π΅ | Notice | Informational, non-critical |
| π | Warning / Degraded | Degraded β attention recommended |
| π΄ | Critical | Failure β immediate action required |
Next stepsβ
- Remote Access β reach the UI from your laptop.
- Platform Overview β read the Dashboard.
- MX-PDK β build and deploy your first network.