MiroxMirox
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
  • 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
    • Wind Plants
    • Battery Storage
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Loss Detection
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Tickets
    • Forecasts
    • Reports
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • Proxy
  • AI

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

    • Market & Tariffs
    • Accounting & Billing
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Permission System
    • Cooperation Restrictions
    • Access Audit Logging
  • Nodes

    • mrxnode
  • Application

    • Door Control
    • Generic Relay
  • Edge Cluster

    • Orchestration
  • Getting Started

    • First Steps
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Components
    • Direct VPN (per Agent)
  • Organization

    • Member Permissions
    • Cooperations
    • File Storage
  • Data Export

    • Export Metric API
    • MiroxQL Query Language
    • External Report Generation
    • Grafana
    • API Overview
  • Support

    • Request Integration Guide
  • mrxnode

    • Overview
    • How-To Guide
    • Container Deployment
    • Command Cheatsheet
    • Troubleshooting
  • Reporting

    • External Report Generator
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
  • 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
    • Wind Plants
    • Battery Storage
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Loss Detection
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Tickets
    • Forecasts
    • Reports
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • Proxy
  • AI

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

    • Market & Tariffs
    • Accounting & Billing
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Permission System
    • Cooperation Restrictions
    • Access Audit Logging
  • Nodes

    • mrxnode
  • Application

    • Door Control
    • Generic Relay
  • Edge Cluster

    • Orchestration
  • Getting Started

    • First Steps
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Components
    • Direct VPN (per Agent)
  • Organization

    • Member Permissions
    • Cooperations
    • File Storage
  • Data Export

    • Export Metric API
    • MiroxQL Query Language
    • External Report Generation
    • Grafana
    • API Overview
  • Support

    • Request Integration Guide
  • mrxnode

    • Overview
    • How-To Guide
    • Container Deployment
    • Command Cheatsheet
    • Troubleshooting
  • Reporting

    • External Report Generator
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Platform

    • Platform Philosophy
    • Platform Overview
    • Platform Resources
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

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

    • Metric Collection

Platform Philosophy

Mirox gives operators, investors, and service providers a renewable-energy platform that not only monitors installations but truly understands them through active data collection, physics-based modeling, and secure collaboration. This page explains the principles behind those choices.

Vision and Purpose

The Mirox platform was created to address fundamental challenges in renewable energy infrastructure management. Traditional monitoring systems often rely on passive data collection, where devices periodically upload information that may be incomplete, delayed, or erroneous. We built Mirox to take an active approach: continuously retrieving data, validating it in real-time, and maintaining a complete, accurate picture of each installation.

Our goal is to provide operators, investors, and service providers with a platform that not only monitors renewable energy installations but truly understands them through digital modeling and intelligent analysis.

Core Design Principles

Modular Architecture

We chose a microservices-based architecture because renewable energy infrastructure is inherently diverse and constantly evolving. Rather than building a monolithic system that tries to do everything, we designed specialized services that each handle specific domains:

  • Data collection services with dedicated adapters for each logger, inverter, and meter family
  • Digital Twin services that model and evaluate solar plant behavior
  • IoT integration services for on-site hardware and the plant's local network
  • Analytics services for performance evaluation and reporting

This modular approach allows the platform to evolve incrementally. New capabilities can be added, existing services can be improved, and components can be replaced without disrupting the entire system.

Cloud-Native Technology

We built Mirox using cloud-native principles and modern infrastructure technologies. This decision enables:

  • Scalability: The platform automatically adjusts to handle installations of any size
  • Reliability: Services are distributed and fault-tolerant
  • Maintainability: Updates and improvements can be deployed without downtime
  • Cost-efficiency: Resources scale based on actual usage

The cloud-native approach also accelerates development cycles. Using established patterns and tools allows us to focus on solving domain-specific challenges rather than rebuilding common infrastructure.

Active Data Collection

Unlike systems that wait for devices to push data, Mirox actively retrieves information from installations. This design choice addresses several critical issues:

  • Completeness: We can detect when data is missing and take action
  • Timeliness: Problems are identified immediately, not hours or days later
  • Reliability: The system doesn't depend on device-initiated communications that may fail
  • Quality: Data is validated as it arrives, not accepted blindly

This active approach requires more sophisticated collection infrastructure, but it fundamentally improves the reliability and usefulness of the monitoring system.

Digital Twin Methodology

