Workflow Engine

Workflow Engine is an embeddable .NET library for building and running business processes inside an application. It best suits development teams that want process state in their own database and can take responsibility for the host application's security. Its strongest case is the combination of an embeddable visual designer, broad database support, and versioned, auditable execution; the edition and deployment limits determine whether it fits a particular rollout.

Overview

Workflow Engine keeps business process state in a database and provides timers, audit history, and process versioning. That makes it a natural fit for teams adding durable workflows to an existing .NET product rather than seeking a standalone general-purpose automation platform. It supports .NET Framework 4.6.2 through .NET 10 and can be self-hosted on-premises or in a customer's cloud.

The HTML5 Workflow Designer can be embedded in an application, with packages for React, Angular, and vanilla JavaScript plus documented Blazor integration. BPMN 2.0 diagrams can be imported as native schemes, but cannot be exported back to BPMN; teams that need round-trip BPMN exchange should account for that boundary.

Key features

Runtime, data, and extensions

The maker lists support for SQL Server, Azure SQL, PostgreSQL, MongoDB, Azure Cosmos DB, MySQL, Oracle, and SQLite. This range gives teams room to use an existing database, though they still need to choose and operate the database as part of a self-hosted deployment. Listed plugins include Approval, Loops, File, Active Directory and Entra ID, and Real-Time Tracking, with custom plugins also supported.

Workflow Engine includes a visual workflow builder, event triggers, execution observability, and human approvals. Workflow Engine NEO adds an HTTP API and multitenancy; Workflow Server is a standalone Docker service called over HTTP. Those options give teams different integration shapes, but the core library remains the closer fit when embedding execution directly in a .NET application.

Security and administration

The core engine has no user store. Authentication and authorization of workflow commands remain the host application's responsibility, through an application-provided rule provider. That is workable for teams with established identity and access-control systems, but it is not a self-contained user or security layer.

Pricing

The free edition costs nothing, billed Perpetual · No payment required. It allows 10 schemas and 4 execution threads and is restricted to personal, non-commercial use, so it is for evaluation or personal projects rather than a commercial deployment. Commercial trials range from 30 to 90 days depending on edition; NEO subscription and business trial keys are valid 60 days, while NEO SaaS and Enterprise keys are valid 90 days.

Workflow Engine Team costs $2,000, paid once, billed Perpetual · One-time. It permits internal commercial use on a single server, with 8 execution threads, 100 commands and 100 activities per schema, and 500 transitions per schema. Those per-schema caps and single-server scope make it the more constrained commercial option.

Workflow Engine Complete costs $5,000, paid once, billed Perpetual · One-time, for internal commercial use with multi-server deployment. Forms integration is a $1,500 add-on. It is the step up for teams that need multiple servers, though public web apps and SaaS use call for a NEO edition instead.

Workflow Engine NEO Subscription costs $8,000 a year, billed Subscription · Per year, with updates included. It supports public web apps or SaaS and multi-server deployment. NEO Business costs $10,000, paid once, billed Perpetual · One-time, for internal commercial use with multi-server deployment. NEO SaaS costs $15,000, paid once, billed Perpetual · One-time, for public web apps or SaaS with multi-server deployment. NEO Enterprise has custom pricing, billed On request · Perpetual · One-time, and adds support for public web apps, SaaS, or OEM use, multi-server deployment, and a white-label canvas. The choice between these editions turns on commercial use, deployment model, and whether an annual subscription or one-time purchase suits the buyer.

Platforms

Workflow Engine supports API, Linux, macOS, self-hosted, web, and Windows. Its runtime is a .NET library, and deployment is self-hosted, so platform support does not remove the need to manage the host environment.

Who it's for

It is best for developers embedding business-process execution in a .NET application who want control over persistence, database choice, and deployment. The designer integrations and custom plugins are useful when workflows need to sit within an application's own interface and capabilities. Teams that need a managed user store, authorization out of the box, or BPMN export should look elsewhere or plan to provide those capabilities themselves.

Pros and cons

• Pros: Broad database support makes it easier to align workflow persistence with an existing application stack.
• Pros: Audit history, timers, and process versioning support processes that need durable state and traceable execution.
• Pros: An embeddable designer with React, Angular, vanilla JavaScript, and Blazor integration gives teams options for fitting workflow design into an application.
• Cons: The free edition is limited to personal, non-commercial use, 10 schemas, and 4 execution threads.
• Cons: The core engine delegates authentication and workflow-command authorization to the host application, adding implementation responsibility.
• Cons: BPMN import is one-way; diagrams cannot be exported back to BPMN.

Alternatives

Consider Kestra if an Apache 2.0-licensed, free platform is a better fit. 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 and no credit card required. Camunda has a free self-managed development option for local development and testing, so consider it when that is the immediate need.

Apache Airflow is free to download and use under the Apache License. Bizagi Modeler has a free plan for one user with unlimited processes and models but local storage only, making it a different option for individual modeling. Windmill has a free and open-source plan with 3 workspaces, 50 users, 10 GiB of workspace object storage, and 100 guest app users. AWS Step Functions has a Free Tier that does not automatically expire after the 12-month AWS Free Tier term and is available to new and existing AWS customers indefinitely.

For more options in the category, browse Workflow Orchestration Software.

Verdict

Choose Workflow Engine if you are building a .NET application that needs embedded, database-backed processes with audit history and versioning, and you can own authentication and authorization in the host. Its deployment flexibility and broad database support are compelling, but the personal-use-only free edition, commercial tier boundaries, and one-way BPMN import make it a poor fit for teams seeking a ready-made security layer, unrestricted evaluation for business use, or BPMN round-tripping.