Embedded
10 September 2026
When does a custom microcontroller make more sense than a ready-made board?
For many IoT and industrial applications, starting with a ready-made developer board is tempting. But as soon as volumes grow or requirements for size, power consumption or security become specific, a custom microcontroller design pays off. This article explains the key decision criteria, cost factors and typical pitfalls.
Selection starts with defining sensors, communication interface and power supply. An STM32 offers high flexibility, an ESP32 integrates Wi-Fi and Bluetooth cost-effectively, and an nRF52 excels at Bluetooth Low Energy. The decisive factor is not the price of a single component, but the total cost for development, certification and maintenance.
In our experience, custom designs pay off from around 1,000 units per year, when the enclosure, power supply or interfaces have special requirements. Before that, an iterative approach is best: prototype with a developer board, field test, then custom hardware.
Web
10 September 2026
Web application or Excel? How to find the right time for custom software
Many companies start with spreadsheets to map processes. That is fast and cheap. But at some point Excel and SharePoint reach their limits: multi-user capability, permissions, versioning and automation become problems. The right time for a custom web application is reached when errors from manual input become more frequent and collaboration via email keeps getting stuck.
A custom web application solves these issues through clear workflows, roles and permissions, and direct integration into existing systems. It scales with the company and can be extended with targeted new functions. Important is to make the benefit measurable: saved working time, fewer errors, faster throughput times.
Companies that invest in custom software early pay less in the long run than those constantly struggling with workarounds and manual processes. The decisive factor is a clear MVP: a first working prototype that fixes the biggest pain point.
Industry
10 September 2026
Connecting PLC and IT: OPC UA as a bridge between machine and cloud
In industry, a gap is opening: controllers communicate in real time, corporate IT works data-oriented. OPC UA closes this gap. The open standard allows machine data to be exchanged securely, semantically described and platform-independently. For companies this means more transparency, better maintenance and the basis for predictive maintenance.
The challenge lies in integration: older PLC generations often speak proprietary protocols, networks need segmentation, and security requirements are rising. A solid architecture relies on gateways, consistent identity management and clear data models. We use proven industrial protocols and complement them with modern backends in C#/.NET or Python.
Success is measured by how quickly machine data can be turned into business decisions. Companies that establish an open communication architecture today are ready for Industry 4.0 and upcoming regulatory requirements.