ProcessMaker review: the BPM tool that became Decisions

Disclosure: Tallyfy competes with ProcessMaker, and with the Decisions platform it became. I’ve fenced the Tallyfy comparison into the final section, so read that part knowing my side; everything before it is straight analysis.

Here’s the single fact that reshapes any 2026 evaluation of ProcessMaker: the website doesn’t go to ProcessMaker anymore. Type processmaker.com into a browser and you’re redirected to decisions.com, because the two companies merged in late 2025.

So the real question isn’t whether ProcessMaker is good software. It’s whether you’re buying ProcessMaker at all, or the combined Decisions platform that now carries its name.

Where I sit in this: I run Tallyfy, which competes with both, so the closing section has my thumb on the scale and I’ll flag it when we get there. Everything up to it sticks to what ProcessMaker is, what it does well, and where it bites. For how the broader category lines up, the guide to BPM platforms gives you the map.

Where ProcessMaker started, and where its URL now sends you

ProcessMaker built its name as open-source BPM and workflow software, and the founding story is the bootstrapped kind. Co-founder Brian Reale has described a stretch where no one took a salary for the first three years and investors kept telling the team it would never be fundable. The company started in South America, then around 2017 built out a proper US presence and rebuilt the platform, eventually basing itself in Durham, North Carolina. Its first major outside capital arrived late: a 45 million dollar investment from Aldrich Capital Partners in February 2021. Then, in November 2025, ProcessMaker merged with Decisions, a rules-engine and orchestration vendor, into a single business that now runs under CEO Giles Whiting. ProcessMaker brought AI-enriched workflows, low-code development, and document processing; Decisions brought a rules engine, process orchestration, and case management.

What ProcessMaker is good at

Strip back the merger noise and ProcessMaker’s core competence is clear: it builds low-code workflows for people who aren’t full-time developers, and it pairs that with intelligent document processing, which matters a lot in paperwork-heavy work like lending or admissions. The drag-and-drop designer is the part long-time users praise most. Its open-source heritage is a real asset too, because organizations with infrastructure constraints or data-residency rules get self-hosting options that pure-SaaS vendors don’t offer. And the Decisions side now layers in a mature rules engine, so logic that ProcessMaker used to handle thinly, branching decisions, policy checks, case routing, has a stronger home. The current decisions.com pitch (“Orchestrate instantly. Innovate endlessly.”) sits alongside a customer wall that names the likes of Lockheed Martin, University of Virginia, Genentech, and Sony Music. For a buyer who wants workflow and document handling and decision logic under one roof, that combination is the draw.

For a team weighing the commercial product against the open-source edition, that fork is worth thinking through early, because the self-hosted path trades the convenience of managed hosting for control and a heavier operations burden. Mind you, “open source” never meant free to run at scale.

What reviewers flag most

Now for the rough edges, and there are a few well-documented ones. A sourcing note first: the big review sites wall their pages off from bots, so rather than lift individual quotes I’ll describe the criticisms that come up over and over. No invented reviewers.

The complaint I see most is that the interface feels dated.

It works, but it doesn’t have the polish buyers now expect after living in modern SaaS tools, and that perception shows up across forums and writeups.

Second is pricing friction in the exact markets where ProcessMaker built its early base. The product grew strong in Latin America, Africa, and parts of Asia, and the sales-led commercial pricing can be a tough sell to mid-market teams there once they outgrow the entry tier. Third, reporting and analytics lag the enterprise pack, so teams that need rich dashboards often bolt on something else.

And fourth, the freshest unknown: the Decisions merger is only months old, so the combined roadmap, the migration path for existing ProcessMaker customers, and which capabilities get priority are all still settling. None of that makes ProcessMaker a weak product. It makes it a maturing one, mid-transition.

Who ProcessMaker fits, and who it frustrates

Here’s the honest split.

ProcessMaker fits a regulated institution, a bank, a credit union, a university registrar, that needs low-code workflow and document processing together, can negotiate enterprise pricing, and values a vendor with a long operating history and self-hosting on the table. It’s a natural fit where the existing stack already leans on its open-source edition or self-hosted deployments, and where the new Decisions rules engine answers a decision-management gap the team actually has. For that buyer, the combined platform is more capable than it was a year ago.

It frustrates the team that wants a clean, modern interface their operations staff pick up without training, or a price they can read on a web page without a call. We’ve watched enough buying cycles to know the install base a vendor bragged about ten years ago says little about whether its roadmap still has momentum. So if you’re a small or mid-market team that wants to skip implementation services and just run a process next week, the weight here works against you, and a lighter tool will get you there faster.

ProcessMaker alongside Tallyfy

From here on, read me as an interested party. ProcessMaker, now Decisions, and Tallyfy overlap on the words “workflow” and “automation” but chase different buyers. ProcessMaker is an enterprise BPM and orchestration platform with low-code development, document processing, a rules engine, and a self-hosting heritage. Tallyfy is a workflow execution product for operations teams: a checklist-style interface, conditional logic with no code, and no platform to stand up before you run a process.

In our conversations with teams shopping for workflow software, the worry we hear most about an acquired vendor is blunt: whose roadmap survives the merger?

So the contrast is about weight versus reach. ProcessMaker’s edges are document processing depth, decision-management via the Decisions engine, and self-hosting for constrained environments. Tallyfy’s edges are a fast start for non-technical staff, live status anyone can read, and a live Model Context Protocol server that lets an AI agent drive a real process over an open standard rather than a bespoke build. On price, Tallyfy lists its per-seat rate on the website, where ProcessMaker’s number now lives behind the Decisions sales team. The fair read is which buyer you are. A bank wiring document-heavy approvals into one governed platform may want ProcessMaker. A fifty-to-five-hundred-person ops team that needs a process running reliably wants something lighter.

Want the feature-by-feature version and notes on switching? The ProcessMaker alternative page lays them out side by side. I’m keeping this one at altitude. If you’re still comparing, more of our BPM platform walk-throughs cover the field, the Nintex review looks at another long-running BPM player with complicated ownership, and the Camunda review covers the developer-first end.

Frequently asked questions

The verdict on ProcessMaker

ProcessMaker is a capable, document-strong BPM platform that just changed shape. If you’re a regulated institution that wants low-code workflow plus document processing plus decision logic, and you can work with sales-led pricing and a vendor mid-merger, the new Decisions platform is more capable than ProcessMaker was alone, and the open-source heritage still buys you deployment flexibility most rivals can’t match. If you’re a leaner team that wants a modern interface, a price on a web page, and a process live this week, the dated UI and the implementation weight will slow you down. The merger is the headline to digest before you sign anything: judge what ProcessMaker became, not the open-source reputation it built a decade ago.