---
title: "Workflow Engine by Optimajet Review for .NET Teams"  
description: "Workflow Engine by Optimajet review: an embeddable .NET workflow engine with a free product. See how Workflow Engine by Optimajet licensing compares"  
author: "Austin Luthar"  
published: 2026-11-11  
updated: 2026-11-11  
canonical: https://www.mindstick.com/blog/307116/workflow-engine-by-optimajet-review-for-dot-net-teams  
category: "software"  
tags: ["software", "workflow"]  
reading_time: 11 minutes  

---

# Workflow Engine by Optimajet Review for .NET Teams

[Workflow Engine by Optimajet](https://workflowengine.io/) is a family of embeddable workflow engines for .NET and C#, developed by Optimajet Limited since 2014, that adds approvals, state machines and long-running business processes to an application a team already owns. The family has four products: Workflow Engine Free, Workflow Engine, Workflow Engine NEO and Workflow Server, with Workflow Engine NEO as the flagship for multi-tenant SaaS.

Workflow Engine by Optimajet is commercial software with a free product, Workflow Engine Free, which covers personal use and internal commercial use, with attribution. Most paid editions are perpetual licenses paid once, Workflow Engine NEO Subscription is the only annual plan, and no edition charges royalties or per-execution fees. Workflow Engine NEO is source-available on its Enterprise edition, where GitHub access to the source code is included, and on NEO Business and NEO SaaS as an add-on; Workflow Engine Complete offers the same add-on under a commercial EULA.

*How this review was compiled. Product facts come from the vendor documentation at docs.workflowengine.io, the workflowengine.io pricing page and the NuGet registry. Competitor facts come from each vendor's own documentation and license pages. Performance and load were not tested.*

## Key takeaways

- Workflow Engine by Optimajet runs in-process inside a .NET application and stores process state in SQL Server, PostgreSQL, MySQL, Oracle, MongoDB or SQLite.
- Workflow Engine NEO adds a multi-tenant HTTP API with Data API and RPC API groups, three tenant isolation models and multi-server operation without a message broker.
- Workflow Engine Free needs no license key and allows internal commercial use, with attribution, within 10 workflow definitions (schemes) and 4 execution threads on one server.
- Paid editions start at $2,000, paid once, for Workflow Engine Team.

| **Product** | **What it is** | **License** | **Typical use** |
| --- | --- | --- | --- |
| Workflow Engine Free | The same library without a license key | $0, perpetual; personal and internal commercial use, with attribution | Evaluation, proof of concept, small internal app |
| Workflow Engine | Embeddable .NET library with Team and Complete editions | Perpetual; Team $2,000, Complete $5,000 | Internal .NET applications |
| Workflow Engine NEO | Separate product based on classic Workflow Engine, with HTTP API, multitenancy and Workflow Forms | Subscription $8,000 per year; Business $10,000; SaaS $15,000; Enterprise on request | Multi-tenant SaaS and web apps on .NET |
| Workflow Server | Standalone application in Docker with its own APIs and admin console, built on the Workflow Engine NEO stack | Own license and price list | Teams that call a ready service over HTTP |

\

## Workflow Engine by Optimajet Runs Inside Your .NET Application

Workflow Engine by Optimajet installs from NuGet as the WorkflowEngine.NETCore-Core package and runs inside the host application's process, so a team does not deploy or operate a separate workflow cluster. The core package had passed 1.2 million downloads on NuGet.

The engine keeps every process instance in the team's own database through one of six providers: SQL Server, PostgreSQL, MySQL, Oracle, MongoDB and SQLite, with SQLite intended for evaluation and local development. Switching databases means switching a NuGet package and a connection string, while application code stays the same. Developers call the engine from C#: they create process instances, execute commands such as approve or reject, and read the transition history of each process. The full product line, editions and documentation are collected on the official site of Workflow Engine by Optimajet.

## Workflow Engine NEO Adds a Multi-Tenant HTTP API for SaaS

Workflow Engine NEO is a separate product based on classic Workflow Engine, built for .NET teams that manage processes over HTTP from web back ends, JavaScript front ends, mobile apps or other services. NEO adds the Workflow Engine HTTP API with Data API and RPC API groups, multitenancy and Workflow Forms, and the HTTP API runs on .NET 8 and later.

Tenant isolation in Workflow Engine NEO follows three models. Logical isolation keeps a TenantId in a shared database, physical isolation gives each tenant a separate database or database schema, and hybrid isolation combines both in one deployment. The tenant is selected with the Workflow-Api-Tenant-ID header, and a new tenant can be registered without restarting the application. Authentication stays with the host application, while NEO adds per-operation and per-tenant permission checks that the host configures.

Every Workflow Engine NEO edition runs on several servers against one shared database. Database locks coordinate timers, and heartbeat records detect runtimes whose processes need recovery, so the cluster needs no external message broker, Redis or ZooKeeper.

## Visual Workflow Designer Serves Developers First

Visual Workflow Designer ships with all four products of Workflow Engine by Optimajet and shows a process as a scheme that a developer can change and debug without rewriting C# code by hand. Schemes use a state machine model: activities where a process waits, transitions between them, commands issued by users or systems, timers, and actions that run C# code. This vocabulary maps directly to approval chains, document routing and status changes.

The designer is an HTML5 component that embeds into applications built with React, Angular, Blazor or plain JavaScript, and a team can also expose it to business users inside its own product. Workflow Engine by Optimajet imports a supported subset of [BPMN 2.0](https://www.omg.org/spec/BPMN/2.0/) diagrams into its own schemes. The import is one-way, and teams that need full BPMN execution semantics are better served by a dedicated BPM platform such as Camunda 8.

## Workflow Engine by Optimajet Licensing Is Commercial With a Free Product

Workflow Engine by Optimajet licensing differs from open-source engines in what a team pays for, not in whether a team can start without paying. Workflow Engine Free requires no license key and no sales conversation. It covers personal use and internal commercial use, with attribution, within 10 workflow definitions (schemes), 4 execution threads and one server, while activities, transitions and commands are not limited. Moving to a paid edition means registering a key instead of rewriting code. A public web app or SaaS needs Workflow Engine NEO Subscription or NEO SaaS, and OEM distribution needs NEO Enterprise.

Prices are $2,000 for Workflow Engine Team (50 workflow definitions, 8 threads, one server), $5,000 for Workflow Engine Complete (no limits, several servers), $8,000 per year for Workflow Engine NEO Subscription, $10,000 for NEO Business and $15,000 for NEO SaaS, with NEO Enterprise quoted on request. Perpetual editions include 365 days of updates, and renewal costs 50% of the license price. Vendor support with guaranteed response times is sold as separate annual plans, and trial or proof-of-concept support is free for 30 days.

Elsa Workflows and Workflow Core are distributed under the MIT License, which removes the license fee but does not include vendor support with response times. Elsa documentation directs teams that need commercial tooling or long-term support to Elsa+, and ELSA-X, which describes itself as the commercial arm of Elsa, offers enterprise support without published prices. The real cost of any .NET workflow engine therefore combines the license, support, infrastructure and the code a team writes itself, such as a tenant-aware API.

## Workflow Engine by Optimajet Compared With Other .NET Workflow Engines

Workflow Engine by Optimajet competes most directly with Elsa Workflows, because both are embeddable libraries that run inside a .NET application. The other common options either run as a separate service or describe processes only in code.

| **Engine** | **Delivery model** | **License** | **Visual designer** | **Best fit** |
| --- | --- | --- | --- | --- |
| Workflow Engine NEO by Optimajet | In-process .NET library | Commercial, perpetual or annual | Visual Workflow Designer, HTML5 component | Multi-tenant .NET SaaS with approvals |
| Elsa Workflows | In-process .NET library, plus deployable Server and Studio | MIT | Elsa Studio (Blazor) | Event and integration orchestration |
| Workflow Core | In-process .NET library | MIT | None | Code-first workflows in C#, JSON or YAML |
| Temporal .NET SDK | Client for a separate Temporal Service or Temporal Cloud | MIT SDK | None | Large-scale durable execution |
| Camunda 8 | JVM platform with a C# SDK | License required for Self-Managed production | Camunda Modeler (BPMN) | Full BPMN execution |

\

The current Elsa Workflows release includes User Tasks with an inbox in Elsa Studio and BPMN 2.0 import and export with limited coverage, so both products now cover human steps and BPMN. The practical difference lies in tenant isolation, multi-server setup and the commercial terms behind each product.

## Workflow Engine by Optimajet Limits to Weigh Before Choosing

Workflow Engine by Optimajet has limits that a .NET architect should check before a proof of concept:

- The product is commercial software, not open source, and source-code access is a paid option on selected editions.
- Workflow Engine Free does not cover a public web app, SaaS or OEM distribution.
- The Workflow Engine HTTP API requires .NET 8 or later.
- BPMN 2.0 import covers a supported subset, works one way and is a paid add-on in every edition except NEO SaaS and NEO Enterprise.
- After a crash, the runtime loads the last persisted checkpoint; by default an interrupted process moves to Error or Terminated, and an external call still needs idempotency on the application side.
- The community is smaller than the Elsa community, so most answers come from vendor documentation and support.

## Workflow Engine by Optimajet FAQ

### What is a workflow engine?

A workflow engine is a software component that executes defined business processes, such as approvals, document routes and status changes, and stores the state of every running process instance. Workflow Engine by Optimajet is a workflow engine for .NET that runs inside the application as a library and moves each process forward through commands, timers and rules.

### What is the difference between a state machine and a workflow engine?

A state machine is a model that describes states and the transitions between them, while a workflow engine is the runtime that persists those states, runs timers and executes actions for thousands of process instances. Workflow Engine by Optimajet uses a state machine as its native process model and adds persistence, history, versioning and Visual Workflow Designer on top.

### Is Workflow Engine by Optimajet open source?

No. Workflow Engine by Optimajet is commercial software with a free product, Workflow Engine Free, and it is not MIT or Apache licensed. Source-code access on GitHub is available on selected commercial editions under a commercial EULA: it is included in Workflow Engine NEO Enterprise and sold as an add-on for Workflow Engine Complete, NEO Business and NEO SaaS.

### Can Workflow Engine Free be used for commercial projects?

Yes, for internal ones. Workflow Engine Free covers personal use and internal commercial use, with attribution, including internal applications in production, within 10 workflow definitions (schemes), 4 execution threads and one server. A public web app or SaaS needs Workflow Engine NEO Subscription or NEO SaaS.

### How much does Workflow Engine by Optimajet cost?

Workflow Engine by Optimajet costs $0 for Workflow Engine Free, $2,000 for Team and $5,000 for Complete, both paid once. Workflow Engine NEO costs $8,000 per year for Subscription, $10,000 for Business and $15,000 for SaaS, with Enterprise on request. No edition charges royalties or per-execution fees.

### What is the difference between Workflow Engine and Workflow Engine NEO?

Workflow Engine is the embeddable .NET library that a team calls from C# inside its own application. Workflow Engine NEO is a separate product based on Workflow Engine that adds a tenant-aware HTTP API with Data API and RPC API groups, logical, physical or hybrid multitenancy, multi-server operation in every edition and Workflow Forms.

Workflow Engine by Optimajet suits .NET teams that want to embed process state, approvals and Visual Workflow Designer into their own application instead of operating a separate orchestration cluster. Teams building a multi-tenant SaaS product evaluate Workflow Engine NEO with a 30-day trial key, and teams with an internal application start with Workflow Engine Free from NuGet. The most useful test for any engine is the same in every case: model one real process, restart the host while the process waits for a timer, and compare the code each engine requires.

---

Original Source: https://www.mindstick.com/blog/307116/workflow-engine-by-optimajet-review-for-dot-net-teams

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.
