MiroxMirox
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
    • Availability and Maintenance Windows
    • Releases and Versions
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Solar Trackers and Park Controllers
    • Wind Plants
    • Battery Storage
    • Alarm System
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Inverter Status Codes
    • Inverter Events
    • Loss Detection
    • Power Limits & Curtailment
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Alarm Levels
    • Tickets
    • Forecasts
    • Reports
    • Metrics
  • Alert Manager

    • Overview
    • Alert Rules
    • Alerts & Notifications
    • Examples
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • VPN Address Conflicts
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • How Revenue Is Calculated
    • Accounting & Billing
    • Contracts
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Account Lockout
    • Organization Security Policy
    • Permission System
    • Network Segmentation
    • Cooperation Restrictions
    • Access Audit Logging
    • Activity & Audit Trail
    • Data Isolation
  • Getting Started

    • Onboarding
    • Setup
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
    • Notifications
    • Connect Microsoft Teams
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Generic Modbus Reader
    • Components
    • Direct VPN (per Agent)
    • Data Volume
    • History Import
  • Organization

    • Member Permissions
    • Security Policy
    • Cooperations
    • File Storage
    • VPN Services
    • Working with Reports
  • Data Export

    • Metric Export
    • Metric Export API
    • Migrating to the Metric Export
    • Legacy Export API
    • External Report Generation
    • Grafana
    • Grafana Dashboards
    • API Overview
    • MiroxQL Formulas (API)
  • Support

    • Request an Integration
  • Reporting

    • External Report Generator
    • Metric Export for Excel
  • Remote Access
  • Account Security
  • AI in Mirox
  • History Import
  • Reports
  • Data Export
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
    • Availability and Maintenance Windows
    • Releases and Versions
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Solar Trackers and Park Controllers
    • Wind Plants
    • Battery Storage
    • Alarm System
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Inverter Status Codes
    • Inverter Events
    • Loss Detection
    • Power Limits & Curtailment
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Alarm Levels
    • Tickets
    • Forecasts
    • Reports
    • Metrics
  • Alert Manager

    • Overview
    • Alert Rules
    • Alerts & Notifications
    • Examples
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • VPN Address Conflicts
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • How Revenue Is Calculated
    • Accounting & Billing
    • Contracts
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Account Lockout
    • Organization Security Policy
    • Permission System
    • Network Segmentation
    • Cooperation Restrictions
    • Access Audit Logging
    • Activity & Audit Trail
    • Data Isolation
  • Getting Started

    • Onboarding
    • Setup
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
    • Notifications
    • Connect Microsoft Teams
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Generic Modbus Reader
    • Components
    • Direct VPN (per Agent)
    • Data Volume
    • History Import
  • Organization

    • Member Permissions
    • Security Policy
    • Cooperations
    • File Storage
    • VPN Services
    • Working with Reports
  • Data Export

    • Metric Export
    • Metric Export API
    • Migrating to the Metric Export
    • Legacy Export API
    • External Report Generation
    • Grafana
    • Grafana Dashboards
    • API Overview
    • MiroxQL Formulas (API)
  • Support

    • Request an Integration
  • Reporting

    • External Report Generator
    • Metric Export for Excel
  • Remote Access
  • Account Security
  • AI in Mirox
  • History Import
  • Reports
  • Data Export
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Platform

    • Platform Philosophy
    • Platform Overview
    • Platform Resources
    • Availability and Maintenance Windows
    • Releases and Versions
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Mirox-Agent
    • Agent Deployment
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection

Platform Overview

The Mirox platform pairs a central cloud service with a dedicated agent for each plant, giving you a single, reliable view of your renewable energy assets.

Architecture Components

The platform is built around two components that define how the system operates: the Mirox-Cloud and the Mirox-Agent.

Mirox-Cloud — Central Coordination

The Mirox-Cloud is a cloud-native platform built on a microservices architecture. It coordinates specialized services to create a robust, scalable ecosystem.

