AgilePoint NX vs jBPM

AgilePoint NX is a composable platform for coordinating enterprise systems and AI through governed workflows. Its visual, model-driven tools let teams build and run applications without compilation or a virtual machine. Workflows can be changed while active, with options including rollback, pause and resume, splitting, merging, partial rework, and migration in progress without redeployment. The platform lists more than 1,200 reusable assets from over 120 systems, including Salesforce, SAP, SharePoint, ServiceNow, Jira, OpenAI, and AWS services. NX v10 can create application experiences from images, PDFs, mockups, documents, and external data. Its MCP Server allows compatible agents to trigger workflows, while the AI Control Tower provides governance and oversight of AI process behavior. Security features include field-level encryption with customer-managed keys and API key management. Deployment options include on-premises, private cloud, SaaS, and hybrid configurations. A Community Edition is listed for up to 25 named users and two applications. Paid plans start at $39 a month per named user, with a 50-seat minimum; a 30-day trial is listed.

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.