Imixs-Workflow Engine

An open source BPMN 2.0 workflow engine for building human-centric process applications.

Stars
★ 419
Last updated
6d ago
License
NOASSERTION
Primary language
Java

At a glance

How it runs
Library / SDKSelf-hosted service
Works with
Universal · cross-platform
Cost
Free, no paid service needed
Setup effort
Medium · a few setup steps
You'll need
JDK 8+Maven 3.0.3+Jakarta EE application server (Wildfly, Payara, Open Liberty, Apache TomEE)Docker (optional, for Imixs Process Manager)Shell / CLINetwork accessLocal filesystem
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)

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.

  1. 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.
  2. 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.
  3. A process designer modelling flows in Eclipse with Imixs-BPMN according to BPMN 2.0, letting the engine execute them without writing transition code.
  4. An operator administering running instances remotely with Imixs-Admin, or spinning up development and test environments from the Imixs Process Manager Docker image.
  5. A platform team deploying on Kubernetes or Docker-Swarm and building a complete service stack from the Imixs-Microservice project.
  6. 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 install

To 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 up

The 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 up

You 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?

Pros
  • 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.
Limitations
  • 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?

FollowAgents source review · FARS-2.1
Major gaps
48/ 100 5-point scale 2.4 / 5
This review covers the source as of Nov 08, 2026. The project has shipped 1 stable release(s) since, which have not been re-reviewed. The score and verdict describe the reviewed version only. Recent releases ↓
Trust 11/29
Reliability 5/14
Adaptability 9/18
Convention 10/18
Effectiveness 9/13
Verifiability 4/8
Why each dimension lost points
Trust11 / 29 · 1.9/5

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.

Reliability5 / 14 · 1.8/5

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.

Adaptability9 / 18 · 2.5/5

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.

Convention10 / 18 · 2.8/5

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.

Effectiveness9 / 13 · 3.5/5

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.

Verifiability4 / 8 · 2.5/5

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.

Risks and how to mitigate them
  • 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.
Evidence confidence: Low Reviewed Nov 08, 2026 Reviewed revision 55c67b2fdb43 New commits since this review; the score may not cover them
See the full review method →
Maintain this project? Add the FARS badge to your README

The badge shows the current review score and verdict and links back to this page. It refreshes about once an hour after a re-review.

FARS

[![FARS review](https://followagents.com/badge/imixs-workflow.svg)](https://followagents.com/en/agents/imixs-workflow)
<a href="https://followagents.com/en/agents/imixs-workflow"><img src="https://followagents.com/badge/imixs-workflow.svg" alt="FARS review"></a>

Recent releases

Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.

  1. 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 #984
    View on GitHub ↗
  2. 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 #981
    View on GitHub ↗
  3. 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 #978
    View on GitHub ↗

FAQ

Does Imixs-Workflow cost anything?
No. It is released under the Eclipse Public License v. 2.0, and the documentation states you may also use, modify and distribute it under GPL-2.0-or-later.
Am I tied to one vendor's application server?
No. The README lists Wildfly, Payara, Open Liberty and Apache TomEE among the supported modern application servers, and states its openness lets it fit into modern microservice architectures.
Which Jakarta EE version is supported?
Full Jakarta EE 9 support, so it runs on every modern application server supporting Jakarta EE 9. For Jakarta EE 8 you can use version 5.2, which is still fully supported.
Can I try it without building an environment myself?
Yes. Imixs Process Manager provides a Docker image and a docker-compose file; running docker-compose up starts a process-management suite with a generic user interface locally or in a container environment.
How do I connect it to an existing microservice system?
Deploy the engine as a separate microservice and use the RESTful API from imixs-workflow-jax-rs; the README also points to the Imixs-Microservice project for a full service stack.
Is Imixs-Workflow Engine open source?
The source code is public on GitHub (imixs/imixs-workflow), but the repository does not declare a recognised licence, so the rights to reuse or modify it are unclear. Ask the author or check the README before building on it.
Is Imixs-Workflow Engine safe to use?
FollowAgents' FARS review (Nov 08, 2026) scored Imixs-Workflow Engine 11/29 on trust and safety. None of the eight safety controls the review checks for was missing outright. The repository has changed since that review.
Is Imixs-Workflow Engine still maintained?
Yes. The latest commit on GitHub is from 2026-11-15, within the last 30 days. The latest release is imixs-workflow-6.2.10 (2026-11-11).
Who makes Imixs-Workflow Engine?
Imixs-Workflow Engine is published on GitHub by the account imixs. FollowAgents has not verified which person or company is behind that account.
What is Imixs-Workflow Engine's official website?
The project's GitHub repository lists http://www.imixs.org/ as its website. That link is set by the repository owner; the source code itself is on GitHub (imixs/imixs-workflow).
Was this page helpful?
View on GitHub ↗ Install ↓

Related concepts