Stella Ops Workflow

Stella Ops Workflow is a set of libraries that let you run an orchestration engine inside your own services, with horizontal scaling, fine-grained control and extensions.

What that means in practice

Who it is for

.NET teams that build business applications with long-running processes in them: approvals, reviews, claims, onboarding, fulfilment. Processes that wait for people, call your services, branch, time out and must be auditable, inside services you already run.

How it differs

The full comparison, dated and sourced, covers Temporal, Camunda 8, Elsa Workflows, Azure Durable Functions, Conductor, Workflow Core, Dapr Workflow, WorkflowEngine.NET, Flowable, Camunda 7 and Operaton, and describes each approach as a design choice.

About these pages

These pages are for developers who embed the engine and write their own workflows. Each page has worked examples, configuration in JSON and environment variables, typical cases, and the pitfalls to avoid. Every step you type is on the page, and every C# example compiles as shown.

Reading paths

You want toRead, in order
Decide whether it fitsWhat is different, Standard features, Comparison, Overview, Licensing
Run a workflow end to end in under an hourOverview, Getting started
Put the engine into an existing ASP.NET Core applicationAdd Workflow to your project, Hosting, Persistence and signals, Configuration reference
Write workflowsDefining workflows, Calling services, Canonical definitions, the tutorials
Build a task list or a client of the HTTP APIHuman tasks and the HTTP API, HTTP API reference
Deploy definitions and versions with an audit trailGoverned activation and publishing
Operate the engineOperations, Troubleshooting, Upgrading
Test your workflowsTesting
Understand the licenceLicensing, Packages
Look up a type, a member or its signature.NET API reference

All pages

Start here

Hosting and authoring

Calling out and the API

Runtime behaviour

Reference and operations

Licence and packages

Runnable material

Other references