992 · Workflow Engine by Optimajet · v22.1.0 stable · August 2026 · .NET 10 down to .NET Framework 4.6.2 · Page last updated
A free .NET workflow engine by Optimajet, formerly called Community Edition. Embed it in your application, model processes in Workflow Designer, and keep workflow state in your own database. The full engine, the full designer, no license key, no time limit. It covers personal projects and your company's internal applications.
Releases, samples, and issues are available on GitHub. Full engine source access is available with selected editions under a commercial EULA.
Workflow Engine Free is the free product of the Workflow Engine Family by Optimajet, an embeddable .NET workflow library. It is a perpetual license for personal use and internal commercial use, with attribution, and it includes the full Workflow Designer.
An embeddable NuGet library that runs in-process, on .NET Framework 4.6.2+ and modern .NET.
Initial activity
The full HTML5 designer ships free. Embed it with React, Angular, Blazor, or vanilla JS.
Activities, transitions, and commands, with state that survives restarts in your database.
SQL Server, PostgreSQL, MySQL, Oracle, SQLite, or MongoDB. Tables are created and migrated for you.
A perpetual free license for personal and internal commercial use, with attribution: 10 schemas, 4 execution threads.
One line, WorkflowRuntime.RegisterLicense(key). Schemas, code, and database carry over.
Current activity
Use it to evaluate the engine, learn to model processes visually, build a proof of concept, or run a small application inside your company. It includes all core runtime features.
There is no separate free codebase. You install the same NuGet packages, call the same API, and persist to the same database schema as the paid embedded products, and Workflow Engine Free needs no key at all. That is why code written here runs unchanged after you register a paid license. The other products are the base Workflow Engine library, Workflow Engine NEO for SaaS and multi-tenant platforms, and the standalone Workflow Server. The full matrix is on the product comparison page.
Workflow Engine ships with a web-based HTML5 workflow designer your team hosts inside your own .NET app. Model schemes visually, reuse custom steps, and connect workflow behavior to server-side C# actions, with no external tool and no SaaS hop.
For production and AI-assisted scenarios, keep sensitive behavior in reviewed server-side C# actions or a curated action catalog. The designer makes the process visible. Your application still controls authorization, side effects, data access, and integration boundaries. Code Actions compile dynamically with full server access and should be disabled for end users in production.
Everything you draw in the designer is written in Simple Process Notation, the engine's own flowchart language. A workflow is a graph of activities connected by transitions, and commands are one of the things that fire a transition.
How one step runs. The process waits in Activity 1. A trigger fires the transition: automatic, a command from an actor, or a timer. The engine checks the condition. On true, the process moves to Activity 2 and runs its actions. On false, it stays and waits.
A step where the process stops and waits, shown as a box on the canvas. One activity is marked as initial, one or more as final. Each activity can carry a State, the business status you show to users, and a list of actions, your C# code that runs when the process enters it.
An arrow between two activities that defines an allowed move. A transition is fired by one of three triggers: it runs automatically, on a command, or on a timer. It can be guarded by a condition, a C# function returning true or false; Condition plus Otherwise works exactly like if and else in code. Branching needs no gateway element, just several outgoing transitions.
The trigger users press. When a user or your code calls ExecuteCommand, the engine finds the outgoing transition with a matching command and follows it. Rules decide who is allowed to execute which command, wired to your own identity system.
That is the entire model. For comparison, BPMN defines over 50 element types and usually needs training. This notation is readable by anyone who has seen a flowchart, so a developer, an analyst, and a product manager all read the same diagram.
The Get Started guide is three short pages. Install the packages, connect your database, and run your first process instance. No registration, no license key, no sales call along the way.
dotnet add package WorkflowEngine.NETCore-Core
dotnet add package WorkflowEngine.NETCore-ProviderForMSSQLPick any of the six providers instead of MSSQL if your stack runs on PostgreSQL, MySQL, Oracle, SQLite, or MongoDB. Then follow the Get Started guide from install to a running process, or start from the downloads page for the full package list.
Workflow Engine Free has a short list of restrictions, stated exactly and in full below. Read each limit next to what it means for a real project, and you will see why most learning, POC and small internal work fits inside them.
Ten process types per Free runtime. A learning project, a proof of concept or a small internal application models several processes end to end without hitting this. Paid products and editions remove the schema count limit.
The runtime executes up to four operations at the same time; the rest wait their turn in a queue. For one developer or a demo audience, you will not notice this limit. An internal application with many simultaneous users may queue, and Team (8 threads) or Complete (no limit) lifts it.
Model a process as large as it needs to be. The Vacation Approval demo scheme, a full multi-step approval with two approvers and a timer, uses 5 activities, 9 transitions and 4 commands, and nothing stops you going further.
The runtime works in single-server mode (AsSingleServer). Clustering across several servers is a commercial feature. A learning project or a POC runs on one instance anyway, and so can a small internal application.
The designer is fully functional and shows the Optimajet logo in the bottom-right corner of the canvas. Current builds still print "For non-commercial use only" beside it, and the license agreement, which allows internal commercial use, governs. Workflow Engine Complete and the editions of Workflow Engine NEO remove the logo.
Nothing is disabled. The designer canvas carries one badge in its bottom-right corner, the Optimajet logo; past that badge the usage caps above are the only restrictions. You do not have to take that on faith either. The runtime reports its active limits in code:
var restrictions = WorkflowRuntime.GetLicenseRestrictions();
if (restrictions.MaxNumberOfSchemes <= 10)
{
logger.LogWarning(
"Workflow Engine is running in Workflow Engine Free mode. " +
"Scheme and thread limits apply.");
}The one boundary that matters is the license grant. Workflow Engine Free covers personal use and internal commercial use, with attribution. When the project becomes a public web app or SaaS, or outgrows the limits, you buy a license and register the key. The code you wrote stays.
In this session from Fritz's Tech Tips and Chatter, an independent .NET community channel, the host walks through making workflows with Workflow Engine. It was recorded in 2019, and the schemes you see still run on the current release.
More recordings are on the official Optimajet YouTube channel and in the video tutorials section of the documentation.
Workflow Engine Free covers learning, proof of concept, and small applications that run inside your company in production. You get the real engine and the real designer, so the work you do here is the work you keep.
Learn on a production engine, not a toy. The notation is three building blocks, so the learning curve is short. Model a process in the designer, run it, and read its state and history straight from your database. Free forever, so it also fits pet projects and study.
Model your real approval or document flow in days and show stakeholders a working process with Workflow Designer they can open themselves. When the project is approved, it can run inside the company on Workflow Engine Free, within its limits, or move the same schemas and code to a Team or Complete license.
Prototype the workflow core of your SaaS on Workflow Engine Free. When you need the REST and RPC API, multitenancy, and clustering, a Workflow Engine NEO license turns them on in the code you already wrote.
Workflow Engine has shipped backward-compatible releases for over 10 years, and schemes from earlier versions run on current releases without migration.
You are also not tied to Workflow Designer. A process can be defined three ways, and all three produce the same runtime model. Draw it in the designer, write the scheme as XML and keep it in git where it diffs in pull requests, or build it in C# with the ProcessDefinitionBuilder API and get compile-time checking.
Workflow Engine Free, Workflow Engine, and Workflow Engine NEO use the same Core NuGet package. Registering a key selects the licensed product and edition. Your schemas, database, and everything you built in Workflow Designer carry over.
// Workflow Engine Free: no key, nothing to register.
// Any paid edition: add one line before runtime.Start().
WorkflowRuntime.RegisterLicense("your-license-key");Integrate additional Workflow Engine NEO capabilities only when you adopt them. The upgrade is safe in the other direction too. If a commercial key expires or goes missing, the engine does not stop. It switches back to the free mode, running processes continue, and new instances can still be created. License checks run locally, with no network calls, so nothing depends on an outside service.
Want to test the commercial features before buying? Get a free 30-day trial key at trial.workflowengine.io. No credit card required; a business email is. The key carries a TRIAL prefix and works like a commercial key for 30 days. If you evaluate with an AI assistant, the agent can request the trial key itself through the API described at trial.workflowengine.io/llms.txt.
| You are building | Recommended product |
|---|---|
| Evaluation, POC, learning, personal projects, small internal apps with attribution | Workflow Engine Free |
| Internal company process automation beyond the Free limits | Workflow Engine Team or Complete |
| SaaS or multi-tenant platform, subscription | Workflow Engine NEO |
| SaaS or multi-tenant platform, perpetual license | Workflow Engine NEO SaaS |
| Internal app with NEO API features, perpetual license | Workflow Engine NEO Business |
| OEM, white-label, enterprise redistribution | Workflow Engine NEO Enterprise |
The full feature and price matrix lives on the product comparison page and the pricing page.
Direct answers about Workflow Engine Free, its limits, the license grant, and the path to the paid products and editions.
Workflow Engine Free is the free Workflow Engine product by Optimajet, an embeddable .NET workflow library. It is a perpetual license for personal use and internal commercial use, with attribution. Use it to evaluate the engine, learn workflow modeling, build a proof of concept, or run a small application inside your company. It uses the same Core package and API as the paid embedded products, needs no license key, and has no time limit.
Workflow Engine Free is limited to 10 schemas and 4 execution threads. Activities, transitions, and commands are unrestricted. The engine runs in single-server mode only, and the designer canvas carries the Optimajet logo in its bottom-right corner. There is no time limit and no feature trial that expires.
Nothing is disabled. Workflow Designer is fully functional, and the one visible mark is a badge in the bottom-right corner of the canvas: the Optimajet logo. Current builds still print "For non-commercial use only" beside it; the license agreement, which allows internal commercial use, is what governs. Past that badge the usage caps are the only restrictions, and you can read the active limits in code with WorkflowRuntime.GetLicenseRestrictions().
Simple Process Notation is the built-in flowchart language of Workflow Engine. It describes any workflow with three elements. Activities are the steps where a process waits (each can carry a business State and C# actions that run on entry), transitions are the allowed moves between them, and commands are triggers users or code invoke. A transition fires automatically, on a command, or on a timer, and can be guarded by a condition; Condition plus Otherwise works like if and else in code. There are no gateways, pools, or separate event types to learn. Schemes are stored as XML, so you can keep them in version control and review changes in pull requests.
Yes. It is a perpetual license. You install it from NuGet with no registration and no license key, and you always get the latest release, the same code that paid customers run. Nothing expires and nothing forces you to upgrade.
Yes, inside your company, with attribution. Workflow Engine Free covers personal use and internal commercial use: websites and applications that run inside your company's security perimeter, in production too, within 10 schemas and 4 execution threads. A public web app or SaaS needs Workflow Engine NEO Subscription or Workflow Engine NEO SaaS, and shipping the engine inside a product you sell (OEM) needs Workflow Engine NEO Enterprise. Workflow Engine Team and Complete cover the same internal use and lift the limits.
No. Workflow Engine is commercial software with a free product, not MIT or Apache licensed. Workflow Engine Free is licensed for personal use and internal commercial use, with attribution. Licensed engine-source access is included for one year with NEO Enterprise, a one-year add-on on Complete, NEO Business and NEO SaaS, and unavailable on Free, Team and NEO Subscription, under a commercial EULA. The public repository at github.com/optimajet/WorkflowEngine.NET hosts releases, samples, and issues. Full engine source access is a separate, edition-specific entitlement.
The full engine. You get the visual HTML5 designer, all core runtime features (persistence, timers, process versioning, rules, and actions), and all six database providers (SQL Server, PostgreSQL, MySQL, Oracle, SQLite, and MongoDB). Pre-execution simulation, the Bulk API, and work calendars are part of the core runtime in every product. The Basic, Approval, and Loop plugins ship inside the core NuGet package and need no separate license.
Commercial products and editions add larger limits, multi-server clustering, the Workflow Engine NEO HTTP API, full multitenancy, forms integration, BPMN import, and an unbranded designer. Registering the appropriate license key keeps existing schemes and Workflow Runtime integration intact; capabilities that use additional packages or APIs are integrated separately.
Buy a license or request a trial key, then pass it to WorkflowRuntime.RegisterLicense() before the runtime starts. Your Core package, Workflow Runtime integration, schemas, and database stay the same. If you move to Workflow Engine NEO, add and configure only the capabilities you choose to adopt.
Choose by what you are building. For internal company automation that outgrows the Free limits, choose the Team edition of Workflow Engine, or Complete when you need unlimited usage and clustering. For a SaaS or multi-tenant platform, choose the Subscription or SaaS edition of Workflow Engine NEO. For an internal app that needs the NEO API, choose Workflow Engine NEO Business. For OEM and white-label distribution, choose Workflow Engine NEO Enterprise.
The engine keeps working. When a key expires or is missing, the runtime switches to the free mode with its limits. Running processes continue and new instances can still be created; nothing stops and no data is lost. Register a new key and restart the application to restore the commercial limits. License validation runs locally, without any network call.
Yes. Workflow Engine has shipped backward-compatible releases for over 10 years, and schemes written for earlier versions run on current releases without migration. A POC built on Workflow Engine Free is not throwaway work. If it stays inside your company and within the Free limits, it can go to production as it is. After you register a commercial key, the same schemas and the same code become the base of a larger production system.
From NuGet. Install WorkflowEngine.NETCore-Core plus one database provider package, for example WorkflowEngine.NETCore-ProviderForMSSQL. No registration, no key, no sales call. Licensed engine-source access is included for one year with NEO Enterprise, a one-year add-on on Complete, NEO Business and NEO SaaS, and unavailable on Free, Team and NEO Subscription, under a commercial EULA. If you work with an AI coding assistant, it can request a 30-day trial key for the commercial features on its own, through the API described at trial.workflowengine.io/llms.txt.
Install Workflow Engine Free from NuGet with no key and no registration, and run your first workflow in about 15 minutes. Request a trial key to test commercial capabilities; your schemes and Workflow Runtime integration carry into the paid products.
01Download
Add WorkflowEngine.NETCore-Core and one database provider. No registration, no license key, no sales call.
02Deploy
Three short pages take you from installing the package to a running process instance. Storage, runtime, designer, first scheme.
03Request a trial
Clustering, larger limits, and the Workflow Engine NEO API. A free 30-day trial key lets you evaluate them; add the relevant packages and configuration for the capabilities you test. No credit card required.
