The problem
An IoT project is not finished at commissioning. Devices fail, disks fill up, certificates expire, connections drop. Without monitoring, the customer is the first to notice.
Many platforms are built on a hyperscaler’s services. That is quick to set up and gets more expensive with every machine. Data sits with a provider outside the EU, and switching is costly because the architecture is tied to that provider’s services.
Monitoring and operations on EU infrastructure
Devices and platform send metrics and logs to a central monitoring stack: Prometheus and Node Exporter for metrics, Promtail and Loki for logs, Grafana for dashboards and alerts. You see across all sites what is running and what is not.
The platform itself runs in containers, on your infrastructure or with an EU provider. Configuration and deployment live as code in Git, and the pipeline builds and distributes. That way someone else can also take over operations.
An example: BLUECTRL ran on Azure PaaS services. Thomas Deutsch, as architect at BLUELINE, moved the platform to self-operated containers at Hetzner. This was possible because the edge devices work offline, which makes the cloud replaceable. Details in the case study.
What you get
- monitoring, logs and alerts for devices and platform
- operation of the platform on EU infrastructure or in your environment
- for a move: inventory, target architecture, migration plan and implementation
- configuration and deployment as code in your repository
Limits
We are not a data centre or a hosting provider. The infrastructure comes from you or an EU provider; we run the software on it. We do not offer a 24/7 on-call service.