Cflow vs jBPM

Cflow is an AI-powered, no-code platform for automating business processes and approvals. Its tools include visual workflow and form builders, a rules engine, routing, notifications, and reports and analytics. Cflow says its AI can read requests and documents with policy context, automate routine decisions, and escalate exceptions with reasoning. Integrations can use Zapier, APIs, webhooks, or direct connections; named services include Salesforce, Zoho CRM, Slack, Xero, Stripe, Google Drive, Gmail, GitHub, Zendesk, Dropbox, and Zapier. Android and iOS apps with push notifications are listed. Customers can choose cloud or on-premise data storage, while private hosting is listed as an add-on. Cflow states it operates with 99.9% uptime and hosts infrastructure in geographically distributed AWS data centers. Joy costs $22 a month, billed monthly, with a 10-user minimum and up to 20 workflows. Bliss costs $32 a month, billed monthly, with a 20-user minimum and up to 50 workflows. Zen requires 100 or more users and has custom pricing. A 14-day trial is available, but there is no free plan. Cflow was founded in 2010 and is headquartered in San Diego, California, USA.

jBPM is an open-source Java toolkit for automating business processes, tasks, decisions and rules. It consists of Java libraries embedded in a service, rather than a standalone server, and executes processes modeled with BPMN 2.0. Human tasks can use configurable lifecycles, assignment strategies and deadlines. Process rule tasks can call DRL rules or DMN decisions evaluated by Drools in the same service. For long-running processes, jBPM supports durable state, timers, signals, message correlation, service-level agreement tracking and migration of running instances to a new process version. Persistence choices include PostgreSQL and other JDBC databases, MongoDB, Infinispan, RocksDB and the filesystem. Web and IDE modelers offer graphical drag-and-drop process creation. For Apache KIE 10, the documented service approach uses Kogito on Quarkus or Spring Boot; BPMN models compile at build time, with no runtime deployment step or process repository to manage. The project says jBPM is written in pure Java and runs on any JVM, and the software is available from Maven Central under Apache License 2.0. Getting started calls for an IDE, JDK 21 preferred or JDK 17, and Maven 3.9 or later. Community support channels include user and developer mailing lists and Zulip. Apache KIE is incubating and has not yet been fully endorsed by the ASF.