Intelligent business process management, on one governed engine.
iBPMS — intelligent business process management suite — is the name QKS Group uses for the market of platforms that combine executable BPMN, low-code configuration, integration, analytics and embedded AI. It is the same competitive space Gartner evaluates as business orchestration and automation technologies and Everest Group as process orchestration products: the names differ by firm, the shortlists largely overlap. That combination — one engine executing governed processes with intelligence inside them — is what Dexon BPM has been for two decades.
The term and the brand
We call it Executable Business Architecture. In this market, it is an iBPMS.
Our category is Executable Business Architecture, because what differentiates Dexon BPM is not that it manages processes — every suite in this market does — but that the processes it runs are objects of a governed architecture: each one linked to the capability it serves, the service it delivers, the data it consumes and the indicator that verifies it. If you arrived with the iBPMS vocabulary, this page is the translation.
The word doing the work in the category name is intelligent, and it deserves precision. In Dexon BPM the intelligence is embedded in the governed process: classification, prediction and grounded answers run as activities of the flow, under the same audit trail as every other step — and the AI capability was assessed externally within the PinkVERIFY certification, not merely claimed. Intelligence bolted on beside the process is a copilot; intelligence inside the governed process is an iBPMS.
The mapping
What this market expects, and where it lives in Dexon BPM
The capabilities that define the category, and where each one lives in Dexon BPM.
Executable core
Executable BPMN →
Processes modelled and executed on the same engine: states, transitions, rules, concurrent work — every path ends in a declared outcome or a governed exception.
People in the loop →
Assignment by role, group, calendar and workload; approvals with real authority rules; escalation routes that act before the breach.
Service levels as clocks →
Deadlines computed against work calendars and service windows, validated against real cases before going live.
Intelligence embedded
AI under governance →
Classification trained on your history, deadline-risk prediction and grounded answers — as activities of the process, leaving auditable evidence, assessed externally within PinkVERIFY.
Analytics on live records →
Indicators computed over the operational records of the processes themselves, with drill-down to the case — not a warehouse bolted on.
Data as part of the flow →
Business entities captured and consulted per activity, with mandatory fields per state — the process and its data are one system.
Low-code and governance
Configuration, not development →
Processes, forms, rules and integrations configured on the engine by business-and-IT teams; the two hundred changes after go-live do not wait for a vendor.
Enterprise connectivity →
A REST API and a native integration engine move data in both directions; the systems you already run stay, and the process orchestrates them.
Governance of the platform →
Profiles with deny-by-default, approval dates and owners on every process, and an unalterable event log per case.
See one process run end to end
Bring a process that crosses systems, documents and people. We will show it modelled, executed, measured and governed on one engine — with the AI working inside it, not beside it.