Workflow Engine

Workflow Engine is built for .NET teams embedding durable business processes in an existing application. Its strongest appeal is control over workflow state, deployment, and the design experience; the trade-offs are substantial commercial license costs and security responsibilities that stay with the host application.

Overview

The engine persists process state in a database and supports timers, audit history, and process versioning. That makes it a plausible fit when a product needs workflows that survive beyond a single application request, especially if the team already operates a .NET application and its data layer. It supports .NET Framework 4.6.2 through .NET 10 and is self-hosted on-premises or in a customer's cloud, rather than supplied as a hosted service.

An HTML5 visual designer can be embedded in the application, with packages for React, Angular, and vanilla JavaScript and documented Blazor integration. BPMN 2.0 diagrams can be imported as native schemes, but the engine cannot export them back to BPMN. That makes it less suitable for organizations that need to exchange editable BPMN diagrams in both directions.

Key features

Persistence, databases, and extensions

Database support covers SQL Server, Azure SQL, PostgreSQL, MongoDB, Azure Cosmos DB, MySQL, Oracle, and SQLite. This range can accommodate an existing data environment, but the self-hosted model means the team remains responsible for operating its chosen database and deployment. Plugins include Approval, Loops, File, Active Directory and Entra ID, and Real-Time Tracking, with custom plugins also supported. These extensions offer building blocks for common workflow needs without making the engine a turnkey business application.

Embedding, deployment, and security

The core library can be embedded in an application; Workflow Engine NEO adds an HTTP API and multitenancy, while Workflow Server is a standalone Docker service called over HTTP. Those options distinguish an embedded integration from a service-oriented deployment, but buyers need to select the product matching their architecture. The core engine has no user store: authentication belongs to the host application, which must also provide the rule provider that authorizes workflow commands. That division gives application teams control, but it makes this a poor choice for buyers expecting the engine to supply identity and authorization end to end.

Pricing

Workflow Engine uses a freemium model, with a free edition and trial periods that vary by commercial edition. The Free edition costs nothing, is perpetual, and requires no payment, but it is for personal, non-commercial use only and is capped at 10 schemas and 4 execution threads. Those limits make it a way to explore the product or build personal projects, not a commercial deployment option.

Workflow Engine Team costs $2,000, paid once, perpetual, for internal commercial use on a single server. It includes 8 execution threads and caps each schema at 100 commands, 100 activities, and 500 transitions. Workflow Engine Complete costs $5,000, paid once, perpetual, for internal commercial use across multiple servers; forms integration is a $1,500 add-on. Complete is the multi-server step up, while Team is the lower-cost fit only if its single-server scope and per-schema limits suffice.

For public web apps or SaaS, Workflow Engine NEO Subscription costs $8,000 a year, with updates included and a 60-day trial key. NEO Business costs $10,000, paid once, perpetual, for internal commercial use across multiple servers, also with a 60-day trial key. NEO SaaS costs $15,000, paid once, perpetual, for public web apps or SaaS across multiple servers, with a 90-day trial key. NEO Enterprise has custom pricing on request, is perpetual and one-time, and covers public web apps, SaaS, or OEM use across multiple servers; it adds a white-label canvas and a 90-day trial key. The annual subscription is the option with updates included, while the perpetual options avoid an annual billing term; choose among them according to commercial use and deployment scope rather than assuming the editions are interchangeable.

Platforms

Workflow Engine is listed for API, Linux, macOS, self-hosted, web, and Windows. Its .NET runtime range and self-hosted deployment make the application environment and the team's operational capacity central to platform fit.

Who it's for

It is best suited to development teams building workflow features into a .NET product, particularly when they want a visual designer, persistent process state in their own database, and control over hosting. It is less appropriate for buyers who want a managed service, built-in user management, or BPMN round-trip exchange. Commercial buyers should also match the plan to internal versus public-facing use and single- versus multi-server deployment before committing.

Pros and cons

• Pro: Persistent state, timers, audit history, and versioning support durable processes inside an existing application.
• Pro: The embeddable designer and broad database compatibility give .NET teams options to fit workflow design and storage into their product.
• Pro: NEO and Workflow Server provide alternatives to embedding the core library directly.
• Con: The core engine delegates authentication and command authorization to the host application, adding security work for the development team.
• Con: BPMN import without export limits diagram exchange with teams that rely on round-trip BPMN.
• Con: Commercial entry points are costly, and the free edition excludes commercial use while limiting schemas and execution threads.

Alternatives

For a broader comparison, browse Workflow Orchestration Software. Consider Kestra if an Apache 2.0-licensed, free platform is a better starting point. Argo Workflows is a free open-source workflow engine for Kubernetes, making it the alternative to consider when Kubernetes is central to the choice. Bonita offers a free plan capped at 150 process instances per month, with no time limit or credit card requirement. Camunda is another freemium option, with a free self-managed development plan for local development and testing. Apache Airflow is free to download and use under the Apache License. Windmill has a free and open-source plan with 3 workspaces, 50 users, 10 GiB of workspace object storage, and 100 guest app users. Hatchet offers 1M runs and 1M events per month free before billing for usage above included amounts. YAWL is a free, open-source BPM/workflow system released under the LGPL licence.

Verdict

Choose Workflow Engine if you are building a .NET application and want durable, database-backed workflows with an embeddable visual designer and control over deployment. Its defining advantage is that workflows can live within the product and infrastructure you already own. Look elsewhere if you need built-in identity management, round-trip BPMN, or a lower-cost managed service; also check the plan's usage and deployment limits before making it part of a commercial rollout.