/ the platform
One platform. One execution loop.
What is available today, what selected customers are previewing, and where the platform is going. Every module ends in the same place: an action someone owns.
/01 — the catalogue
What is in the box, and what is coming.
We release modules continuously. Planned modules are not available yet; we list them so you can see where the platform is going.
Available today
10
Released. Every customer gets these modules.
Execution
Insight
Foundation
In preview
13
Built and in use with selected customers ahead of general release.
Governance
Insight
People & organisation
Foundation
On the roadmap
31
Planned. Not available yet, and listed without a delivery date.
People & organisation
Quality
Production
Strategy
Collaboration
Facility & EHS
More
This list is generated from the product's own release flags, so it is always current. When a planned module is released, it is included in your plan.
/02 — how it works
Everything ends in an action.
Whatever a module records, it leaves the same way.
01 · Capture
Record it where it happens
A decision in the morning meeting. A finding on a walk. A document that is due for review. A request that needs a signature.
02 · Assign
It becomes an action
One owner, one due date, one site. Not a line in a protocol nobody opens again.
03 · Execute
Work it in the open
To-dos, attachments and the conversation live on the record. Overdue is visible to everyone who should see it.
04 · Verify
Done is verified, not declared
Where it matters, an approval or an e-signature closes the loop, and the record keeps the trail.
05 · Learn
See what is open, late and improving
Insights dashboards and the opexONE assistant read the same records, by site and by line.
That loop is the product. Every module we add plugs into it. None of them ends in a PDF.
/03 — the promise
Works out of the box. Really.
Every module we release ships with opinionated defaults built from operations-excellence practice: statuses, workflows, roles, and KPIs that match how plants actually work. You don't configure opexONE into usefulness; you sign in and start. That's not a limitation. It's the product.