FOR PLANTS WITH DATA STUCK IN THE HISTORIAN
Your device data, in your Azure, ready for AI.
Set up an Azure IoT Hub and an Azure Data Explorer cluster in your own subscription from one window. Device data then flows into queries, APIs and the AI your team uses.
New to OpenX? Key terms →
DEVICE TO ANSWER · ONE WORKSPACE
- IoT Hub
- Your devices connect here
- Data Explorer
- Their data lands here
- Warm query
- The question you keep asking
- API route
- The answer, for your apps
- MCP
- The answer, for your AI
From device to API in one workspace.
FROM THE FIRST DEVICE TO THE FIRST ANSWER
IoT Hub and Data Explorer, set up for you.
Set up from one window
Environment > Data & IoT Fabric provisions the hub and the analytics cluster in your own Azure subscription.
Provisioning you can watch
The setup window updates while it is open. If the analytics cluster fails, it tells you what to do next.
A device's credentials in one place
Each connection's panel holds its connection string, testing tokens labelled with their expiry, and key regeneration that asks before it acts.
A simulator to start with
Try the pipeline with a simulated device that holds only its own key.
Changes an AI can propose
An AI connected over MCP proposes IoT changes through a small set of named settings, and a person accepts them.
Feeds everything else
Device data flows into warm queries, API routes and your AI's view of the workspace.
IF YOUR DEVICE DATA HAS NOWHERE USEFUL TO GO
For teams whose data should be doing more.
Plant and OT/IT leads
Get data out of the historian and into your own cloud, not a vendor's.
Teams planning for life after Azure IoT Central
Microsoft is closing IoT Central to new applications. OpenX builds on IoT Hub, in your own subscription.
Device makers and integrators
Keys and testing tokens in one place, so pilots lose less time to expired or regenerated credentials.
Data teams
Device data queryable and served as an API, without building the ingestion stack by hand.
NEXT TO YOUR EDGE AND BROKER TOOLS
Keep your plumbing. Put its data to work.
Edge gateways, brokers and DataOps tools move plant data well, and OpenX works alongside them. OpenX is where that data becomes queries, APIs and apps an AI can help build, in your own Azure.
- IoT Hub and Data Explorer, set up from one window, in a workspace that also serves the data as an API and to AI.
- A device's keys and testing tokens together on its connection panel.
- Device data sits under the same access rules as everything else, and cloud changes wait for Deploy.
WHAT DEVICE DATA TURNS INTO
From a sensor to a decision.
Device to dashboard to AI
- 01Devices stream into IoT Hub.
- 02A warm query computes OEE, and the API Manager serves it.
- 03An AI reads it over MCP.
A reading on the record
- 01A threshold query finds an excursion.
- 02A QA app you build on OpenX records a correction with a reason.
- 03Provenance keeps the record in your storage.
Sell the data
- 01Device data is served through API routes.
- 02Licenses sells a monitoring plan per customer site.
- 03The plan's rights open those routes.
WHERE THE DEVICES ARE
Plants, labs and buildings.
MANUFACTURING
SCADA, MES and historian data in one workspace.
ENERGY AND BUILDINGS
Meters, building systems and utility feeds, brought together for cost allocation.
LIFE SCIENCES
Cleanroom and equipment monitoring, with traceability.
Connect a device. Ask it anything.
Set up IoT Hub and Data Explorer in your Azure, start with a simulator, and serve the answer.
GO DEEPER
MORE OF OPENX
AI governance →
Over MCP, AI proposes and a person accepts. Only a person deploys.
OpenX MCP Server →
A few tools let any MCP-capable AI read your workspace and propose changes to it.
API Manager →
Your workspace is already an API. Decide who may call it and what each caller reaches.
Warm queries →
Save a question over live data and serve the answer to dashboards, apps and AI.
Provenance →
A record you can prove, kept in your own cloud, with corrections and signatures.
Your cloud →
Connect your Azure, build the landing zone, and the rest of OpenX runs inside it.
Databases →
A Cosmos DB store in your subscription, with a governed API for each container.
App Identity →
Your own sign-in directory, identities for your jobs, and access in one window.
Licenses →
Sell what you build on your own Stripe, and turn a subscription into a plan's rights.
Communications →
Send mail through your own relay, with the password in your vault and sends on record.
App building →
Data, sign-in, access, an API and billing: your app's backend, already there.