Emakin vs jBPM

Emakin is a low-code platform for designing, automating, and managing business processes and applications. Its browser-based visual designer lets teams assign roles, add automated steps, and route work conditionally without coding. A smart form designer builds forms that respond to user input, validate data in real time, and can be deployed on the web, mobile, or embedded. Case management adds automatic task assignments, email integration, and SLA escalation for information-centric work. Dashboards and reports help locate bottlenecks, delayed tasks, and workload distribution. Connections to external systems use REST APIs and webhooks, with SOAP integrations also described in the documentation. Deployment choices include Emakin Cloud, Emakin Private Cloud, or self-managed installation on customer servers or a cloud provider. The maker lists Windows, Linux, and Docker support, plus modern browsers including Chrome, Firefox, and Edge. Advanced includes mobile access for iOS, Android, and web. Emakin was founded in 2010 and is headquartered in Dublin. Pricing is per user, with no amounts shown.

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.