
Data privacy and AI: what happens to the documents we hand over
Using AI on contracts and confidential documents means deciding where the data goes. The options, from local models to pseudonymization, and what each one costs.
Stories on how we design and ship our industrial, IoT and digital products. Experiments, lessons from the field, technical deep-dives.

Using AI on contracts and confidential documents means deciding where the data goes. The options, from local models to pseudonymization, and what each one costs.
Stories from our R&D team.
A prototype of a development support tool: an AI reviewer reads our pull requests from inside a locked-down container and leaves only private drafts.
The Indaconn Edge module that collects data over MQTT, OPC-UA and MTConnect, makes it uniform and exposes it to SCADA and PLCs over OPC-UA and Modbus, with replay to Indaconn Cloud.
What it really costs to build an AI assistant on your documentation: the numbers item by item, from tokens to review hours, with the public price lists in hand.
Context, boundaries and characterization tests: three pillars for letting AI agents work on legacy code safely. With a hands-on Rails upgrade.
From the IAM group to the first kubectl get nodes: how we set up Kubernetes clusters we run ourselves on AWS.
How we moved the software that tracks donated human milk to React and TypeScript, after more than a decade locked to Silverlight and Internet Explorer.