openX

FOR PEOPLE BUILDING APPS ON THEIR OWN DATA

Your app's backend, already in the workspace.

Data storage, sign-in, access, an API and billing are all capabilities you switch on in OpenX, with your data in your own Azure. Build your app in the framework you like, and let OpenX be the backend it calls.

New to OpenX? Key terms →

THE BACKEND · SWITCHED ON, NOT BUILT

Data
Cosmos DB containers with their own routes
Sign-in
Your own Entra or B2C directory
Access
API Manager rules on card rights, checked by the server
Queries
Saved queries as API routes
Billing
Plans on your own Stripe account

One workspace. Your Azure. Your app.

WHAT YOU WOULD OTHERWISE BUILD FIRST

Every piece of the backend, on one API.

A database per app

Cosmos DB containers in your subscription, each publishing REST routes with paging, ETag writes and batch transactions.

Sign-in for your users

Your own Microsoft Entra or Azure AD B2C directory, set up step by step in App Identity.

Access you can read

API Manager rules, judged on access cards, decide what each signed-in user reaches. Any caller can ask the API what it is allowed.

Answers as endpoints

Save a warm query over live data and it is a parameterised API route.

Plans and payments

Sell plans on your own Stripe account. A subscription grants the plan's rights, and a lapsed one removes them.

Identities for your jobs

Background jobs and integrations get their own identities, with certificates or federated credentials.

IF THE BACKEND IS THE SLOW PART

For builders who want to ship the part users see.

Internal app teams

Build the inspection app, the lot tracker or the supervisor view without a backend project first.

Software makers

Turn a tool into a product with sign-in, plans and access already wired.

Teams building with AI

Your AI reads the same API your app does, and proposes changes for a person to accept.

NEXT TO A BACKEND-AS-A-SERVICE

Not a separate backend. The workspace your data already lives in.

Backend services give you a database and an API, usually in their cloud. In OpenX the app's data, its users, its rights and its billing sit in the same workspace as your operational data, in your own Azure.

  • Store, sign-in, access, queries, billing and AI access on one workspace API.
  • The same access rules and AI-proposal review for the app as for everything else.
  • A query can filter live sensor data by keys from your app's own data.

APPS TEAMS BUILD

From an idea to a paid app.

A complete app backend

  1. 01A Cosmos container holds the app data.
  2. 02App Identity signs users in, and API Manager rules set their reach.
  3. 03Licenses sells the plans.
Databases →

A data product

  1. 01A warm query becomes an API route.
  2. 02Buyers sign in through your directory.
  3. 03A plan's rights open the route.
Licenses →

A supervisor app

  1. 01An OEE query runs over live line data.
  2. 02Supervisors sign in with their own accounts.
  3. 03API Manager rules on their access card decide which lines they see.
App Identity →

APPS ON OPERATIONAL DATA

The app, next to the data it serves.

MANUFACTURING

Inspection and work-order apps beside machine data.

LIFE SCIENCES

Sample and lot apps with their writes on the record.

ENERGY AND BUILDINGS

Tenant dashboards and billing apps over meter data.