The term "digital twin" is often used loosely in the industry to describe simple visualizations or static models. We implemented the Digital Twin as a dynamic, physics-based model that:

  • Continuously compares each plant against its expected behavior under current conditions
  • Calculates the energy a plant should produce from solar irradiance and component layout
  • Identifies deviations that indicate underperformance or faults
  • Attributes losses to the responsible component or condition

This is grounded in established solar physics rather than statistical guesswork, so it enables capabilities that simple monitoring cannot provide: loss detection, component-level evaluation, and early fault detection.

Secure Collaboration

Modern renewable energy operations involve multiple parties: owners, operators, maintenance companies, investors, and service providers. We designed the platform's permission system to support this reality:

  • Fine-grained role-based access control
  • Secure cooperation between different organizations
  • Audit trails of all access and changes
  • Support for regulatory compliance requirements (including KRITIS standards)

Rather than treating collaboration as an afterthought, we made it a core architectural concern.

Technology Choices

Multi-Protocol Support

Our platform focuses exclusively on TCP/IP-based communication. When integrating new devices or data loggers, we require either direct TCP/IP communication to the end device or an intermediary device that translates wired technologies into TCP/IP protocols.

This design choice is based on crucial aspects of modern development: TCP/IP has become the standard protocol for all new devices on the market due to its high flexibility, reliability, and universal compatibility—unlike outdated communication protocols such as traditional serial Modbus. While wired communication technologies have their own benefits, our architecture and need for scalability necessitate a clear boundary at TCP/IP.

We consciously set this technical boundary to maintain system coherence and performance, though we remain open to supporting other communication technologies upon specific customer requests.

European Data Sovereignty

We made a deliberate choice to build Mirox as a European solution with architectural independence from vendor lock-in. Our design adapts to evolving European critical infrastructure requirements, including KRITIS regulations and the Critical Entities Resilience (CER) Directive for the energy sector.

During development, we build on proven open source tools—primarily from the Cloud Native Computing Foundation (CNCF)—rather than reinventing existing solutions. Once deployed, the platform operates independently. We maintain no vendor dependencies for hosting or service provision, ensuring:

  • Data remains under European jurisdiction and regulations
  • Full compliance with GDPR and evolving European critical infrastructure standards
  • Independence from geopolitical concerns affecting proprietary software providers
  • No mandatory reliance on external vendors for operations

This approach combines the efficiency of modern open source development with the sovereignty and resilience required for critical energy infrastructure.

Pricing Philosophy

Many renewable energy monitoring platforms charge based on installation capacity, which disproportionately affects large operators. We chose a different pricing model that aligns costs with actual usage and value rather than penalizing scale.

Development Approach

AI-Assisted Development

We leverage AI-generated code and modern development tools to:

  • Accelerate development cycles
  • Reduce implementation costs
  • Maintain consistent code quality
  • Focus human expertise on complex domain challenges

This approach allows us to offer competitive pricing while maintaining high-quality software.

Continuous Evolution

The platform is designed to evolve continuously. New features, improved algorithms, and enhanced capabilities are deployed regularly without disrupting existing operations. This keeps the platform current with technological advances and changing industry needs.

Operational Philosophy

We believe effective monitoring requires more than just collecting data—it requires understanding what that data means. The platform is designed to:

  • Detect Problems Early: Identify issues before they become critical
  • Provide Context: Explain why something is happening, not just that it happened
  • Enable Action: Give operators the information they need to make decisions
  • Support Improvement: Track performance over time and identify optimization opportunities

To make that understanding accessible, the platform also offers AI-assisted operation: a conversational assistant and guided wizards help you onboard plants, interpret results, and act on findings without digging through every screen.

Looking Forward

The renewable energy sector is evolving rapidly. New technologies, changing regulations, and growing scale all present challenges for monitoring and management systems. Our modular, cloud-native architecture positions Mirox to adapt to these changes while maintaining the stability and reliability that critical infrastructure requires.

We continue to develop new capabilities, refine existing features, and respond to the real-world needs of renewable energy operators. The platform's design ensures that these improvements benefit all users without requiring disruptive migrations or complete system replacements.

Related Features

  • Platform Overview — how the cloud and agent layers fit together
  • Digital Twin — the physics-based modeling that turns data into understanding
  • Data Scraper — the per-vendor adapters behind active data collection
  • Permission System — the role-based access control that enables secure cooperation
  • AI Assistant & Wizards — conversational and guided operation across the platform
Next
Platform Overview
MIT Licensed | Copyright 2026 Mirox Verwaltungs GmbH