Imixs-Workflow Engine
An open source BPMN 2.0 workflow engine for building human-centric process applications.
- Source repo
- imixs/imixs-workflow
- Stars
- ★ 419
- Last updated
- 6d ago
- License
- NOASSERTION
- Primary language
- Java
- FA score
- 48/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platform
- Cost
- Free, no paid service needed
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- A Java enterprise team replacing paper or spreadsheet based approvals (leave, expense, purchase) with a programmable engine deployed on its existing Jakarta EE application server.
- Not a fit if
- Teams that cannot deploy a Jakarta EE application server
- Users who want an instantly available hosted cloud service
- Teams needing an embedded engine outside the Java/Jakarta EE stack
- Website
- imixs.org ↗ set on GitHub
- Maintenance
- Commits in the last 30 dayslast commit 2026-11-15latest release imixs-workflow-6.2.10 (2026-11-11)
- Source review
- 48/100 · Major gaps
What does this agent do, and when should you use it?
Imixs-Workflow is an open source workflow engine for building human-centric workflow applications on a flexible, robust framework, with business logic modelled in BPMN 2.0 and executed by the engine. It is built on the Jakarta EE and Eclipse MicroProfile standards and runs on modern application servers such as Wildfly, Payara, Open Liberty and Apache TomEE, with full Jakarta EE 9 support (Jakarta EE 8 users can stay on version 5.2). The repository ships several parts: the core imixs-workflow-engine, a RESTful layer in imixs-workflow-jax-rs, a Lucene-based index module imixs-workflow-index-lucene, plus the Imixs-BPMN modelling tool, Imixs-Admin, the ready-to-run Imixs Process Manager and the Imixs-Microservice stack for Kubernetes or Docker-Swarm. You can consume the engine as a Maven dependency inside your own Java project or deploy it as a standalone microservice that manages human tasks through a RESTful API. Builds use Maven and artifacts are published to Maven Central, so it suits teams that want a self-hosted, programmable, standards-based engine rather than a hosted SaaS or a non-Java stack.
The engine takes process models designed with Imixs-BPMN, an Eclipse modelling tool based on the BPMN 2.0 standard, and executes the task transitions they define: it receives a process instance (workitem) and an event, advances the state according to the model, and triggers the modelled business logic. It is distributed as Maven artifacts such as org.imixs.workflow:imixs-workflow-engine, org.imixs.workflow:imixs-workflow-jax-rs and org.imixs.workflow:imixs-workflow-index-lucene, which you add as dependencies. The jax-rs module exposes a RESTful API so the engine can be deployed as a separate microservice managing human-centric workflow tasks; the index module uses Lucene for search over process data. Around the engine, Imixs-Admin provides web-based remote administration, Imixs Process Manager bundles a generic user interface and a Docker image, and Imixs-Microservice provides a full service stack for Kubernetes or Docker-Swarm. The build command is mvn install, and artifacts are published to Maven Central.
- A Java enterprise team replacing paper or spreadsheet based approvals (leave, expense, purchase) with a programmable engine deployed on its existing Jakarta EE application server.
- An architect who wants workflow as its own service in a microservice architecture, exposing the engine through the RESTful API of imixs-workflow-jax-rs.
- A process designer modelling flows in Eclipse with Imixs-BPMN according to BPMN 2.0, letting the engine execute them without writing transition code.
- An operator administering running instances remotely with Imixs-Admin, or spinning up development and test environments from the Imixs Process Manager Docker image.
- A platform team deploying on Kubernetes or Docker-Swarm and building a complete service stack from the Imixs-Microservice project.
- A developer adding imixs-workflow-index-lucene to support Lucene-backed search over workflow data.
How do you install or deploy this agent?
Building from source needs JDK 8+, Maven 3.0.3+ and a Jakarta EE application server. From the repository root run:
mvn installTo add the engine, REST layer and Lucene index to an existing Maven project:
<dependencies>
<dependency>
<groupId>org.imixs.workflow</groupId>
<artifactId>imixs-workflow-engine</artifactId>
<version>${org.imixs.workflow.version}</version>
</dependency>
<dependency>
<groupId>org.imixs.workflow</groupId>
<artifactId>imixs-workflow-jax-rs</artifactId>
<version>${org.imixs.workflow.version}</version>
</dependency>
<dependency>
<groupId>org.imixs.workflow</groupId>
<artifactId>imixs-workflow-index-lucene</artifactId>
<version>${org.imixs.workflow.version}</version>
</dependency>
</dependencies>For a working environment in one step, download the Imixs Process Manager docker-compose file and start it:
docker-compose upThe README does not document the REST endpoints, authentication scheme or initial administrator credentials; those require the project home or the relevant module documentation.
How do you use this agent?
After defining a process with Imixs-BPMN under the BPMN 2.0 standard, deploy the engine either as a Maven dependency or as a standalone microservice and drive task transitions through process instances. Dependency declaration example:
<dependency>
<groupId>org.imixs.workflow</groupId>
<artifactId>imixs-workflow-engine</artifactId>
<version>${org.imixs.workflow.version}</version>
</dependency>For a local or container environment with a generic user interface, start the Process Manager first:
docker-compose upYou can then administer the instance remotely with Imixs-Admin, or integrate through the RESTful API provided by imixs-workflow-jax-rs in a microservice architecture. The README does not list concrete REST paths or payload formats, so check the module documentation and examples for real integrations.
What are this agent's strengths and limitations?
- Uses BPMN 2.0 as the modelling standard: flows designed in Imixs-BPMN are executed directly by the engine, keeping business logic out of code.
- Built on Jakarta EE and Eclipse MicroProfile standards, so it deploys to Wildfly, Payara, Open Liberty or Apache TomEE without locking you to a single vendor runtime.
- Modular distribution: engine, REST layer (imixs-workflow-jax-rs) and Lucene index are published separately to Maven Central.
- Comes with a full toolchain around the engine: Imixs-BPMN for modelling, Imixs-Admin for administration, Imixs Process Manager and the Imixs-Microservice stack for deployment.
- Released under EPL 2.0 (or GPL-2.0-or-later), so it can be used, modified and redistributed freely.
- Building and running requires a JDK, Maven and a Jakarta EE application server, which is more setup than a single-file tool.
- There is a version split between Jakarta EE 9 and Jakarta EE 8 (EE 8 requires version 5.2), so upgrades need compatibility checks.
- The README does not document concrete REST endpoints, authentication or initial credentials, so first integration needs extra documentation digging.
- The core stack is Java/Jakarta EE, which makes it hard to embed in non-Java projects.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Imixs-Workflow Engine This agent | 48 · Major gaps | Library / SDKFree | ★ 419 | 6d ago | Java | — |
| Budibase | 46 · Major gaps | Self-hosted serviceFreemium | ★ 28k | 1d ago | TypeScript | — |
| Bubble Lab | 45 · Major gaps | Web appFreemium | ★ 1.1k | 6mo ago | TypeScript | — |
| ClickClickClick | 36 · Major gaps | CLIFree + model costs | ★ 718 | 8mo ago | Python | OpenAI API |
How does FollowAgents rate this agent?
Why each dimension lost points
The repository describes a Java workflow engine, REST API, and container deployment, but the supplied files do not explain runtime permissions, data flows, sensitive-data protections, confirmation of external effects, or recovery mechanisms, so those criteria receive partial scores. The security policy lists supported versions and mentions Dependabot, while the CodeQL workflow schedules scans, supporting a basic dependency-security process (2). Vulnerability reports are directed mainly to the issue tracker, with no specific confidential handling process shown. README and the EPL/GPL license text corroborate licensing, but publisher identity is not verifiable from the supplied material, limiting attribution.
The README describes Jakarta EE 9 support and version 5.2 for EE 8, and gives build prerequisites. The security policy lists 5.2.x and 5.1.x as supported, but the current support picture is not fully reconciled, so self-consistency scores 1. Maven Central, Maven build instructions, and application-server prerequisites provide basic availability guidance (2). The supplied static files contain no evidence about error handling or user-facing failure messages, so that criterion scores 0.
The README targets developers building human-centric workflow applications and covers BPMN modeling, REST microservices, and several Jakarta EE application servers, giving ordinary scenarios reasonable coverage. Permission and capability boundaries are only implied by the product overview; unsuitable scenarios and precise triggers are not described, so those scores remain low. JDK, Maven, Jakarta EE prerequisites, and container options provide useful environment guidance, though version support information is incomplete.
The README is organized around product capabilities, building, related tools, and project participation, and includes a Maven dependency example and build command. It lacks an FAQ, troubleshooting guidance, and detailed system limitations. LICENSE.md explicitly states EPL-2.0 OR GPL-2.0-or-later, and the README describes the dual-license choice, justifying 3 for license. The support table, issue tracker, and vulnerability-reporting route provide some maintenance guidance; no clear release cadence or changelog appears in the supplied material, limiting versioning and responsibility scores.
The files describe a BPMN 2.0 human-centric workflow engine with REST integration and companion modeling, administration, and process-management tools. The README also provides Maven dependencies and a Docker Compose starting point, making the output practically usable. Scores are limited because the packet lacks a complete end-to-end example and details about operational costs or resource requirements, so deployment tradeoffs cannot be judged fully.
Product purpose, build method, licensing, and supported versions have concrete statements in the README, LICENSE.md, or SECURITY.md. The CodeQL and publishing workflows also corroborate the described scanning and Maven publication processes. Claims about product effectiveness, boundaries, and runtime safety remain broad; the material does not clearly distinguish demonstrated facts from promotional claims, so fact/inference separation scores 1.
- This review uses only the supplied static files and cannot confirm runtime permissions, data handling, recovery behavior, or end-to-end operation.
- The README's Jakarta EE 9 support statement is not fully mapped to the security policy's supported-version table; check compatibility and security support for the intended release before deployment.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
Release notes excerpt
Features - AdminP Job to update/process workitems #988 - new $migration flag #987 - ApplicationPlugin - introduce new item names #986 - Mulitiple Adapter Support for Microkernel #985 - Adapt new Open-BPMN Meta lib #984View on GitHub ↗ -
Release notes excerpt
Enhancements - WorkflowKernel improve updateModelVersionByEvent #973 - Extend SchemaService with default fields #970 Bugfixes - SplitAndJoinPlugin - update subprocess ignores new relationship #983 - Provide secure XML DocumentBuilder (protect XXE injection) #982 - XMLParser did not extract end tag correctly #981View on GitHub ↗ -
Release notes excerpt
Features - EventLogService - added new count metods #979 - ModelService - added findVersionsByRegEx #977 - TextAdapter for Timestampsfeature #976 - ItemCollectionComparator added support to compare Long and Double values #975 Enhancements - DocumentService - add media type for rest api countTotalHitsByQuery #980 - ModelService - provide public method initModels #974 Bugfixes - findDocumentsByJPQL should not decode the path parameter query #978View on GitHub ↗
FAQ
Does Imixs-Workflow cost anything?
Am I tied to one vendor's application server?
Which Jakarta EE version is supported?
Can I try it without building an environment myself?
How do I connect it to an existing microservice system?
Is Imixs-Workflow Engine open source?
Is Imixs-Workflow Engine safe to use?
Is Imixs-Workflow Engine still maintained?
Who makes Imixs-Workflow Engine?
What is Imixs-Workflow Engine's official website?
Thanks — we use this to improve the page.