Open by default. Secure by definition.
We speak the protocols your network already speaks, we write to standard storage, we run inside your perimeter. Outbound traffic only, an audit on every write, exportable history. Data you can read only with one tool is not really yours.
Sources, core, destinations. Outbound only.
Industrial standards, any brand.
Compatible ecosystems: Siemens · Allen-Bradley / Rockwell · Omron · Mitsubishi · ABB. If a connector is missing, we integrate it as part of the suite, with no upsell.
Format lock-in. History ends up in a proprietary archive no other tool can read.
Every protocol is code. Every new line becomes custom development, which someone then maintains.
Zero observability. A tag that stops writing is something you find out weeks later, among a hundred disconnected alarms.
Every read and every write, logged.
Previous value, new value, user and time on every write to the machines.
Role-based permissions and separate environments (dev, staging, production).
Read-only in the pilot. Writing to PLCs is enabled only after your validation, with instant override.
NIS-2 ready. Data in Europe (AWS Milano) or in your own data center.
What we do not do.
We are not a MES, an ERP, a SCADA or a BMS. We connect to all of them, we do not replace them.
No heavy proprietary ML. We do anomaly detection with rules and thresholds, and we route the data to third-party analytics where needed.
ISO 27001 in progress, not obtained yet. CyberVadis with an active score. For sensitive contexts: on-prem, read-only, joint pen tests.
You have a team that could build it.
Many of the people we talk to could. The question is what is worth maintaining: connectors, formats that change and new protocols are the part that breaks and eats time. Meddle takes that edge, your team stays on the product. And the data stays yours and open, so the choice is always reversible.
The rest, briefly.
What happens to the data if we stop?
It stays yours and readable. History is queryable in SQL and exportable in open formats. No format lock-in.
What does it cost at scale?
Cost follows the machines connected. No cost per tag, per data point or per source, so adding signals does not inflate the bill.
Who does the configuration and how much effort do we need?
We do it. On your side we need one technical contact for the initial session, then we handle the conversations with your suppliers.
Try it on your network.
A pilot line inside your perimeter, outbound, without touching the rest.
Book a demo