Skip to content

Introduction

EventConductor is a production-grade, event-driven workflow orchestration platform for the Java/Spring ecosystem. It covers the full lifecycle of a business process — from definition to execution to monitoring — without forcing you into BPMN’s complexity or an external SaaS dependency.

Most workflow engines fall into one of two traps:

  • Too heavy: BPMN-based engines (Camunda, Flowable) require dedicated XML diagrams, separate process engines, and steep learning curves for developers.
  • Too coupled: SaaS solutions (Temporal Cloud, Conductor Cloud) introduce external dependencies and vendor lock-in.

EventConductor sits in the middle: a library you embed in your Spring Boot application, with a JSON DSL designed to be written and reviewed by developers, and three deployment modes that scale from a unit test to a multi-pod Kubernetes cluster.

Before choosing which engine, it is worth asking whether you need one at all. A process written by hand has to rebuild compensation, idempotent retries, crash recovery, timers, human tasks, versioning of in-flight runs and an operations console on its own — usually one incident at a time. Why a process engine? walks through that with a concrete example, lists what an engine costs in return, and says when plain code is the better choice.

A JSON or YAML file that describes the steps of a business process — their types, ordering, timeouts, retries, and branching conditions. Definitions are versioned and stored in version control.

A running execution of a workflow definition. Each instance has its own variables, status, and step execution history.

The execution of a single step within a process. Steps can be:

  • START — the entry point of a flow; completes instantly at process creation
  • ACTION — dispatches work to a worker microservice
  • USER_TASK — pauses the workflow until a human submits a form
  • PROCESS — starts a child workflow as a sub-process
  • FORK / JOIN — parallel execution branches
  • END — marks the workflow as complete

A stateless microservice (or a Spring bean) that receives TaskExecutionRequested events, performs business logic, and reports back a TaskStatusChanged event with the outcome and output variables.

A companion module that manages form definitions and form executions. When a USER_TASK step starts, the engine creates a FormExecution and pauses the workflow until the user submits the form.

FeatureEventConductorCamunda 8Temporal
Definition formatJSON/YAML DSL (code-friendly)BPMN 2.0 XML (diagram-first)Code (Go/Java/TS/Python/.NET SDKs)
DeploymentEmbedded libraryDedicated cluster / SaaSDedicated cluster / SaaS
External dependenciesNone / PostgreSQL / KafkaComponent stack + ElasticsearchTemporal cluster + database
License (production)MITPaid (source-available)MIT
Human tasks (forms)Built-in, with form editorBuilt-in (Tasklist + Forms)Manual (signals + your own UI)
AI / MCP integrationNative, engine + your servicesMCP client connector (8.8+)MCP server + agent SDK integrations
Learning curveLowHighMedium-high

See the full comparison with Camunda and Temporal for an in-depth, honest analysis — including when the alternatives are the better choice.

EventConductor is, to our knowledge, the first workflow engine with a native Model Context Protocol (MCP) integration.

Every module exposes its domain as MCP tools. Any MCP-compatible AI client — Claude Desktop, a custom chatbot, an internal copilot — can connect and operate the engine in natural language:

What you sayWhat happens
“What is the status of order 123?”Queries process by business key, returns status + variables
“Retry all failed processes from today”Calls retryProcess for each ERROR process
“Show me the pending user tasks for the onboarding workflow”Lists form executions filtered by workflow
“Import the new workflow definitions from Git”Triggers importWorkflowDefinitionsFromGit

EventConductor was, to our knowledge, the first workflow engine to ship native MCP support — and it remains the only one where MCP exposure of the engine and your own business services is a built-in, embeddable feature rather than a separate connector or add-on.