Cloud, on-premise or edge. Same architecture.
Meddle runs in a European cloud, inside your own data centre, or at the edge next to the machines. The architecture does not change: only the place it executes does.
How it is reached, securely.
Managed VPN
Remote connectivity to plant equipment over a managed VPN, with a private, dedicated VPN available where it is needed.
Endpoint and SSO
A custom DNS endpoint and SSO authentication, to line up with the access management you already run.
Outbound only
The field agent opens outbound connections: no port exposed towards the OT network, compatible with DMZ and segmentation.
Where it executes.
Cloud. No upfront infrastructure cost, automatic updates, remote access and scalability. It is the shortest path for an SME.
On-premise. A local instance in your own data centre: complete data sovereignty, minimal latency and independence from internet connectivity.
Hybrid. Edge processing for time-critical data, cloud for long-term history, analytics and model training. Supported natively.
Who evaluates it with you.
The rest, in short.
Can I install it on-premise?
Yes. Meddle can run in your own data centre or in a European cloud. The architecture is the same, only the place it executes changes.
We are air-gapped, the network does not leave the plant.
That is fine. Meddle runs on-premise or at the edge, reading from the PLCs. No data leaves the plant.
Can I change topology later?
Yes. The architecture does not change across the three options, so you move between them without redoing the integrations.
Do I need hardware to start?
No. The pilot starts with no extra hardware: connectivity to most PLCs is software.
Which perimeter do you need?
We weigh cloud, on-premise and hybrid against your real constraint, before any commitment.
Book a demo