BPA, workflow automation and RPA name three different purchases, and vendors keep the confusion alive. Buying the wrong layer costs months and tens of thousands — so here is how to tell them apart before comparing anything.
Zakaria El Asri11 min
What nobody says
RPA is not an automation solution. It is the symptom of a missing API.
In one sentence
The short answer
Camunda if you have a technical team and want processes you own (Apache-2.0, standard BPMN). Bonitasoft for the same logic with a French vendor. Appian or Pega for regulated case management at scale, with the cost that implies. Power Automate if you already pay for Microsoft 365. UiPath only when no API exists.
Framing
Three layers, constantly confused
The confusion is not innocent: a BPM vendor benefits from you believing you have a BPM problem. Here is the distinction that prevents the buying mistake.
Layer
What it does
Typical example
Time to implement
Workflow automation
Connects APIs, stateless
"New form → create CRM record → notify"
Hours to days
BPA / BPM
Stateful process: actors, approvals, audit
Insurance claim, onboarding, leave request
Weeks to months
RPA
Drives an interface for want of an API
Re-entering data in software with no machine interface
Days, then perpetual maintenance
Three distinct purchases. Lumyniq, 2026.
The three-question test. Does the process have lasting state — a case open for days? Does it involve several roles with sign-offs? Will you later need to answer "who decided what, when"? Three yeses: BPM. Two noes: a workflow tool suffices, for a fraction of the cost.
If you are unsure which layer you are in, start with our n8n vs Make vs Zapier comparison: most needs that present themselves as BPA are handled there, faster and for far less.
At a glance
The comparison
Tool
Layer
Licence
The right case
Camunda
BPM
Apache-2.0 (engine)
Technical teams wanting explicit, testable processes
Appian
Hybrid
Proprietary
Enterprises wanting one platform for processes and business applications
Pega
Hybrid
Proprietary
Processes with heavy regulatory load and complex arbitration
Bonitasoft
BPM
Open source (community edition)
European SMBs wanting BPM without depending on a US vendor
Microsoft Power Automate
Hybrid
Proprietary
Microsoft organisations, office processes and approvals
UiPath
RPA
Proprietary
Internal or legacy software with no API that you cannot modify
Automation Anywhere
RPA
Proprietary
The same cases as UiPath, if your IT function prefers its deployment model
Nintex
Hybrid
Proprietary
Organisations that must document processes before automating them
ProcessMaker
BPM
Open core
Approval processes on a constrained budget
Read on 17 August 2026 from official sites and repositories. No pricing: quote-based sales. Lumyniq, 2026.
BPM on an open-core model, oriented toward forms and approvals.
The right case: Approval processes on a constrained budget
Strengths
Lower entry cost than enterprise platforms
Open-core model for evaluation
Limitations
Less depth than the established players
Smaller community
Handle with care
The special case of RPA
RPA deserves its own section because it is sold as an automation solution when it is really an admission: the target software exposes no API, so a robot pretends to be a human clicking.
Sometimes that is the only option — a legacy business application you cannot modify, a supplier extranet with no machine interface, a system whose vendor no longer exists. In those cases UiPath or Automation Anywhere do the job, and do it well.
Check before buying RPA
Why
Does an API exist, even undocumented?
Often yes, and nobody asked the vendor
Would a file export/import do?
Less elegant, vastly more stable than a robot
Who maintains the robot in a year?
Every screen change breaks it
Does the ROI include maintenance?
Almost never — and that is where the saving disappears
The four questions that prevent permanent debt. Lumyniq, 2026.
The simple rule: look for the API first, including by explicitly asking the vendor of the software concerned — many have one they do not document publicly. Automate the interface only as a last resort, and budget the maintenance from day one.
When the real need is making systems talk that were never designed to, without a fragile robot in between, that is what Lumyniq does. Disclosure: we publish this site and do not appear in this comparison, because we are not a BPM platform vendor.
FAQ
Frequently asked questions — business process automation
Three different purchases, constantly conflated. Workflow automation (Zapier, Make, n8n) connects APIs: it is stateless, builds in minutes, and suits "when X happens, do Y". BPA or BPM (Camunda, Appian, Pega, Bonitasoft) handles stateful processes: multiple actors, approvals, deadlines, an audit trail — typically a leave request, an insurance claim, an onboarding. RPA (UiPath, Automation Anywhere) drives user interfaces because no API exists. Buying BPM to do what a workflow tool would have handled is the most expensive mistake in the category.