Capture where data is born
Each site reads its own PLCs, RTUs and meters over Modbus, OPC UA, Siemens S7, EtherNet/IP or IEC 104, and keeps logging its history while the link is down.
8 protocolsModbus, OPC UA, Siemens S7, IEC 104, EtherNet/IP, NMEA 0183 and 2000, and CAN
Closed loopread, decide and act: control, not just dashboards
Site to siteevery change between installations, in real time
Your serversa Linux, macOS or Windows service, or a signed container image
Distributed capture and control
Capture and control at every site, linked in real time
Install Data Orchester in the control room and at each site. Every installation captures and controls its own plant, and keeps doing so if the link drops. Between them, values travel the moment they change, commands reach any site, and history catches up as soon as a link returns.
Linked in real time
Every change is pushed to the other side the moment it happens, in signed requests. A site behind NAT or on an outbound-only network dials out, so it needs no public address.
Control across sites
The control room sends setpoints and commands to any site, and that site's own modules drive the devices. Each site decides which of its variables others may write.
How installations link → Satelite, the uncapped edition for your sites →
Three pillars of industrial control
One platform from plant floor to control room
OT/IT silos, alarm latency and fragile PLC integrations are the three barriers between your plant floor and your decisions. Data Orchester removes all three, and closes the loop: it acts on the plant, not only watches it.
01
Universal industrial connectivity
It does not matter where your signals come from - Data Orchester speaks the language of your automation systems.
- Plant floor: Modbus TCP and RTU, OPC UA, Siemens S7, EtherNet/IP and IEC 60870-5-104, reading and writing
- SCADA, MES & ERP: OPC UA, Modbus and IEC 104 servers and a signed REST API
- Site to site: installations exchange live values, commands and history, even from behind NAT
02
Intelligent control engine
A reactive engine sits at the heart of the system: it evaluates every change the moment it arrives and sends the result back to the plant.
- Formulas and visual blocks, with PID, PWM and Kalman control modules
- Setpoints and commands written back to your PLCs and RTUs
- Logic modules that arbitrate between local, SCADA and scheduled commands
03
Monitor and operate
Dashboards your operators act from, not only look at, on every device they use.
- Switches, buttons and sliders that write straight to the plant
- Multi-device: desktop, tablet and phone
- Every connection reports its status and messages; loggers keep the history
AI assistant
An AI assistant inside your configuration
Three chats in the Site read your configuration, the documents and drawings you attach and Data Orchester's documentation, and the web when you allow it. The editor chats check their own drafts, and nothing they propose is saved without you.
General
Explains the plant, diagnoses a problem and suggests an action plan.
- Reads module health and live values when you allow it
- Checks before changes, each step with how to verify it
- Hands configuration changes to the editor chats
Programming
Modules, variables and formulas from your requests and the register lists you attach.
- Validates its draft and simulates new formulas first
- Proposes each change on a card you apply
- Undo takes an applied card back at once
Dashboard
Views designed and fixed from P&ID pages and requests.
- Binds to variables anywhere in the configuration
- Marks every change that writes to the plant
- Changes only the dashboard open in its editor
On by default wherever the licence is valid and the Portal can be reached; a user with the Configuration role can turn it off for the installation. Secrets are never sent, and the assistant never saves, starts or stops the engine or writes to the plant.
Solutions by industry
Built for where seconds carry cost
The same engine, the same activation flow - shaped to the control and monitoring needs your sector actually has.
Industry 4.0 & manufacturing
Track vibration and temperature with time-series checks you define, act before a drift becomes a failure, and watch line efficiency second by second.
Water & process utilities
Monitor flow, pressure and tank levels across pump stations and treatment plants, and drive pumps and valves automatically the moment a threshold is crossed.
Mining & resources
Track ground vibration and fleet health across remote sites, and act on drift before it becomes downtime or a safety incident.
Energy & utilities
Speak IEC 60870-5-104 to substations and RTUs, watch grid load and asset uptime substation by substation, and send commands from the control room.
Why us
Everything a small plant needs, at its own price
Commercial SCADA is priced for large plants, and open-source stacks leave the integration and the support to you. Data Orchester is a finished product, priced by size, with technical support included.
A fraction of the cost
A small plant runs on Full for 864 USD over three years. Commercial SCADA covering the same plant costs 3,680 to 14,670 USD.
Technical support included
Every licence includes answers to your technical questions from the engineers who build Data Orchester, at no extra cost.
Nothing sold as an add-on
Every protocol, the history, the panel editor, sign-in with your directory and the AI assistant come with every edition. You pay for size, not for modules.
Free for real work
Up to 50 variables, for commercial use, with every module, panels and the AI assistant. No trial clock.
Runs on your servers
A service on Linux, Windows or macOS, on x86 or ARM, or a signed container image: from a rack server to a field board.
Made for remote sites
Sites on mobile links connect out to the control room, with no public address, VPN or proprietary router, and catch up on their history after an outage.
The operational challenge
Every plant floor generates millions of signals every second: PLC tags, sensor readings, alarms, machine states. But is your control room actually seeing them in real time, and acting on them?
Most industrial operations struggle with:
- OT/IT silos — SCADA, PLCs and business systems that don't talk to each other.
- Alarm latency — anomalies detected minutes or hours after they start costing you.
- Fragile integrations — brittle drivers and point-to-point links that break with every firmware update.
Data Orchester removes these barriers. It is the unified platform for industrial automation control and monitoring — it connects your sensors, PLCs and controllers, and turns their signals into live monitoring and automated control, on-premise, in a private cloud, or across both.
It is designed to control, not only to monitor and display. Data Orchester reads your PLCs, RTUs and sensors, decides with formulas and PID, PWM and Kalman control modules, and writes setpoints and commands back over the same protocols. Your SCADA can command it through its own OPC UA, Modbus and IEC 104 servers, and your operators act straight from its dashboards.
And it is distributed. Install it in the control room and at every site: each installation captures and controls its own plant, and they exchange values, commands and history in real time. A site behind NAT simply dials out.
And an AI assistant helps you build it. Three chats in the Site read your configuration, the register lists and drawings you attach and the documentation: two propose modules, variables, formulas and views on cards you review, apply and undo, and the third diagnoses problems with an action plan. Nothing is saved without you. See the AI assistant and its guide.
Technical specifications
Designed for demanding automation and OT teams, but friendly to the business side.
| Feature | Detail |
|---|---|
| Industrial protocols | Modbus TCP and RTU (master and slave), OPC UA (client and server), Siemens S7, EtherNet/IP and IEC 60870-5-104 (client and server), NMEA 0183 (listener and talker), NMEA 2000 and CAN bus, reading and writing |
| Control | Formulas and visual blocks; PID, PWM and Kalman control modules; logic modules; setpoints and commands written back to the plant; switches, buttons and sliders on dashboards |
| Distributed | Installations linked site to site: every change pushed in real time, setpoints and commands to any site, history replication that catches up after an outage, sites behind NAT that dial out; every exchange signed, and each site chooses what others may write |
| Integration | A signed REST API and outbound HTTP calls for SCADA, MES, ERP and cloud systems |
| Modularity | Every connection, logic block, logger and peer link is a module, added and configured from the browser |
| Operations | Every module reports its status and messages; chosen records export and import between installations |
| AI assistant | Program, dashboard and general chats that read the whole configuration, your documents and the documentation, and the web when allowed; changes proposed on cards you apply and undo, never saved without you; off until turned on per installation, and secrets never sent |
| Deployment | One install package for Linux and macOS (x64 and arm64) and Windows (x64), or a container image for amd64 and arm64: on-premise, in your private cloud, or both |
| Security | HTTPS built in or behind your reverse proxy; OPC UA Sign and SignAndEncrypt; signed peer links; sign-in with local accounts, LDAP/Active Directory, OpenID Connect or SAML through a broker; roles that separate configuration from security administration |
| Licensing | Free, Satelite or Full - permanent, or a prepaid term of as many months as you need |
Every edition runs the same engine and the same activation flow — only the limits and the features differ.
Ready to take control of your plant?
Stop reacting to the past. Start controlling the present.
Download the platform and run it on your own infrastructure, or talk to an engineer about a deployment shaped around your control systems.