Same VECHR MES everywhere. You choose where the core runs.
There is no cloud-only edition and no on-premises edition. One platform, installed where your IT team wants it.
The core runs in your own cloud account or on your own servers. Every plant connects through a local Edge Agent that keeps recording when the network drops.
Cloud or on-premises. The difference is where it lives, not who runs it.
| Cloud | On-Premises | |
|---|---|---|
| Runs in | A dedicated, private deployment in your company's own cloud account | Infrastructure you already run: your cluster, data center or private cloud |
| Servers and database | Run by your own team, inside your account | Run by your own team, as part of your estate |
| Shared with other customers | Never | Never |
| Best fit for | Getting started quickly, no data-center overhead | Data residency, regulation, or nothing leaves the building |
Every plant gets an Edge Agent. It is part of both paths, not a third option.
A small component on hardware inside the plant, close to the machines.
- Keeps recording offline Every reading lands locally first. Nothing is lost, and it catches up when the link returns.
- Speaks your machines' protocols OPC UA, MQTT and Modbus TCP, over a local connection.
- No inbound firewall rule One outbound connection to the core. Nothing opens at the plant.
- Approved before it joins An administrator approves every device. Nothing connects automatically.
Built to keep running while the plant keeps running.
- Runs on Kubernetes In your cloud account or on your own cluster.
- Scales and self-heals Adds capacity under load and recovers if something fails.
- Zero-downtime updates New releases roll out without stopping production.
- Monitoring included Logs, traces and metrics, so IT isn't building dashboards from scratch.
Exact sizing depends on your tag count, sample rates, transaction volume, number of plants and retention. We measure those in the Workshop Assessment, so your IT team gets a number, not a guess.
Frequently Asked Questions
What happens if a plant loses its internet connection?
The Edge Agent keeps recording locally and catches up automatically once the connection is back. The line does not stop.
Is this a shared platform we log into?
No. Even on the cloud path, VECHR MES is installed as a dedicated deployment in your own account. No other customer's data shares it.
Does our data leave our building on-premises?
No. On-premises, your production data never leaves your environment.
Who manages the database?
Your own team, on either path. The deployment choice changes where it lives, not who operates it.
Do we choose between the cloud and the Edge Agent?
No. The Edge Agent is part of every deployment. You only choose where the core runs.
Terms on this page(5)
- MESManufacturing Execution System
- The system that runs and records production on the floor: orders, materials, steps, quality and machines.
- Modbus TCPModbus over TCP/IP
- A long-established industrial protocol, carried over an Ethernet network.
- MQTTMessage Queuing Telemetry Transport
- A lightweight publish/subscribe protocol for sending machine data.
- OPC UAOPC Unified Architecture
- The open standard for reading data from PLCs and machines securely.
- PLCProgrammable Logic Controller
- The industrial computer that controls a machine and holds its live values.
See VECHR MES on your own process.
A walkthrough built around how your plant runs. Not a generic demo.