AereA GmbH
Discuss your project

Custom software for technically demanding systems

Software that still runs in five years.

Architecture, development and quality assurance in one team, for systems where downtime gets expensive. Industrial automation, energy, telecommunications, medical technology.

Technology fields

  • OPC UA · MQTT · Kafka
  • Modbus / SunSpec
  • SIP · RTP/SRTP · WebRTC
  • PKI / X.509 · OAuth2 / OIDC
  • IEC 62304 · BITV 2.0
2009
founded, owner-managed, at the same location ever since
17
years owning the same product, since the day we started
6
industries with their own approval and protocol constraints
14
years as a registered training company, IT specialist for application development

The core promise

Architecture, development and quality assurance sit in one team.

At a software company of this size, independent QA competence is rare. Usually developers test their own code, or the client takes on acceptance testing. At AereA, an ISTQB-certified test manager owns quality assurance from the management level. That is why the systems keep running after handover.

01

QA is not a phase, it is a role

Test-driven development as a binding team standard, tests as a mandatory gate in CI, end-to-end tests against genuinely running APIs with a real database instead of against mocks.

Evidenced by the test architecture in EcoPulse and Phonalisa

02

Responsibility over years, not until handover

We have owned Phonalisa architecturally since the day we founded the company, 17 years now, developing, testing and documenting it throughout. At the same industrial client, the data platform was followed by the migration of the condition monitoring backend.

The answer to “will you still be around in ten years?”

03

Regulated and safety-critical environments

Medical technology in an approval-relevant setting, tax software for a state finance authority with accessibility and GDPR testing, vehicle bus analysis at a premium manufacturer, energy infrastructure in the field.

  • IEC 62304
  • BITV 2.0
  • GDPR

On the subject of AI

A small team delivers at the speed of a large one.

Agent-assisted development runs inside defined guardrails, with human sign-off for architecture, security and release. The capacity we free up goes into test depth, not into more features.

Project report: energy, IIoT, e-mobility

EcoPulse consolidates 20 device and manufacturer types into one real-time data base, backed by over 90 % test coverage across all services.

Inverters, battery storage, wallboxes and meters come together in a shared time series base. On that basis the platform decides automatically about charging, discharging and shifting flexible loads, operated by us, with observability across the whole path.

Industry
Energy, IIoT, e-mobility
System type
Distributed platform, edge to web
AereA's role
Architecture, development, QA, operations
Deployment
On premises, cloud or hybrid
EcoPulse web interface: site overview with status metrics, forecast curves and the energy flow between generation, storage, grid supply and flexible loads.
Fig. 1: Real-time site overview: status metrics, forecast values and the energy flow between generation, storage, grid supply and flexible loads.

Starting point

Heterogeneous energy and charging infrastructure without a shared data base: every manufacturer with its own interface, no reliable basis for load decisions.

Approach

Five cleanly separated processing stages: edge connectivity, ingest via MQTT and Kafka, state projection into TimescaleDB, versioned REST API with live stream, Angular interface.

Result

Price- and CO₂-optimised charging and storage based on day-ahead prices from European bidding zones, with automated load shifting and storage control.

  • C#/.NET
  • Angular
  • TypeScript
  • Python
  • MQTT
  • Kafka / Redpanda
  • Modbus / SunSpec
  • PostgreSQL / TimescaleDB
  • SignalR
  • Testcontainers
  • Grafana stack

Services

Four clusters, end to end from the machine to the interface.

Each cluster with its own page: what we actually do, when we are the wrong supplier, collaboration models, typical project size and a named contact.

How we work

Methodology you can actually read.

Our playbook is public: what a quality gate looks like here, what an agent may and may not do, how we cut an arc42 document.

Read the playbook →

  1. 01 Test-driven development is the team standard, not a recommendation: red/green/refactor, and the test suite decides the merge.
  2. 02 Documentation is part of the product: architecture to arc42, test documentation, release notes, manuals and context help.
  3. 03 Agent-assisted development with guardrails: human sign-off for architecture, security and release, always.
  4. 04 Knowledge transfer is part of the deal: coaching within the team and at the client, training at industrial clients, in-house apprenticeships since 2012.
  5. 05 Developed in Germany, no cookies on this site, processes documented to ISO 27001 logic without claiming a certificate.

Contact

Talk to the architect directly.

No call centre, no transfers. We reply within one working day, usually within the hour.

Sören Sprenger
Software architecture & technical project management

Wüstenstein 18, 91346 Wiesenttal · Mon-Fri 9:00-18:00 CET

Discuss your project: four fields

No cookies, no tracking, no sharing with third parties.