Stella Ops Workflow

Stella Ops Workflow is a set of .NET libraries that runs a workflow orchestration engine inside your own services, not as a separate server. Long-running business processes keep their state in your own PostgreSQL or MongoDB database and scale out across the instances of your service. You decide which definition version runs, who works each task and how the engine is extended.

Not released yet: no Workflow package has been published. This page describes the release that is being prepared.

Why Stella Ops Workflow

  • No separate workflow server

    The engine is a library in your own .NET host, an existing service or one you add for workflows, and keeps its state in your PostgreSQL database or MongoDB replica set; to scale, you run more instances of that host.

  • Checked when you build

    Workflows are typed C#: the analyzer reports most code that cannot become a workflow as a build error, and each workflow compiles to a canonical JSON definition you can validate, review and draw, so changes by people and coding assistants are checked before they run.

  • Service calls with failure handling built in

    Steps call your services over HTTP, GraphQL or RabbitMQ, including commands that wait for a reply, and the definition says which steps run when a call fails or times out.

  • Human tasks built in

    Roles per workflow and per task, assignment, deadlines with an escalation branch, and an HTTP API that acts as the signed-in user, ready for your own task list.

  • Governed change

    Versions are immutable and running instances keep theirs; a new version stays inactive until an activation that checks the version it replaces, records who made it and why, and treats a return to an older version as an explicit rollback.

Key features

  • Runs inside your own services

    A library in your ASP.NET Core or worker host: no separate workflow server to run, secure or upgrade.

  • Scales out on one database

    Add instances of your service on the same store: they share the signals by lease and the background jobs by lock, and a signal that loses a concurrent change is applied again on the reloaded workflow instance.

  • Processes that wait for days and survive restarts

    Workflow instances wait for people, external signals or timers for as long as the process needs, and resume after a restart.

  • Tasks for people over an HTTP API

    People assign, release and complete tasks through the engine's HTTP API, under your own ASP.NET Core authentication and authorization.

  • Calls, branches, parallel steps and sub-workflows

    Steps call your services over HTTP, GraphQL or RabbitMQ, branch, loop, run branches in parallel and start other workflows.

  • Versions you activate and roll back

    Definitions are written in C# and checked at build time; an imported version stays inactive until an administrator activates it, and an activation can be rolled back.

  • Your own functions, drivers and transports

    Extension points let you add expression functions, signal drivers and transports of your own.

  • Diagrams and replayable dead letters

    Every definition renders as an SVG diagram, and a signal that cannot be delivered waits in a dead-letter list you can inspect and replay.

How it differs from well-known alternatives

ProductHow Stella Ops Workflow differs
TemporalStella Ops Workflow runs the engine inside your own .NET services and database instead of as a separate workflow service. Source, Details
Camunda 8Stella Ops Workflow defines workflows in C# or canonical JSON, checked at compile time, and runs them inside your own services. Source 1, Source 2, Details
Elsa WorkflowsStella Ops Workflow centres on immutable workflow versions with fenced, audited activation and role-based human tasks. Source, Details
Azure Durable FunctionsStella Ops Workflow runs in any .NET host you operate and executes stored workflow definitions instead of replaying orchestration code. Source 1, Source 2, Details

As of 2026-11-08. Each line links the public documentation it is based on. All products, the dimensions and the details: Full comparison.

Go deeper

The licence in plain words Licence and purchase options All components