MaestroHub is the industrial context platform: it connects every machine and business system in your plant and turns their data into one governed language, so your people and AI can see the plant, understand it and act on it, inside your rules and on your own infrastructure.
120+ machines and systems
AI agents
Claude, or any MCP clientMaestro agentbetaApps and analytics
Dashboards and appsData platforms and BIEvery pipeline is checked when you save it, every stored value carries a quality verdict and its writer, and a 2.6 install upgrades with one command. Your PLCs, your historian and your SCADA stay where they are.
Upgrade from 2.6, with a command, not a script
# see every change before anything moves $ context-platform upgrade check # back up, convert, verify $ context-platform upgrade apply # changed your mind $ context-platform upgrade restore
Read what changes in 3.0 before you apply.
Why industrial AI stalls
You bought the AI. It still cannot tell you what a stop cost, because all it sees is numbers: nothing gave your data one meaning, one map, or permission to act.
Plant managerWhat did yesterday's stop on Line 3 cost us?
Your AIThree systems give me three different stop times, so I cannot tell how long it lasted, let alone what it cost.
Missing: one meaning
Dozens of protocols, thousands of tags, and three systems that disagree about the same event. Every integration is a one-off.
See the Context EnginePlant managerPump 4 is running hot. What happens if it fails?
Your AII can see it is at 87 °C. I cannot see what it feeds, so I do not know what would stop.
Missing: one map
A value has no neighbours. Nothing says what feeds what, what controls what, or what stops if this stops.
See the Knowledge GraphPlant managerSlow Line 2 down until the jam is cleared.
Your AII am not allowed to. Nobody has set who I act for, what I may change, or how my changes are recorded.
Missing: permission to act
Nobody lets an agent touch a line without knowing who it acts for, what it may do, and what it did.
See agents and governanceThe architecture
ns=2;s=P101.VIB3.4No name. No unit. No quality.MaestroHubContext Engine
Names itPump 1, vibration
Adds the unit and checks qualitymm/s, good
Records where it came fromOPC UA, PLC-2
3.4 mm/s
from PLC-2
and 80+ more connectors, reaching 120+ kinds of machines and systems.
More than 100 connectors reach over 120 kinds of machines and systems. Context Engine gives every value its schema, its quality and where it came from. Take a destination offline and watch the buffer drain.
Line 2, demo plant. Illustrative.
What stops if Pump 1 stops?
Also ask
What does Tank 1 feed?
What changed on Line 2 since Tuesday?
Which pumps vibrate above 3 mm/s?
2 things stop. 1 can take over.
StopsFiller 2fed by Pump 1
StopsCapper 2fed by Filler 2
StandbyPump 2also feeds Filler 2
Walked 2 hops downstream over "feeds". As of now.
Knowledge Graph holds every thing in the plant and how it relates: what feeds what, what controls what, what stops if this stops, and what the plant looked like on any past day. Illustrative answer on a demo plant.
Claude, through MCP
Capper 2's gearbox is running hot. Schedule the service for Thursday and raise the work order.
Or ask through
The Maestro agent insidebeta
An App Studio appbeta
Acting forRyu Kaplan, maintenance lead
Read the historianAllowed
Write a work orderNeeds approval
RKRyu approves. Scoped grant, two hours.
Audit trail
06:02agent proposesrecorded
06:04Ryu Kaplan approvesrecorded
06:04ran as Ryu Kaplanrecorded
Chain verified
Bring your own MCP client today. In Beta, by early access: the Maestro agent inside the product, and App Studio, where a domain expert describes the application they need and it is built on the whole platform. It all runs inside that person's permissions, and every step is audited.
The product
One trusted source for all your plant data.
Connect your machines and systems once. Every value carries its meaning and traces back to where it came from.
Know what stops if this stops.
Your plant as things and links. Ask what feeds what, what stops next, and what changed since Tuesday.
Your line's app, without waiting on IT.
Describe it to our agent, or to the one you already use, like Claude. Each app can only do what the person using it is allowed to do.
Deployment
MaestroHub runs where your data is, your tools stay where they are, and nothing leaves your network unless you send it.
Your network
MaestroHub runs hereOne binary at the edge, or Kubernetes at site levelMaestroHub, the companyPublishes releases with SBOMs you can check without us, and gives support on your terms.European home appliance leader
Planning, PLC and quality data in one hub, with live KPI dashboards and alerts before issues escalate.
Automotive leader
Edge data and operator feedback feed anomaly models that warn supervisors before a CNC tool fails.
Chemical manufacturing leader
Distillation SCADA and ERP data joined to show steam and energy cost per batch in real time.
Reference architecture
What comes in from the plant, what MaestroHub does with it, and who uses it. Follow the numbers.
Your plantAny vendor, any age
PLCs and controllers
CNC machines and robots
SCADA and historians
MES and ERP, such as SAP
Databases and files
Cloud and IoT services
MaestroHubOne platform, running inside your network13 releases, Feb to Aug 202637 engineering rules, each from a real defect
2Context EngineSee the plant
3Knowledge GraphUnderstand itComing soonin development and testing
4Agents and App StudioAct on itLiveBeta
5Governed write-backActions return to the plant as a named person, checked first and recorded. A data path, not a control loop.
Who uses itPeople, agents and systems
Compliance and control
Free trial
Download MaestroHub and run it on your own machine. You get every feature, Enterprise ones included, in two-hour sessions that you can restart as often as you like, with no licence and no sales call.
Windows, macOS and Linux
MaestroHub is the industrial context platform. It connects machines and business systems, gives every value one meaning in a governed namespace, holds the plant as a knowledge graph, and lets AI agents and applications act on the factory inside permissions and an audit trail. It has three products: Context Engine, which is live, App Studio, which is in Beta, and Knowledge Graph, which is in development.
Context Engine, the semantic layer (Beta), the MCP server for agents, the approval gate, access control and the audit trail are live. App Studio and Maestro, the assistant inside MaestroHub, are in the 5 November 2026 release as Beta, both by early access on request. The Knowledge Graph is in development.
Two ways. You can point your own MCP client, such as Claude or Cursor, at the MaestroHub MCP server. You can also use Maestro, the assistant inside the product (Beta, early access on request). In both cases the agent sees only what the person it acts for is allowed to see, and every action is recorded.
No. MaestroHub sits above the systems you already own. Ignition, your historian, your PLCs and your MES stay where they are. MaestroHub reads from them, writes back under permissions and audit, and keeps an operational window of history that you set: one day by default, and from release 3.0 up to 32 days per topic.
On your own infrastructure. The same codebase runs as a single binary on a laptop or at the edge, as a container, as a Siemens Industrial Edge app, or on Kubernetes at site level. Your data does not leave your network unless you send it.
Per site, not per tag. There are Foundation and Enterprise editions. Foundation and Enterprise licences are available for direct purchase. Implementation support can be scoped separately, and a paid Proof of Value is optional.
Just ask. The AI you already use connects your machines and systems, builds the pipelines and lays out your Unified Namespace, one source of truth for the whole factory.
Every site, one Knowledge Graph. Hover any point to explore.