A process engine, not a catalogue of templates.
In the analyst vocabulary, Dexon BPM belongs to the business orchestration and automation market — what Everest calls process orchestration and QKS calls an iBPMS. Most enterprise tools are products built around a fixed set of templates: you configure within what the vendor anticipated. Dexon BPM differs at the base — the boundary of what you can change is not what someone foresaw, but whatever can be modelled as a process.
The structural difference
The first configuration is quoted. The next two hundred are not.
You will keep the tool you choose today for five years, and in five years your structure, your services, your suppliers and the regulation governing you will all change. Each of those changes will be either a configuration your team makes in an afternoon, or a request to the vendor with a quote and a schedule.
| A closed tool | A process engine | |
|---|---|---|
| What can be changed | Whatever the vendor anticipated someone would want to change | Whatever can be modelled as a process |
| If you need something unforeseen | A request, a quote, a schedule — or waiting for the roadmap | It is modelled and published |
| Who does it | The vendor or a certified partner | Your team, from the browser |
| At the next update | Custom development must be retested | Configuration survives |
Three questions worth asking any vendor, ourselves included: Can my team change it without you? Is that configuration or development? Does it survive the next update?
The modules
Built in-house, natively integrated
These are not products from different vendors joined by an integration project. They share the same data model, the same CMDB and the same governance — which is why the inventory and the ticket live in the same record.
Designer
Where the whole chain is drawn — strategy, capabilities, services, offerings, processes, data and indicators — each link with its own editor, and a verifier that checks the result.
Workflow
Conditional routing, parallel tasks, dynamic approvers, deadlines on business calendars and append-only history — the same engine across every record type.
ETL & integration
REST API, scheduled and event-driven exchange with databases, files and web services, plus directory, email, Teams and discovery — with the authoritative source of every attribute on record.
IDP & document management
Version trees, permissions, retention, digital signature and custody — with document requirements enforced as gates the workflow will not pass without.
BI & KPIs
Scorecards under strategic objectives, targets by period, drill-down from the aggregate to the source record, and projection that never overwrites a measurement.
IT asset management
Agent-based discovery for Windows, Mac and Linux, network monitoring, licensing measured on real usage, disposal governance, and remote control recorded on the case.
Licensing
End users are not licensed
You license the base module and the management users — those who handle and operate. Your entire workforce, the other companies in the group and the third parties taking part in a case can all use the platform at no incremental cost.
The paradox worth checking with any vendor: if your goal is to increase self-service — that is, more people using the platform — then under a named or active user model, meeting that goal raises your bill. And that does not show up in the year-one proposal: it shows up at the year-three renewal.
Deployment models
The engine's proof
Dexon ServiceDesk is an implementation of the ITIL processes on Dexon BPM.
It is not a different product: it is a configuration. The ITIL processes are content on the engine, which is why an external auditor was able to certify them across twelve areas.
That is the most economical demonstration of our whole thesis. If the engine can carry an audited service desk, it can carry procurement, hiring, supplier management or any process with forms, approvals, deadlines and evidence.
See the twelve certified processes →The boundary, declared
What we do not claim
→LLM-based agentic automation in production. The methodology already defines the agent as an executor class — bounded scope, escalation criteria, evidence per intervention — and that is the framework our agent capabilities are being built into.
→Process mining discovery over external event logs. Every process produces a native event log, exportable to the mining tool of your choice; discovery over systems we do not run is your mining tool's job.
→A general-purpose app builder. The engine builds and runs governed processes with their forms, rules, data and integrations; if what you need is an arbitrary application with no process behind it, other tools fit better.
Test what it costs to change it
Pick one of your processes, with its real rules and its awkward exceptions. We configure it with you, live, so your team sees the true cost of a change — not just how the platform looks once configured.