FOR TOOLS WORTH PAYING FOR
Sell what you build, on your own Stripe.
Turn an app you built on OpenX into a product. Plans, prices and coupons sit in one window, payments run through your own Stripe account, and a subscription grants the plan's rights in your workspace.
New to OpenX? Key terms →
ONE PLAN · FROM PRICE TO ACCESS
- Plans
- Prices and coupons in one window
- Stripe
- Your own account, keys in your vault
- Routes
- Catalogue, subscribe, checkout, portal
- Rights
- Granted with the subscription, removed when it lapses
- Stats
- Monthly recurring revenue and subscribers
A subscription is a set of rights.
FROM PLAN TO PAYING CUSTOMER
Plans, payments and access in one place.
Plans, prices and coupons
A licence is what you sell. Manage Licenses holds its plans and prices, coupons, subscribers and the Stripe connection.
Health and stats beside them
A Health tab checks the setup. A Stats tab shows subscription numbers such as monthly recurring revenue.
Your Stripe, your vault
The workspace connects to your own Stripe account, and the keys are kept as references in your own Key Vault.
Routes for your app
A plan catalogue, read, subscribe and cancel, Stripe Checkout and customer-portal sessions, and a verified Stripe webhook for each licence you sell.
A subscription is a set of rights
A subscription grants the plan's access rights to the user, and a lapsed one removes them.
Subscription events as data
A Stripe Events node forwards a summary of the events you pick (type, time, ids, status) to an IoT Hub connection. Never customer details or amounts.
IF YOUR INTERNAL TOOL COULD BE A PRODUCT
For teams ready to charge for what they built.
Teams turning a tool into a product
Inside the enterprise or for its customers, without wiring billing, entitlements and access checks by hand.
Industrial and life-science software makers
Subscription access to dashboards, queries and APIs, with no separate billing stack.
Finance and operations
Recurring revenue and subscriber numbers next to the product they pay for.
ON TOP OF STRIPE, NOT INSTEAD OF IT
Keep your Stripe. Gain the routes and the rights.
OpenX is a layer on your own Stripe account. It is not a billing engine and not a merchant of record, and it does not handle tax. What it adds is everything around the payment: the plans window, the routes your app calls, and the rights a subscription grants.
- Build the app, sign users in, sell it and see the revenue in one workspace.
- Licences use the same access rights as the rest of the workspace.
- An AI connected over MCP can propose plan and price edits for a person to accept.
WHAT TEAMS SELL
From a query to a paid product.
A data product in a box
- 01A warm query becomes an API route.
- 02App Identity signs the buyers in.
- 03Licenses sells a plan whose rights open that route.
Subscription events next to usage
- 01The Stripe Events node picks activations, cancellations and failed payments.
- 02A summary of each lands in an IoT Hub connection, next to product usage.
- 03Revenue numbers stay in the Stats tab.
Pricing changes an AI drafts
- 01An agent connected over MCP proposes a new plan and coupon.
- 02A person accepts.
- 03A person deploys.
WHAT GETS SOLD
Your data, as a subscription.
EQUIPMENT MAKERS
A monitoring subscription per customer site, with the data and the licence in one workspace.
LIFE SCIENCES
Licensed access to a data product, with the plan's rights granted and removed with the subscription.
ENERGY AND BUILDINGS
A paid, tenant-facing energy dashboard backed by meter queries.
Built it? Sell it.
Plans, Stripe, routes and rights, in the workspace your app already runs in.
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.
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.