Bizagi cost vs self-hosted Flowable: where the money moves
Self-hosted Flowable usually does not cost less in total than a Bizagi subscription, but it moves the spending. The Flowable engines are Apache-2.0 licensed, so there is no engine license fee to pay. Bizagi's cost is a recurring subscription to its cloud PaaS, which bundles the modeler, runtime, forms and work portal. With Flowable, the money goes to hosting, to rebuilding the forms, UI and data model that Bizagi provided, to migration work, to support, and to developers who write and maintain the processes in code. Whether the total goes down depends on how much of that work your team already has in place.
Start by listing what your current Bizagi subscription actually covers. Ask Bizagi for the components in your renewal quote, the number of users or processes it counts, and what it includes for upgrades and support. Then map each item to a Flowable cost: the database and servers in your own cloud account or data center, the Spring Boot or Java application that hosts the engines, and the internal or partner effort to rebuild each form and work queue. Flowable's commercial editions, Flowable Work and Flowable Design among them, add low-code modeling and monitoring. If your renewal depends on those features, price them with Flowable directly, since the open-source edition leaves them to your developers.
Expect the largest one-time cost to be rebuilding screens and the case workflow, and the largest recurring cost to be the engineers who keep the platform patched and running. Flowable 8.0.0, released on February 27, 2026, is the current major release and moves to Spring Boot 4, so check that your application stack can follow it before you budget for upgrades. Ask any implementation partner for a fixed-scope estimate that separates engine setup, form and UI rebuild, data migration and parallel running, and ask what ongoing support will cost after go-live. Those written scopes, not a license comparison, are what let you compare Bizagi's subscription with a self-hosted total.
Cost components on each side
This table sets each cost component of a Bizagi Cloud subscription against the self-hosted Flowable path, and marks whether each cost is one-time or recurring. Read it as a checklist of what to ask for in each quote, since the Flowable engine itself carries no license fee and most of the spend moves to hosting, people and migration work.
| Cost component | Bizagi Cloud (commercial) | Self-hosted Flowable | One-time or recurring |
|---|---|---|---|
| Engine or subscription | Cloud PaaS subscription covers the platform, modeling and the work portal. Confirm terms, user metrics and renewal in the contract. | Flowable engines are Apache-2.0 licensed, so there is no engine license fee. A commercial Flowable edition is optional and priced in its own quote. | Bizagi recurring; Flowable open source none, commercial edition recurring if chosen |
| Infrastructure and hosting | Included in the vendor's cloud service. You pay for integrations and any data egress that your architecture adds. | You pay for servers or Kubernetes capacity, load balancing, backups, monitoring and environments for development, test and production. | Recurring, scales with users, process volume and number of environments |
| Database | Managed by the vendor as part of the service. | You choose and license the database. Flowable supports H2, MySQL, Oracle, PostgreSQL, DB2 and Microsoft SQL Server, so licensing and DBA time depend on that choice. | Mostly recurring; some licensing may be one-time |
| Forms and UI rebuild | Forms, work portal and modeling come with the platform. Your own process screens are built in Bizagi tooling. | Flowable does not ship a full work portal in open source, so forms, task lists and user interface are built by your developers or a partner. | One-time build, then recurring maintenance |
| Migration | Export of diagrams and rebuild of rules, forms and data model is your effort, whether done internally or by a partner. | Same export and rebuild work, plus re-adding extended attributes and running old and new processes side by side until open cases close. | One-time, sized by the number and complexity of processes |
| Support and upgrades | Covered by the subscription and the vendor's upgrade cycle. | Community forum for open source. Professional services or support from Flowable or a partner are separate purchases. Major upgrades such as Flowable 8.0.0 need regression testing. | Recurring if you buy support or retain a partner; internal testing recurs with each upgrade |
| Internal skills | Citizen developers and a smaller platform team are often enough for standard work, depending on your process complexity. | A code-first engine needs Java and BPMN engineers who can model, integrate, secure and operate the engine. Confirm skills before committing. | Recurring salaries or contractor fees |
What moves the comparison for your organization
Bizagi's cost and a self-hosted Flowable stack do not scale the same way. The drivers below decide where the total cost lands, so measure them against your own portfolio before comparing quotes. Each one shifts spending between subscription fees, infrastructure and engineering time.
Number of processes and cases
Bizagi's subscription is typically tied to the users and apps you run, so a growing number of processes adds licensing as well as build effort. With Flowable, each additional BPMN or CMMN model costs mostly developer time for modeling, testing and forms, and the engine itself adds little license cost. Count active processes, case types and decision tables separately, because decision tables and case models rebuild differently. Ask any vendor exactly what its pricing meter counts.
Process data and history retention
Retention drives database size, backup windows and storage cost. Flowable keeps runtime and history data in the relational database you choose, so the history level and how long you keep it directly set your database footprint. Bizagi's storage terms sit inside its cloud subscription, so ask how much data is included and what overage costs. Decide retention periods per process class before sizing hosting.
Commercial Flowable edition for low-code and governance
Flowable's open-source engines provide BPMN, CMMN and DMN execution with Java and REST APIs, but the low-code modeling, visual debugging, security controls, monitoring and governance tools are part of its commercial products. If business analysts must model and monitor processes without developers, budget for a commercial edition or for building those tools yourself. If developers own every change, the open-source engines may cover the need at lower license cost. Confirm which features each edition includes in writing.
Availability and clustering needs
Running several Flowable nodes against one database requires the async executor to coordinate timers and jobs. It uses lock owners and lock expiration times stored in the database, so a failed node's expired locks are recovered and its jobs are picked up by others. This is useful, but it means you must plan database high availability, node count and monitoring, which adds infrastructure and operations cost. Ask whether your uptime targets justify a multi-node design from day one.
Existing Java and Spring skills
A code-first engine shifts cost toward people. If your team already builds and operates Java and Spring services, Flowable's embedded or Spring Boot model fits existing practices and lowers the learning curve. If not, expect to hire or train, and budget for ongoing upgrades, such as the Spring Boot 4 and Spring Framework 7 change in Flowable 8.0.0 that broke Spring Boot 3 compatibility. Skills gaps are usually the largest recurring cost in this comparison.
How to build the comparison with your own numbers
This sequence turns a general cost comparison into a figure set you can defend, built from your Bizagi contract, your process inventory and written quotes. Each step produces a cost line that feeds one side of the Bizagi against Flowable comparison.
Inventory processes, forms and integrations
Start by listing every Bizagi process in production, in pilot and in retirement, along with its forms, business rules, data model, connected systems and monthly case volume. Owners in the business and the Bizagi administrator should review the list together. The step is done when each process has a named owner, a form count and a note on which integrations it calls, because rebuild effort is driven by these counts rather than by the number of diagrams.
Record current Bizagi subscription terms
Collect the current Bizagi agreement and order forms, and write down the term, the billing unit, the included environments, the user or process metrics that trigger extra charges, and any support or renewal clauses. Ask Bizagi in writing to confirm what the subscription covers and what it costs to add capacity. The step is done when a single sheet shows the recurring fee for each year of the remaining term and the events that change it.
Cost the target hosting architecture
Design the self-hosted target for Flowable, including the relational database that the engine supports, application hosting, load balancing, backups, and separate test and production environments. Ask your infrastructure team and cloud or data center provider to price each component, and note which items are one-time setup and which recur each month. The step is done when the hosting cost is split into infrastructure, database, backup and environment lines, each with a stated source.
Estimate rebuild effort per process and form
Using the inventory, estimate the developer and business analyst effort to rebuild each process model, form, business rule and user screen in Flowable's code-first model, because the open-source engines do not ship Bizagi's modeling studio or work portal. Group processes by complexity so that similar items share an estimate. Ask implementers for written quotes on a sample of processes, and compare them with your internal estimate. The step is done when each process has an effort range and a named role for each piece of work.
Add migration and parallel-run effort
Add time for exporting diagrams, re-adding the attributes that BPMN export drops, moving data, testing, and running old and new processes side by side until open cases close. Record who runs each activity and how long open cases will stay in Bizagi, since that period extends the subscription cost. The step is done when the migration plan lists each activity, its owner and the date on which the Bizagi subscription can end.
Estimate support and upgrade effort each year
Estimate the recurring work for the self-hosted platform: applying security updates, upgrading the engine and its Java and Spring dependencies, monitoring, backups and restore tests, and on-call cover. Decide whether you will use community support, a commercial Flowable edition, professional services or a retainer, and request written prices for each option. The step is done when an annual figure exists for internal staff time and for any paid support, separate from the Bizagi fee it replaces.
Compare totals over the same period
Place the Bizagi recurring fees and the Flowable one-time and recurring costs side by side over the same number of years, with one-time costs spread across those years. Test the result with a higher and a lower case volume, and with a longer migration period. The step is done when the sheet shows the year in which cumulative costs cross, if they do, along with the assumptions that would change that result.
What you rebuild in a code-first engine
The first thing to price is the work portal, not the engine. Flowable gives you BPMN, CMMN and DMN engines with Java and REST APIs, but it does not give your users a task inbox, a case workspace or a low-code modeler. Those are the parts Bizagi includes in its platform, and in a code-first setup your team builds them, buys them from a commercial Flowable edition such as Flowable Work or Flowable Design, or combines both. Before comparing numbers, list every screen your Bizagi users touch today, from work queues and case views to administrator pages for process versions, and mark each one as built, bought or dropped. The Flowable open source page describes the commercial products as adding low-code modeling, visual debugging, security controls and monitoring on top of the same engines, so confirm with Flowable which of those capabilities your use case needs before deciding what to license.
Forms and UI are a separate cost line that teams often underestimate. The Flowable 7.0.0 release notes say version 7 removed the UI applications and the form and content engines, so the form rendering and data entry that Bizagi handles through its form designer must come from your front-end code, a form library you select, or a commercial component. Each Bizagi form carries field rules, validation, calculated values and attachments, and each of those has to be re-expressed in your chosen stack and tested against the same cases. Your business rules move the same way: DMN tables can cover decision logic that is stable and tabular, but rules that Bizagi stores inside process steps need to be located, rewritten and tested. Ask any vendor or partner for a written inventory of forms, rules and screens tied to a named scope, because a quote without that inventory tends to hide the largest component of the rebuild.
The identity and task assignment layer is the third item to plan. Flowable's documentation says identity management can be replaced by overriding IdmIdentityServiceImpl or by implementing the IdmIdentityService interface, and it provides an LDAP identity service as a reference, so user, group and role mapping from your directory is code you own. Bizagi users who get roles and queues from its administration console will need equivalent group rules, delegation and escalation logic built and documented. Plan for ongoing ownership of this code: every new process, form or directory change becomes a change request handled by your developers or your implementation partner, and that work recurs for as long as you run the platform.
Questions buyers ask before comparing Bizagi with self-hosted Flowable
How much effort does a migration from Bizagi to Flowable take?
The effort depends mostly on what you have to rebuild, not on the BPMN diagrams themselves. Diagrams can be exported as BPMN 2.0 XML, but the extended attributes often need to be re-added by hand. The drivers to measure before you ask for a quote are:
- Process count and how many processes are still in active use
- Form complexity, including validation rules, conditional sections and document attachments
- Data model depth, including how many entities, relationships and integrations sit behind each case
- Business rules that currently live in Bizagi decision tables and must be expressed as DMN
Ask any provider to inventory these items in writing before estimating effort.
Can our own team migrate without outside help?
A team can do it in-house if it has Java and Spring development skills, database administration experience and someone who understands the business processes well enough to rebuild forms and rules. Flowable is a code-first engine, so there is no visual work portal to configure out of the box. Your developers will build the task interface, identity integration and reporting, and your operations staff will run the database and deployments. Confirm internally whether those skills exist before deciding between an in-house build and a fixed-scope engagement with an implementation partner such as DeployOpen, which plans, implements and documents self-hosted platforms inside your own infrastructure.
How long does a Bizagi to Flowable project take?
No researched duration is available for this migration, so treat any published timeline with caution. The schedule is set by the number of processes in scope, how many forms and integrations must be rebuilt, whether old and new processes must run side by side until open cases close, and how many business reviewers are available for testing. Ask any provider for a written scope with deliverables, phases and acceptance criteria, and ask what assumptions the timeline depends on. Most engagements at DeployOpen are fixed-scope, so the agreed scope and timeline are documented before work starts.
Does the Flowable engine itself carry a license fee?
The open-source Flowable engines for BPMN, CMMN and DMN are licensed under Apache 2.0, so the engine code itself has no license fee. Flowable also sells commercial editions, including Flowable Work, Engage, Orchestrate and Design, which add low-code modeling, visual debugging, security controls, monitoring and governance. Those editions are built on the same engines, so you should confirm with Flowable which features you would need and what they cost. Your remaining costs are hosting, the database, the people who build and run the system, and any support contract you choose.
What support is available for open-source Flowable?
Open-source users get access to a community forum, and professional services and partners are offered separately by Flowable. Community answers are useful for common questions but come with no response commitment, so production teams usually need a support path they can rely on. You can contract Flowable's professional services, use a partner, or engage an implementation provider for ongoing support, upgrades and continuous testing. Ask any vendor in writing what response times, escalation paths and upgrade assistance are included, because these are not set by the open-source license.
What must a self-hosted Flowable team run every year?
Your team owns the recurring work of keeping the platform current and secure. Expect to plan for the following each year:
- Upgrades between major versions. Flowable 8.0.0 was released on February 27, 2026 and moved to Spring Framework 7 and Spring Boot 4 without backward compatibility for Spring Boot 3, so application code must be adapted.
- Database maintenance, backups and restore tests for the supported databases such as PostgreSQL, Oracle or Microsoft SQL Server
- Monitoring of running processes and the async executor, which relies on lock expiration times stored in the database
- Dependency patching, security testing and access reviews for identity integration
Confirm the upgrade cadence and the staffing for it before comparing the total cost with a Bizagi Cloud subscription.
Does moving to self-hosted Flowable change our compliance evidence?
Yes, because you take on the controls that Bizagi Cloud currently provides as a managed service, such as hosting, access control, logging and backup. Your evidence will come from your own systems, so you need documented procedures for change management, access reviews and recovery testing. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports, attestations or certifications. Independent auditors and certification bodies perform those assessments, so ask your auditor which evidence they expect before the migration starts.
What to ask for in a quote
A DeployOpen quote follows from a written scope, and DeployOpen does not publish a price list, so the most useful thing a buyer can do is define the scope precisely before asking for a number. Ask for the scope of processes and forms as a numbered inventory: each process, each form, each business rule and each integration with a named owner and a stated status (rebuild, simplify or retire). Ask for the environments in scope (development, test, staging, production and any disaster recovery copy), where they run, and who operates each one. Ask for the data migration assumptions in writing, including which running cases move, which close in Bizagi, which history is kept and in what form, and who validates the results. A quote that leaves these open will price the uncertainty, not the work.
Separate one-time work from recurring cost in the quote. One-time items usually include discovery, modeling and engine configuration, form and user interface rebuild, migration, testing, hardening and documentation. Recurring items include hosting, database and backup operation, monitoring, the platform upgrades that Flowable's release line requires (the Flowable 8.0.0 release notes describe a move to Spring Boot 4 with no backward compatibility for Spring Boot 3, which affects any custom code), and support hours. Ask what the support model covers, what response expectations apply, and whether upgrades are included or billed separately. Ask who holds the licences for any commercial Flowable edition you choose, because that cost is paid to Flowable and is not part of a DeployOpen quote.
Settle code ownership before work starts. Ask the supplier to confirm in writing that the BPMN models, Java delegates, custom forms, configuration, infrastructure code and runbooks are delivered to your organization under terms you can use internally, and that the repositories are hosted in your environment. Ask which components are third-party open source and under which licence each is distributed. Confirm the exit path as well: if you later change suppliers or engines, you should be able to export models and data without the supplier's cooperation. Where a point is unclear, such as the scope of a retainer or whether a handover includes test evidence, ask for it to be stated in the statement of work rather than assumed.
How DeployOpen scopes a fixed-price Flowable implementation
DeployOpen is a Chainscore Labs company that plans, implements, hardens, documents and supports self-hosted open-source platforms inside your own infrastructure. For a move from a Bizagi Cloud subscription to self-hosted Flowable, we start with a written scope that separates engine work, form and UI rebuild, hosting and handover so you can compare it line by line with the subscription you pay today.
How we scope
- Inventory the Bizagi processes, forms, business rules and integrations in scope, with volumes and user groups recorded in writing.
- Agree which Flowable engines (BPMN, CMMN, DMN) each process needs and which Bizagi features will be rebuilt rather than carried over.
- Set out the hosting target, database type and identity source in the written scope before any build work starts.
How we build
- Convert BPMN 2.0 exports into Flowable deployments and re-add the extended attributes that the export drops.
- Rebuild forms, task screens and the data model in the UI technology your developers will maintain after handover.
- Test process paths, timers and async jobs on the clustered setup, then run old and new processes side by side until open cases close.
How we hand over
- Document each process, decision table, form and integration, with the owner and the change procedure for each.
- Deliver runbooks for deployment, database backup, restore and Flowable version upgrades in your own environment.
- Walk your developers and operations staff through the system and confirm the handover checklist with your team in writing.
How we support
- Engagements are fixed-scope, so scope, deliverables and timelines are agreed in writing before work starts.
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Ask us to quote hosting, licensing and any Flowable commercial edition separately so you see each recurring cost.
