Approach
How we work
The thinking behind the platform: what we connect, where we deliberately stop, and what happens to your data if you ever decide to leave.
01
Edge, not cloud alone
When a machine fault decides whether a line keeps running, the decision cannot wait for a round trip to a data centre on the other side of the internet. That is why we evaluate events as close as possible to where the data is born – at the edge – and send to the cloud only what belongs there: history, analysis and sharing across sites.
This is not an argument against the cloud, it is a question of order. A faster network does not change it – no future generation of mobile networks removes the round trip to zero. A site that can decide for itself is more resilient than one waiting on an answer from outside.
02
We connect, we do not replace
Machines, buildings and sensors a site already has stay exactly where they are. We plug into them over open standards – for example Modbus, MQTT, OPC UA, BACnet and more – instead of replacing them with a new closed system. The data we read this way stays the customer's property and is reachable through an open API – no lock-in to a single vendor. Where you want it, we can also control systems and trigger actions – air handling, heating or lighting; every write follows the same roles, permissions and audit trail as everything else.
03
What not to expect from us
Bespoke software development. Customers build the structure, panels and alarms themselves by clicking – no IT project, no programming. Anyone who needs unique software built around their own process will not find a custom-development team here.
AI that predicts failures. The in-app AI assistant guides you through setting the system up – we do not promise it will forecast what breaks before it does.
Sensor or hardware replacement. We do not sell or swap out meters, cameras or sensors – we connect what a site already has.
04
Security and data
Customer data runs in infrastructure we operate and are responsible for – not in a third party's environment without a contractual relationship. Each customer's data is kept isolated from every other customer, access is governed by roles and permissions per module, and single sign-on (SSO) is available. Every access is recorded in an audit trail.
Processing of personal data is governed by a data processing agreement (DPA) under GDPR. When a contract ends we export or delete the customer's data as agreed in the contract – the customer decides, not us.
Information-security management is certified under ISO/IEC 27001:2022, certificate No. 2025312, issued by ELBACERT with SNAS accreditation, valid until 22 June 2028. The certificate's scope covers operating and developing the platform for digital solutions in industry, smart city, smart mobility and property management.
05
After go-live
Support runs on an SLA agreed in the contract – the coverage belongs in that contract, not on a website. The knowledge base and the helpdesk are available to customers online.
Next step
30 + 30 minutes, no obligation: a walkthrough of the system, then a look at your problem in it.
- 00–30 · system walkthrough
- 30–60 · your problem in the live system
- no obligation · no slide deck