What does BPM cost when you build, partner or buy SaaS?
The engine license is rarely the largest cost of running BPMN processes. The total depends on modeling, integration with existing systems, a task UI for people who work the cases, the infrastructure the engine runs on, and whether production use is licensed. Flowable 8.0.0 is published under Apache-2.0, so its engine carries no license fee for production use. Camunda 8 is different: its Zeebe, Operate and Tasklist source files fall under the Camunda License 1.0, which limits use to non-production environments, so a production deployment needs a commercial license from Camunda. Camunda's pricing page publishes no prices and routes production licensing through sales, so ask for that figure in writing before comparing totals.
The three options shift different costs. Building on Flowable moves the license cost to zero but places the work on your side or a partner's: the modeling method, the human task UI, identity and integration code, clustering, backup, upgrades and test automation. A partner implementation adds a fixed-scope fee for those deliverables, usually paid once for the build and then again for retainers or upgrades if you want ongoing support. A commercial BPM or low-code platform bundles the UI and tooling, but its pricing is typically per user, per month or per app, so the bill grows with headcount and applications. Appian, for example, lists Standard, Advanced and Premium tiers priced per user, per month, per app, without published dollar amounts, so the recurring cost depends on your user count and volume.
Before you request quotes, ask each bidder to price the same scope: the number of processes and decision tables, the integrations, the task UI roles, the production and non-production environments, and the migration of any running Camunda 7 or Activiti instances. Camunda 7 Community Edition received its final feature release, 7.24, on October 14, 2025, and receives no further security patches, so that migration is a one-time cost you cannot defer indefinitely. Ask for the production license terms in writing, the list of components that recur each year, and which items are one-time.
Which cost components sit in each option
This table compares in-house build on Flowable or Camunda 8, an implementation partner, and commercial SaaS or low-code BPM across the main cost components. Read each row as a question to ask: who pays for the item, whether it is paid once or recurs, and what moves the number. The main takeaway is that open-source engines remove the per-user engine license but not the cost of modeling, task UI, integration and operations, and Camunda 7 end of life adds a migration item to every option.
| Cost component | In-house build (open-source engine) | Implementation partner | Commercial SaaS or low-code platform |
|---|---|---|---|
| Engine license | Flowable is Apache-2.0, so no engine license fee. Camunda 8 source is under the Camunda License 1.0, which permits only non-production use without a commercial license, so production use needs a Camunda agreement. | Partner fees are for implementation work. Engine licensing follows the choice of engine and the client's own terms, so confirm the production license position in writing. | Recurring subscription, typically priced per user, per month or per app. Appian lists Standard, Advanced and Premium tiers this way with no published dollar amounts. Camunda pricing publishes no prices, so request a quote. |
| Process modeling | Internal analysts or engineers model BPMN and DMN. One-time for the initial model set, then recurring as processes change. | Partner models and tests processes as a fixed-scope deliverable, one-time, with knowledge transfer to the client team. | Modeling tools are included in the subscription, but modeling time is still paid by the client. Some vendors charge separately for designer or development seats. |
| Integrations | Client engineers build and maintain connectors to core systems. One-time build, recurring maintenance when APIs change. | Partner builds connectors as scoped work, one-time, with a support or maintenance retainer if needed. | Prebuilt connectors may reduce build effort, but custom systems still need client or partner work. Confirm connector coverage and any usage-based charges. |
| Task UI and forms | Open-source engines provide REST and Java APIs, not a full task UI. The client builds and maintains the interface, which is a one-time build with recurring UI changes. | Partner builds task UI and forms as a fixed deliverable. Ask who owns the front-end code after handover. | Task UI is included, but per-user pricing applies to every person who completes tasks. Check whether occasional approvers need paid seats. |
| Infrastructure | Client pays for servers or cloud accounts, databases, load balancing and backups. Recurring. The Flowable async executor relies on the shared database for lock coordination, so clustering adds database work. | Partner may design and deploy infrastructure, one-time, while the client continues to pay the hosting bill, which recurs. | Vendor hosts the platform, so hosting is inside the subscription. Ask for data residency terms and what storage or action volumes are billed. |
| Operations and upgrades | Client staff patch the engine, database and runtime. Recurring. Flowable 8.0.0 moved to Spring Boot 4 with no backward compatibility for Spring Boot 3, so upgrade planning is a real budget line. | Partner may run upgrades and support under a retainer, recurring, priced from the written scope. | Vendor handles platform upgrades within the subscription. Confirm how custom code and integrations are tested before each upgrade. |
| Migration from Camunda 7 | Client team moves models and running instances. Camunda 7 Community Edition receives no further releases or security patches after 7.24, so the work is one-time but urgent. | Partner plans and executes migration, one-time. Ask how running instances, history and decision tables are carried over. | Vendor migration services or tooling may be offered, sometimes with fees. Confirm whether running instances move or only models are converted. |
| Recurring licence or support | Community forums only for open-source Flowable. Professional support is optional and bought separately. | Support and maintenance retainers are separate contracts, recurring, scoped in writing. | Subscription renews, typically annually or per term. Confirm renewal terms, price-change rights and exit provisions. |
How the license decides whether production cost is even possible
The license decides whether a production budget can be built at all, so check it before comparing any quote. Flowable is Apache-2.0, and its engines (BPMN, CMMN, DMN and the event registry) can run in production under that license without a license fee from Flowable. The cost then sits in your team, your infrastructure, the task UI you build or buy, and any Flowable professional services or commercial products you choose to add. Camunda is different. The Camunda 8 source for Zeebe, Operate and Tasklist is under the Camunda License 1.0, which limits use to non-production environments such as development, testing and evaluation, and requires a commercial license from Camunda for production. Camunda's pricing page publishes no prices, and any production deployment of Self-Managed needs an Enterprise license through sales, so the production line item is a quote, not a number you can look up.
Camunda 7 adds a second deadline. Its final feature release, 7.24, was scheduled for October 14, 2025, and after that Camunda makes no further releases or security patches for the Community Edition. The Camunda 7 Enterprise end of life was extended to April 9, 2030, with 7.24 as a long-term support release receiving updates in April and October, and paid extended support available from April 2030 through April 2032. If your estate runs Camunda 7 Community, the open-source cost of staying is the cost of maintaining an unpatched engine yourself, and the migration cost to Flowable or Camunda 8 becomes a near-term budget item rather than a future option. Ask a partner to state in writing which support path each option carries and who pays for security patches after the Community window closes.
Before costing production, get the license terms in writing for every component in the design: the engine, any Camunda 8 module, the task UI, the connectors and any commercial add-on. Ask the vendor or partner to confirm, for each one, whether production use is permitted, whether redistribution or embedding in your own product is allowed, and what happens to the license when you move from a test cluster to a live one. Then build the cost model around the terms that are confirmed. A quote that assumes production use of a component whose license only covers non-production work is not a valid quote, and it is the most common reason BPM budgets are revised after go-live.
What moves the BPM cost up or down
BPM cost rarely scales with license fees alone in an open-source build. The effort comes from how many processes and versions you run, how many systems they touch, and what the engine must guarantee in production. Read each driver as a direction of cost and ask any partner to price each one separately in the written scope.
Number of processes and versions
Every BPMN model, decision table and case definition needs modeling, testing and a versioning rule. Cost grows with the count of live definitions and with how often they change, because each change needs regression testing and a decision on whether running instances move to the new version. A small catalog of stable processes is cheaper to build and to keep current than dozens of processes that change every quarter. Ask a partner how versions are tested and how running instances are migrated between them.
Integration count and API maturity
Each connected system adds design, error handling, retries and test data work, and the cost rises sharply when the systems expose unstable or undocumented APIs. Processes that call a modern REST API with clear contracts are cheaper to build than ones that depend on file drops or screen scraping. Ask for an inventory of integrations with owners and interface types before estimating, since this inventory usually drives the largest share of the build effort.
Human task UI and forms
Flowable and Camunda 7 Community Edition ship engines and APIs, and the Flowable 7.0.0 release notes state that version 7 removed the UI applications. Building task lists, forms, delegation and role-based views is therefore a separate build item, whether you write it in-house, hire a partner, or buy a commercial task client. Count the number of distinct task screens and the number of user roles, since both drive front-end and testing effort.
High availability and clustering
Running more than one engine node needs the async executor to coordinate work. According to the Flowable advanced documentation, nodes use lock owners and lock expiration times stored in the database, so expired locks are recovered and jobs are picked up by other nodes. Cost rises with the number of nodes, database high availability, load testing and on-call operations. Confirm the expected uptime target and the failover tests a partner will run before accepting the scope.
Identity integration
Human tasks need users, groups and roles from your directory. Flowable documents that identity management can be replaced by implementing its identity service interface, and an LDAP implementation is provided as a reference. A reference implementation shortens the work, but connecting to your own directory, SSO and group model, and mapping them to task candidate groups, still needs careful design and testing. Ask whether the partner will use the reference code as is or adapt it.
Audit, retention and migration from Camunda 7
Audit trails, history retention and records policies add storage, backup and review work that recurs every year. Migrating running instances from Camunda 7 or Activiti is a separate project: Camunda 7 Enterprise end of life was extended to April 9, 2030, and Camunda 7 Community Edition receives no further releases or security patches after 7.24. Flowable's blog says Camunda 7 and Activiti data can be migrated in place, including active instances and history, and offers a free tool to report what a migration involves. Request that report before setting a migration budget.
How to build your own BPM cost estimate
This sequence turns a vague BPM budget into a scoped comparison of building, partnering or buying SaaS on the same five-year basis, so each option is priced against identical work.
Inventory processes and decisions
Business process owners and architects list every process to be modeled, with its owner, volume, expected run length and the decisions embedded in it. Separate structured BPMN flows from unstructured case work, and flag rules that belong in DMN decision tables. The step is done when each process has an owner, a rough count of steps and human tasks, and a list of decision points. That inventory is the base for every later cost line, because modeling, testing and migration effort all scale with it.
Classify integrations by system and direction
Integration engineers map each process to the systems it calls or receives from, such as the core banking or case system, identity provider, document store and messaging layer. Mark each integration as read, write or event-driven, and note whether an adapter already exists or must be written. The output is an integration register with a complexity label per item. Ask partners to price against this register, since integration work is often the largest variable cost after modeling.
Decide the task UI and form approach
Product and security leads decide how staff will complete human tasks: a custom front end built on the engine's REST APIs, a commercial task client, or forms supplied by the engine vendor. Each choice carries different build, licensing and maintenance costs. Confirm whether the chosen engine's open-source edition includes task interfaces, since Flowable's open-source scope and Camunda 7's bundled Tasklist differ. The step is complete when the UI approach is written down with its owner and its accessibility and audit requirements.
Size infrastructure, database and environments
Platform engineers estimate the runtime footprint: the number of engine nodes for clustering, the relational database and its high-availability setup, and separate development, test, staging and production environments. Confirm which database types the chosen engine supports in your standard stack. Record the recurring hosting, backup and monitoring costs as a separate line from one-time setup. The step is done when the environment diagram and a recurring infrastructure line item exist for each option under comparison.
Choose the license path for production
Legal, procurement and engineering review the license terms before any price comparison. Apache-2.0 engines such as Flowable carry no per-user production fee in the engine itself, but a commercial product layer or support contract may apply. Camunda 8 source files are under the Camunda License 1.0, which permits only non-production use without a commercial license, so production use requires a quote from Camunda. Confirm each vendor's current terms in writing. The step closes with a documented license decision for each candidate.
Price migration from Camunda 7 or Activiti
If processes already run on Camunda 7 or Activiti, migration becomes its own cost block. Camunda 7 Community Edition received no further releases after its final feature release, so teams should confirm the support date that applies to their edition. Flowable has described in-place migration of Camunda 7 and Activiti data, including active instances and history, and Camunda provides a Diagram Converter for its own path. Ask each candidate to inventory running instances, custom listeners and forms, and test migration in a copy of production data before committing to a price.
Compare build, partner and SaaS on one scope
Finance and the architecture lead build a five-year table with identical scope for each option: modeling, integrations, task UI, infrastructure, licenses, support, upgrades and migration. For build, count internal staff time and recurring hosting. For partner work, request a fixed-scope written quote derived from the inventory, integration register and UI decision above. For SaaS, price per user, per app or per process volume as the vendor states it. The estimate is complete when every option is priced against the same list, and the gaps are explained line by line.
When a workflow engine other than BPMN changes the math
Temporal is a code-first durable execution platform, not a BPMN modeler, so it changes the cost question only when the work is developer-owned orchestration rather than business-owned process models. The Temporal server is MIT licensed and can be self-hosted or bought as Temporal Cloud. Before comparing it with a Flowable build or a commercial suite, confirm that your process owners will not need to draw, version and hand over BPMN diagrams, because that work will fall back on engineers and the cost of model maintenance does not disappear. Expect a different cost mix: fewer license decisions, more engineering time spent on workflow code, testing and operations.
Temporal Cloud pay-as-you-go pricing starts at 50 US dollars per million actions, according to the Temporal pricing page, with separate charges for active and retained storage. Action volume, the number of workflow executions and retained history are the inputs to ask for in any quote, and they grow with long-running or high-frequency processes. Self-hosting removes the per-action charge but moves costs into your own team: you must run persistence on a supported database, provide advanced visibility storage such as Elasticsearch or OpenSearch for anything beyond a few workflow executions, and plan upgrades one minor version at a time with schema changes applied before the server.
If no Authorizer is configured, self-hosted Temporal uses the default noopAuthorizer, which allows every API request with no authentication or access control. Budget for configuring mTLS, a ClaimMapper, an Authorizer and OIDC single sign-on for the Web UI before any production use, and confirm with your security team whether these controls and their evidence are in scope for the engagement. Those tasks, and the audit evidence they produce, are where a partner quote and an internal estimate usually diverge.
Questions buyers ask before they cost a BPM project
How much effort does a typical open source BPM build take?
It depends on scope, and the honest answer comes from a written list of processes, integrations and human task screens. Effort grows with the number of BPMN processes, decision tables, forms and task UIs, the number of systems each process must call, and the amount of exception handling the business expects. A single approval flow with one integration is a very different job from a claims platform with case management, timers and audit reporting. Ask any partner, including DeployOpen, to break the estimate into processes, integrations, UI, infrastructure and testing, and to state what is excluded. DeployOpen agrees scope, deliverables and timelines in writing before work starts, so the quote follows from that document.
Can our own team build a BPM platform without a partner?
Yes, many teams can, provided they have Java or Spring skills, database and operations experience, and someone who owns the process models after go-live. Flowable is licensed under Apache-2.0 and offers Java and REST APIs, so the engine itself carries no license fee. The work that often gets underestimated is the surrounding system: a task UI for human work, identity integration, clustering, monitoring, backup, and a test process for changing models in production. Check whether your team has capacity for those parts over the life of the platform, not only for the first release. A partner can cover some of that work or train your staff on it.
How long does a BPM rollout usually take?
The duration is set by the first process you release, the number of integrations it needs, and how many approvals your organization requires before production. A narrow pilot with one process and one or two systems moves much faster than a rollout across several business units. Timelines should appear in the written scope with milestones for modeling, integration testing, user acceptance, security review and cutover. Ask a partner to show which milestones depend on your staff, such as process owner sign-off or access to test systems, because those dependencies often decide the schedule more than the engineering does.
What does the work need from our organization?
Most of the effort on the client side is people's time and access, not software. You will need process owners who can describe current steps and decision rules, subject matter experts who review models and forms, and an operations contact for infrastructure. Plan for infrastructure in your own cloud account or data center, a database the engine can use, identity integration, and a security review of the design and the hosts. Ask for a responsibility matrix in the scope that names who approves each deliverable and who maintains the platform afterward. Gaps in that matrix are the most common source of delay.
Is a SaaS BPM platform cheaper than building on open source?
It depends on how many users and apps you need, how long you keep the platform, and what you must control. Commercial BPM and low-code platforms are often licensed per user, per month or per app, and some publish tiers without dollar amounts, so you need a written quote for your user counts. Camunda's pricing page, for example, publishes no prices, and its Self-Managed edition requires an Enterprise license for any production deployment. Open source engines remove the license fee but add internal or partner effort for hosting, upgrades and support. Compare total cost over the planned life, including recurring licenses, infrastructure, upgrades and support, and check whether production use is permitted under the license.
What does migrating from Camunda 7 add to the cost?
Migration adds work for models, running instances, history and integrations, and the size of that work depends on how much is in flight. Camunda's final Camunda 7 feature release was 7.24, scheduled for October 14, 2025, and no further Community Edition releases or security patches are planned after that. Camunda's migration tooling includes a Diagram Converter that analyzes Camunda 7 BPMN, DMN and form files and lists migration tasks. Flowable has stated that Camunda 7 and Activiti data can be migrated in place, including active process instances and history, and offers the free Flowable LEAP tool to report ahead of time what a migration involves. Ask for an inventory of models, active instances, custom listeners and forms before agreeing on a fixed price.
What to confirm with each vendor before you compare quotes
Before you compare quotes, get the production license scope in writing from every vendor. Camunda 8 source files fall under the Camunda License 1.0, which permits use only in non-production environments such as development, testing and evaluation. Camunda's pricing page publishes no prices, and any production deployment requires an Enterprise license through sales, so ask for the exact written scope covering production clusters, failover or disaster recovery environments, and any non-production copies that hold real data. Flowable's engines are Apache-2.0, so the question shifts to what a commercial Flowable product, support contract or professional services agreement adds on top. Ask which components, if any, the quote actually licenses.
Next, pin down metering terms. Appian prices per user, per month, per app and publishes record type sync limits of 4M, 20M and 50M rows per record type across its tiers, but no dollar amounts, so the figures must come from a written quote. For any per-user or per-app model, ask how named users, external partners and automated service accounts are counted, how process instances or apps are counted when they are retired, and what happens when you exceed a tier limit. For a Temporal Cloud or similar action-based model, ask for the unit definition and the expected volume assumptions in writing. Any price you cannot trace to a stated unit is not yet comparable.
Finally, confirm support, upgrade and Camunda 7 end of life handling. Ask whether security patches, engine upgrades and migration help are included or billed separately, and what response commitments apply. Camunda's announcement says Camunda 7 Enterprise end of life was extended to April 9, 2030, with paid extended support from April 2030 through April 2032, and Camunda 7 Community Edition received no releases after 7.24. Ask each vendor which option they recommend, what the extended support fee covers, and whether migration tooling is part of the quote. The fees, dates and SLA figures for each option were not supplied here and must come from the vendor or a written quote.
How DeployOpen scopes and delivers a fixed-scope BPM implementation
DeployOpen plans, implements, integrates, documents and supports self-hosted open-source BPM platforms inside the client's own infrastructure. For BPM cost: build, partner or SaaS, the work starts with a written scope that separates one-time delivery from recurring operations, so the total cost can be compared across options on the same basis.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- The written scope lists processes to model, engine edition, integrations, task UI screens and the target hosting environment.
- We record license terms for each candidate engine so production use is confirmed before any build effort is committed.
How we build
- We model BPMN processes, decision tables and case definitions with the business owners and test them before production.
- We build or configure the task UI, connect identity and line-of-business systems, and document each integration interface.
- Where a Camunda 7 or Activiti estate exists, we inventory its running instances and migration tooling before estimating effort.
How we hand over
- Handover covers deployment runbooks, configuration records, process model versions and test evidence held in the client's systems.
- Operators are trained on the engine, monitoring endpoints, backup and upgrade procedures for the chosen infrastructure.
- Audit history, access control settings and change records are documented so the client's own assessors can review them.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, priced separately from the fixed-scope delivery.
- Upgrade planning covers engine version changes, database migrations and rollback steps agreed with the client's change board.
- We recommend the client confirm retainer scope, response expectations and upgrade responsibilities in writing before go-live.