Core Capabilities:

  • Data Aggregation: Collects and consolidates data from all connected agents
  • Advanced Analytics: Performs complex analysis, pattern recognition, and anomaly detection
  • Multi-Tenant Management: Supports multiple organizations, portfolios, and parks
  • User Management: Handles authentication, authorization, and collaboration
  • Visualization: Provides dashboards, reports, and real-time monitoring interfaces
  • Integration: Offers APIs and export capabilities for external systems
  • Event Management: Processes and distributes alerts and notifications

Architectural Principles:

  • Microservices-Based: Specialized services for authentication, data processing, reporting, events, metrics, etc.
  • Cloud-Native: Built using modern container orchestration and deployment practices
  • Scalable: Automatically adjusts resources based on demand
  • Resilient: Distributed architecture with fault tolerance and redundancy
  • Secure: Multi-layered security with encryption, access control, and audit logging
  • Extensible: New microservices can be added to extend functionality

Underlying Building Blocks:

  • Containerized services managed by automated orchestration
  • A time-series database for metrics storage
  • A relational database for configuration and user data
  • A message broker for communication between services
  • Object storage for media and large files
  • Load balancers and API gateways for traffic management

The cloud provides the central coordination and user-facing capabilities that complement the distributed agent network.

Mirox-Agent — Per-Plant Intelligence

The Mirox-Agent is the dedicated component for each renewable energy park. It serves as the intelligent system responsible for the plant's data collection and analysis, connected to the plant through its own VPN tunnel.

Key Responsibilities:

  • Data Collection: Continuously collects data from inverters, meters, sensors, and other equipment using vendor-specific adapters
  • Digital Twin Maintenance: Builds and maintains a virtual model of the installation for solar plants
  • Network Monitoring: Discovers local devices and tracks their connectivity and communication health
  • Edge Analytics: Runs per-plant checks such as performance ratio, clear-sky baselines, and curtailment tracking
  • Local Processing: Performs data validation, preprocessing, and buffering

Architecture Characteristics:

  • Dynamic: Automatically adapts to changes in the installation configuration
  • Extensible: New adapters and capabilities can be added without redesigning the system
  • Resilient Operation: Re-placed automatically if its host or region fails

The agent acts as the bridge between physical renewable energy equipment and the cloud-based Mirox-Cloud, ensuring continuous data flow and local intelligence.

How They Work Together

The architecture leverages both components in a distributed system design:

  1. Mirox-Agents deployed at each park handle local data collection and initial processing
  2. Mirox-Cloud receives data streams from all agents and provides centralized management
  3. Bidirectional Communication allows the Mirox-Cloud to configure Mirox-Agents and retrieve additional information
  4. Separation of Concerns ensures that local operations continue even during network interruptions
  5. Coordinated Intelligence combines edge processing with cloud-scale analytics

This two-tier architecture provides:

  • Performance: Local processing reduces latency and network load
  • Reliability: Distributed design eliminates single points of failure
  • Scalability: Both components scale independently based on needs
  • Flexibility: New features can be deployed to either agents or services as appropriate
  • Cost Efficiency: Processing is distributed optimally between edge and cloud

Design Benefits

This architectural approach provides several key advantages:

Modularity

Both the agent and service are built with modular designs. New capabilities can be added incrementally without redesigning the entire system.

Adaptability

The system adapts to different installation types, sizes, and equipment configurations automatically.

Resilience

Distributed architecture ensures that local operations continue even when connectivity to the cloud is interrupted.

Scalability

Each component scales independently - agents scale with the number of parks, while the service scales based on data volume and user activity.

Maintainability

Clear separation between edge and cloud responsibilities simplifies updates, troubleshooting, and ongoing maintenance.

Summary

This two-component architecture forms the foundation of the platform, combining edge intelligence with cloud-scale coordination while keeping both halves simple and reliable.

Related Features

  • Mirox-Cloud — the cloud-native services behind central coordination and analytics
  • Mirox-Agent — the per-plant agent that collects data and runs local checks
  • Connected Microservices — how the cloud services and external dependencies fit together
  • Platform Philosophy — the principles behind the edge-and-cloud design
Prev
Platform Philosophy
Next
Platform Resources
© 2026 Mirox Verwaltungs GmbH. All rights reserved. | Privacy Policy