Where IBM Business Automation Workflow costs more than self-hosted Flowable, and where it does not
If you are facing a Cloud Pak for Business Automation renewal, the license and platform line item is the one that goes away when you move to Flowable's Apache-2.0 engines. The engines themselves carry no license fee, but that does not make the move cheaper overall. The cost moves from the vendor invoice into your own budget: rebuilding process and case logic in BPMN and CMMN, building the user interface that IBM's coaches and case UI provided, running the hosting and databases, and paying for the people who operate them. Ask your renewal contact to itemize what the current contract covers, including the WebSphere or OpenShift platform beneath Cloud Pak, so you can see exactly which costs disappear and which reappear elsewhere.
Flowable's commercial editions, including Flowable Work, Engage, Orchestrate and Design, are optional. They are built on the same engines and add low-code modeling, visual debugging, security controls, monitoring and governance. Professional services and partners are also offered separately. If your team lacks the skills to build the UI or run the platform, these are the paths to compare, but you do not need them to run the open-source engines. Treat them as line items to price on their own, not as a default assumption that replaces the IBM license.
No price is given here for either IBM or Flowable. Request written quotes that separate the license or subscription fee, the platform infrastructure, one-time migration and rebuild work, recurring hosting and upgrade effort, and support. Confirm with Flowable which edition, if any, includes the tooling your authors need, and confirm with IBM which components of your current estate would still be licensed during a parallel run. The gap between those two quotes, measured over the period you plan to run both systems, is the number your steering committee should decide on.
Which cost components move when you leave IBM for Flowable
This table lists each cost component of running IBM Business Automation Workflow and of running self-hosted Flowable, with who is paid, whether the cost is one-time or recurring, and what drives it up or down. Use it to build a like-for-like comparison from your own quotes and contracts, not from list prices. The main takeaway is that the licence line often moves less than the rebuild, UI and skills lines, so those are the lines to scope first.
| Cost component | What changes when you move to Flowable | One-time or recurring, and what drives it |
|---|---|---|
| IBM licensing and subscription | Cloud Pak for Business Automation and BAW entitlements stop renewing at exit, after any notice and run-off terms in your contract. | Recurring until exit. Driven by the metric in your agreement, such as user or processor counts, and by the renewal date. Confirm the notice period with IBM. |
| WebSphere or OpenShift platform beneath Cloud Pak | OpenShift or WebSphere nodes can be retired only if other workloads do not depend on them. Otherwise the cost stays and only the BAW share is removed. | Recurring infrastructure and support. Driven by shared cluster use, node count and any Red Hat or WebSphere subscriptions you hold separately. |
| Flowable engine licence | Flowable open source is Apache-2.0 licensed, so the engine itself carries no licence fee. Commercial Flowable editions add low-code modeling, monitoring and governance. | Zero for open source. If you buy a commercial edition, it is recurring and driven by the products and seats you choose. Ask for the written quote. |
| Servers, containers and databases | Flowable runs as a Java service in Tomcat, Spring Boot or containers, on databases such as PostgreSQL, MySQL, Oracle or SQL Server. | Recurring. Driven by node count, async executor load, database edition and backup retention. Your existing database licences may already cover part of this. |
| Rebuild of process and case logic | BPMN processes are redrawn in BPMN and cases in CMMN, with DMN decisions re-expressed. Coaches and toolkit artifacts do not carry over as-is. | One-time. Driven by the number of process apps, case solutions and decision tables, and by how much custom Java or toolkit code they contain. |
| UI development | Coaches and the BAW Process Portal are replaced by a UI you build or buy, because Flowable's open-source edition leaves out the authoring and task UIs. | One-time build, then recurring maintenance. Driven by the number of user-facing screens, forms and the front-end stack you choose. |
| Implementation, migration and in-flight instances | Work includes draining running instances, migrating data and running parallel operation until cutover. | One-time. Driven by instance volume, integration count and the cutover window. Ask each bidder to scope these as separate line items. |
| Support and upgrades | Open-source users rely on the community forum, paid professional services or partners, and their own upgrade testing. Flowable 8.0.0 changed the Spring and JSON baseline, so upgrades need regression testing. | Recurring if you buy support or retainers, plus internal effort for each upgrade. Driven by the support tier and the number of Flowable versions you run. |
| Internal skills and operations | Your team takes on engine operations, security patching, monitoring and on-call that IBM previously carried under subscription. | Recurring staff time. Driven by the team size, the on-call model and how much of the operations work you outsource. |
What moves the comparison most for your estate
Six factors decide whether a self-hosted Flowable estate costs less than staying on IBM Business Automation Workflow. Each one shifts where the spend lands, from licensing and platform fees to engineering time and operations. Size them against your own estate before you compare quotes.
Number of process and case applications
Each process app, toolkit and case solution you rebuild is engineering work that IBM's authoring environment currently does for you. Flowable's engines take BPMN, CMMN and DMN models directly, so the count of applications mostly drives rebuild effort and UI work, not licensing. Ask for an inventory that separates shared decision logic from one-off processes. Expect the rebuild cost to rise with the number of distinct user interfaces you must replace.
Process instance volume and async jobs
Instance volume and timer or async job load determine how many engine nodes, database capacity and tuning you need. Flowable's async executor coordinates nodes through lock owners and lock expiration times stored in the database, so a larger cluster adds database write load. Ask your IBM contract team how licensing scales with capacity, and ask the Flowable partner to load test your peak timer load before sizing the platform.
Database and high-availability requirements
Flowable supports H2, MySQL, Oracle, PostgreSQL, DB2 and Microsoft SQL Server, so you can often keep the database standard your DBA team already runs. The main recurring cost is the high-availability design you must operate yourself: replicated databases, redundant engine nodes and backups. Confirm which database licenses you already hold, and whether your DBA team will own patching and failover for the engine schema.
Need for commercial low-code and monitoring
Flowable's commercial products add low-code modeling, visual debugging, security controls, monitoring and governance on top of the same engines. If your business analysts rely on IBM's authoring and monitoring tools, price a commercial Flowable edition or budget for building an operations console yourself. The open-source edition includes a community forum, while professional services and partners are sold separately. Decide this before you estimate UI effort, since it changes the license line and the build line together.
Identity integration with the directory
Flowable lets you replace its identity management by implementing the IdmIdentityService interface, with an LDAP reference implementation provided. Connecting to your directory, SSO and role model is therefore custom integration work, paid once and maintained with each upgrade. Estates that already expose groups through a standard directory will find this cheaper than estates with bespoke role logic in IBM's Process Admin Console. Confirm which roles and delegation rules must be reproduced before scoping.
In-house Java and Spring skills
Flowable runs embedded in Spring, servlet containers or as a standalone REST service, and Flowable 8.0.0 moved to Spring Boot 4 and Spring Framework 7 without backward compatibility for Spring Boot 3. Teams with strong Java and Spring skills carry upgrades in-house, while teams without them pay for partner support on every framework upgrade. Ask whether your engineers can own dependency upgrades on the Flowable 8.0.0 line and what a partner would charge to run them.
What Flowable does not bundle that IBM does
Flowable's open-source edition is a set of engines: BPMN process execution, CMMN case management and DMN decision rules, exposed through Java APIs and a REST API. The Flowable 7.0.0 release notes record that version 7 removed the UI applications and the form and content engines. Work that IBM Business Automation Workflow ships as part of its suite therefore moves onto your project. Before you compare line items, list every IBM component your teams use today, then mark whether each one has an open-source replacement in Flowable, a replacement you must build, or a gap you will close by buying a Flowable commercial product or a partner's service.
The gaps fall into five groups: process and case authoring tools, task and case user interfaces, forms, content storage for case documents, and monitoring dashboards. Each group creates a build, buy or partner decision with its own cost. Building means engineering time for front ends, form rendering, document handling and operational dashboards that recur as long as the system runs. Buying means licenses, which Flowable sells as commercial editions built on the same engines. Partnering means professional services, which Flowable offers separately from its open-source edition. Ask each vendor or partner to price these components in writing against your written scope, and confirm which features are in the commercial product you would license.
Confirm two technical points early, because they change the build effort. The Flowable docs list the database types the engine supports, and the Spring Boot docs describe an actuator endpoint at /actuator/flowable for monitoring running processes, which covers some but not all of the operational visibility IBM provides. Also confirm whether your identity source can be connected through the identity service interface Flowable documents, since the LDAP implementation is a reference rather than a finished integration. Each of these items is a line in the build-or-buy estimate, and skipping them is the most common way an engine-based project overruns its planned scope.
How to build the cost comparison with your own numbers
This sequence turns a vague sense that licensing is expensive into a five-year comparison built from your own IBM quotes, your infrastructure bills and your own rebuild estimates. Every figure in the final model should trace back to a document your organization holds or a quote you have requested.
Inventory current IBM licenses and renewal dates
Collect every IBM Business Automation Workflow and Cloud Pak for Business Automation line on your current order, including entitlement type, licensed metric, core or user counts, support tier and renewal date. Include the WebSphere, Db2, OpenShift and storage subscriptions that sit underneath the product, because they often renew on different dates. Ask your IBM account team to confirm the lifecycle dates for your exact version. The step is done when one table lists each contract line, who pays for it and when it recurs.
Map the platform and infrastructure beneath IBM
Document the runtime that carries the product today: WebSphere or container clusters, OpenShift subscriptions, database licenses and servers, storage, backup tooling, monitoring and the staff hours spent operating them. Separate costs that disappear with a migration from costs that stay, such as shared cluster capacity used by other applications. Note which lines are paid to IBM, to a hosting provider, to a reseller or to your own staff. The step is done when every platform cost has an owner and a recurring or one-time label.
Catalog process apps, toolkits and case solutions
List each process application, toolkit, coach, case solution, integration and custom Java component, with its owner, business volume and number of active process or case instances. Flag apps that are candidates for retirement, that rarely run, or that duplicate another app. This inventory sets the rebuild scope and tells you how much work is BPMN and CMMN modeling, how much is UI replacement and how much is integration. The step is done when every app has a row, a complexity note and a decision of rebuild, merge or retire.
Estimate rebuild and UI work per app
For each app, estimate the effort to redraw the process in BPMN, the case model in CMMN, the decision logic in DMN, and the user interface you will build because IBM coaches will not carry over. Ask two or three implementation partners to quote the same inventory against a written scope, so the figures are comparable. Record which costs are one-time project effort and which recur as change requests. The step is done when each app has a rebuild estimate with its assumptions written down.
Price the Flowable runtime, database and capacity
Price the open-source Flowable engines at zero license cost, then add the components you will pay for: Java application hosting, the chosen database and its licensing if you use a commercial database, Kubernetes or virtual machine capacity, load balancing, observability, backup and identity integration. Flowable's commercial editions are an optional line, so price them separately only if you are considering one. Confirm the supported database and version list with Flowable before you assume a database choice. The step is done when each infrastructure line is quoted or sized and tagged as one-time or recurring.
Choose and price the support tier
Decide what production support you need and who provides it: an internal platform team, a professional services or partner contract from Flowable, or an independent provider. Ask each option for a written scope covering incident response, upgrades, security patches and hours included, and record the annual fee or retainer as a recurring line. Note that the open-source license itself carries no fee, so support and staffing are the main recurring costs to model. The step is done when you have a support option per scenario and a documented assumption about in-house skills.
Model a parallel-run period
Plan a period in which IBM and the new platform run side by side, including duplicate infrastructure, duplicate licensing where contracts overlap, and the cost of keeping staff on both systems. Ask IBM whether you can shorten or reduce a contract term to cover this window, and record any penalties. Plan how in-flight instances will drain from the old system. The step is done when the overlap months and the duplicated lines are written into the model with the contract terms that govern them.
Compare five-year totals and test sensitivity
Build a five-year table that places the IBM path and the Flowable path side by side, with one-time and recurring costs in separate rows and a total for each year. Then vary the largest assumptions, such as rebuild effort, support tier and renewal price changes, to see which ones change the outcome. Share the model with finance, security and the platform team so each can challenge its own lines. The step is done when every number traces to a quote, a contract, an environment measurement or a named assumption, and the open questions are listed for the next conversation with IBM and with implementation partners.
Questions buyers ask before comparing IBM BAW and Flowable costs
What does a cost comparison between IBM BAW and self-hosted Flowable actually include?
A fair comparison covers each cost component separately rather than one licence line against zero. On the IBM side, the Cloud Pak for Business Automation licence, the WebSphere or OpenShift platform beneath it, and the cluster capacity to run both are recurring costs. On the Flowable side, the engine itself is Apache-2.0 licensed, so the main costs are infrastructure, the one-time rebuild of processes and cases, the UI you build yourself, database operations, and support. Ask your team to price each line on both sides before comparing totals.
Can an internal team run Flowable without an outside partner?
It can, provided the team has the skills and capacity to own the engine in production. Flowable's open-source edition ships the BPMN, CMMN and DMN engines and REST APIs, but it leaves out the UI applications and authoring tools that IBM bundles, so your developers will build those. Flowable's open-source community forum is available, while professional services and partners are offered separately. Decide early which parts your staff will own and where you want outside help for design, hardening or incident response.
How long does a rebuild take, and what drives the duration?
No duration figure is supplied for this comparison, so treat any number you hear as a claim to verify against your own inventory. The main drivers are the number of process apps, toolkits and case solutions you run, how many processes need redrawing in BPMN and cases in CMMN, how many custom coaches or integrations must be replaced with your own UI, and how many in-flight instances must be drained or migrated. Ask for the timeline to be tied to a written inventory and a fixed scope.
What skills does the team need to run Flowable in production?
Plan for Java, Spring and database skills first. Flowable runs embedded in Java SE applications, servlet containers, Spring applications or Java EE servers, or as a standalone service over HTTP through its REST application. Its Spring Boot starters support Spring Boot 4.x, and the async executor coordinates nodes through lock records in the database, so your team needs to understand clustering and database tuning. Kubernetes skills matter if you deploy the engine as a container service alongside your other workloads. Confirm each skill gap against your current staff.
Do Flowable's commercial editions change the cost comparison?
Yes, they change the licence line, but not the underlying engines. Flowable sells commercial editions, including Flowable Work, Engage, Orchestrate and Design, built on the same engines and adding low-code modeling, visual debugging, security controls, monitoring and governance. If your gap is mainly the authoring UI and governance tooling, a commercial edition may cost less to build than writing it yourself. Request a written price for the specific products and modules you need, and compare it against your own build estimate on the same basis.
What should a fixed-scope quote from a partner include?
A written, fixed-scope quote should list the inventory you agreed to, the processes and cases in scope, the UI and integrations to build, the database and cluster configuration, the migration approach for in-flight instances, testing, handover documentation and any post-go-live support. Ask which items are one-time and which recur, such as upgrades, patching and monitoring. DeployOpen plans, implements, hardens, backs up, upgrades and documents self-hosted platforms in your own infrastructure, and quotes follow from the written scope. Confirm acceptance criteria before work starts.
Does moving to an open-source engine remove the need for licensing review?
No. Apache-2.0 licensing applies to the Flowable engine code, but your contracts with IBM, your OpenShift or WebSphere subscriptions, and any Flowable commercial edition you adopt each carry their own terms. Ask your legal and procurement teams to map every current agreement with end dates, notice periods and exit obligations before setting a migration timeline. This also keeps the comparison honest, since some subscriptions may be needed during a parallel run.
How the transition period changes the first-year totals
The first-year total is rarely the steady-state cost, because a parallel run keeps the IBM Business Automation Workflow licenses and the Flowable infrastructure active at the same time while in-flight instances drain and cutover happens. Both cost lines run together for that period, so the planning question is how long the overlap lasts and what each side bills for during it. Ask the IBM account team how the Cloud Pak for Business Automation entitlement and the WebSphere or OpenShift capacity are priced if you need to keep them beyond a planned end date, and whether any reduction can be made mid-term. Then ask your own platform team what the Flowable side costs during overlap: database instances, Kubernetes capacity, monitoring and backup for a second estate. Neither figure should be assumed to fall away on the day cutover starts.
Flowable's async executor shapes how instances move between the two estates. It runs timers and asynchronous jobs from a thread pool and coordinates nodes through lock owners and lock expiration times stored in the database, so expired locks are recovered and picked up by other nodes. In planning, this means the number of Flowable nodes you run during overlap, their database connectivity and the lock expiration settings directly affect how quickly migrated timers and jobs are processed and whether duplicate work is avoided. Ask the implementation partner to specify the async executor configuration, the node count for the parallel period and a test that confirms lock recovery under node failure before any production instance is moved.
Treat the overlap window as a scoped deliverable with exit criteria, not an open-ended run. Agree in writing which process definitions are retired first, how running instances are counted and reconciled between the two systems, and what evidence shows that no timers or jobs remain on the IBM side. Ask for a drain plan that names the owner of each decision and the date at which IBM support or license reductions are requested. Any estimate of the transition effort should come from the written scope, with the effort and fees itemized so that overlap time is visible as its own line rather than hidden in the rebuild total.
How DeployOpen scopes a fixed-price Flowable implementation
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside the client's own infrastructure. For a cost comparison between IBM Business Automation Workflow and self-hosted Flowable, we start with a written scope that names every cost component, so the reader can compare like with like before any work begins.
How we scope
- We inventory the current IBM licensing, Cloud Pak, WebSphere or OpenShift components and the people who run them today.
- The written scope lists which process models, case types, decision tables and integrations move to Flowable, with deliverables agreed up front.
- We confirm with you which Flowable edition, database and hosting target fit your environment, and which costs remain outside the scope.
How we build
- We rebuild BPMN processes, CMMN cases and DMN decisions on Flowable's engines and test them against the business rules in the current estate.
- We build the user interface and integrations that IBM's bundled tooling provided, and document the design choices made for each.
- We harden the deployment, including the async executor configuration for multi-node clusters, identity integration and backup procedures.
How we hand over
- Handover includes runbooks, architecture documentation, configuration records and the test evidence gathered during the build.
- We plan how in-flight instances on the old platform drain or migrate, and document the cutover steps agreed with your team.
- Your staff receive the documentation and working knowledge needed to operate the platform after the engagement closes.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer, so the platform keeps pace with Flowable releases.
- We can plan Flowable upgrades, including the Spring Boot and Java version requirements listed in each release, as a scheduled piece of work.
- Ask us to quote the recurring support effort separately from the one-time build so you can compare it with the IBM renewal.
