FOR APPS THAT NEED SOMEWHERE TO KEEP THEIR DATA
A database and its API, in your cloud.
Create an Azure Cosmos DB store in your own subscription from one window, then switch on a governed API for each container. Your apps read and write it, and your AI reads it, under the workspace's rules.
New to OpenX? Key terms →
ONE CONTAINER · ITS OWN ROUTES
- Paging
- Continuation tokens, the way Cosmos pages
- If-Match
- A stale write is refused cleanly
- Batch
- Batch reads and batch transactions
- Audit
- Each write recorded, with Provenance on
- Access
- The workspace's access rules
Your data. Your Azure. Your API.
FROM AN EMPTY SUBSCRIPTION TO A WORKING API
Switch on an API per container.
A database from a window
Once your cloud is connected and the landing zone built, Environment > Databases creates a Cosmos DB account in your subscription. Nothing to paste.
Containers with a purpose
Create containers and declare what each one holds and what it publishes.
Routes when you want them
Each container can publish REST routes on the workspace API, with paging, safe concurrent writes and batch transactions.
Writes on the record
With Provenance on, each write through these routes is recorded: the document's hash and ETag, never the document itself.
Governed like everything else
Routes appear in the API Manager's Data Stores tab, by store and database, under the workspace's access rules.
Query it too
A warm query can read a container directly, and a later step can filter by the keys it read.
IF EVERY NEW APP NEEDS A BACKEND FIRST
For teams that would rather build the app than its backend.
App builders on OpenX
A place for app data (orders, lots, inspections, settings) without standing up a backend.
IT
The data sits in the company's own subscription and region.
Integration teams
No more writing a CRUD service and its access checks for every container.
NEXT TO COSMOS ON ITS OWN
The way Cosmos works, with your workspace around it.
Cosmos DB already has a native REST API, with continuation tokens and ETags. OpenX doesn't replace that. It puts each container's routes on your workspace API, under the workspace's access rules, record and delete protection, ready for your apps and AI.
- Store, API, rights, record, queries and AI access in one workspace.
- Protect from deletion keeps the store from being removed through OpenX.
- An AI connected over MCP can propose containers and routes for a person to accept.
WHAT TEAMS PUT IN IT
From a container to a working app.
A complete app backend
- 01A Cosmos store holds the app data.
- 02App Identity signs users in and the API Manager decides their reach.
- 03Licenses sells the plans.
Data plus telemetry
- 01Lots live in a Cosmos container.
- 02A Data Explorer step filters sensor data by those lot keys.
- 03One route serves the answer.
A schema an AI drafted
- 01An agent connected over MCP proposes containers and the routes they publish.
- 02A person accepts.
- 03A person deploys.
THE RECORDS TEAMS KEEP
App data next to operational data.
LIFE SCIENCES
Sample and lot records in your own region, with writes on the record.
MANUFACTURING
Inspection results and work orders next to machine data.
ENERGY AND BUILDINGS
Tenant and asset registers served to billing and maintenance apps.
Your data, your Azure, your API.
Create the store, switch on the routes, and build the app.
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.
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.
IoT →
IoT Hub and Data Explorer in your Azure, feeding queries, APIs and AI.
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.