Elsa Workflows
A workflow library for .NET that runs workflows inside your own application, defined in C#, in JSON or with a visual designer.
What is Elsa Workflows?
Elsa adds workflow execution to any .NET application. You can write workflows in C#, describe them in JSON, or draw them in Elsa Studio, the visual designer, and run them in the same process as your app or on a dedicated server. A Docker image with the server and the designer is available for a quick trial, though its authors note it is not meant for production as is.
Good fit if
- Your stack is .NET and you want workflows embedded in your own application.
- You need both developers in C# and analysts in a visual designer to work on workflows.
- You want an MIT-licensed engine with no paid parts.
Look elsewhere if
- You want a standalone automation tool with ready integrations: n8n or Activepieces.
- Your services are not .NET: Temporal supports many languages.
Before you adopt it
Elsa is MIT-licensed, and nothing in the repository is paywalled. In June 2021 it moved from a BSD license to MIT. About 94% of commits in the last 90 days come from a single author, so the project's pace rests on one person.
Drafted with AI from the project's README and repository data, then checked against that data on 30 October 2026. Report a correction
Elsa Workflows health: is it still maintained?
75 of 100, actively developed
Read from GitHub on 1 November 2026. How the score works
Elsa Workflows license: is it open source?
Elsa Workflows uses MIT, an open-source license approved by the OSI.
- October 2018First published on GitHub under BSD.
- 13 June 2021Changed to MIT. Commit: Switch to MIT license
- TodayMIT.
How to run Elsa Workflows yourself
- Docker
- Dockerfile or compose file in the repository
- Compose file
- docker/docker-compose.yml: 9 services (postgres, mysql, mongodb, rabbitmq, redis)
- Setup effort
- 4 of 5, judged from the compose file
- Kubernetes
- No Helm chart in the repository
- Desktop and mobile
- No app builds in GitHub releases
- Interface languages
- 3 languages
Install instructions: elsaworkflows.io or the README on GitHub.
Alternatives to Elsa Workflows
- ConductorConductor is an event driven agentic workflow engine providing durable and highly resilient execution engine… 78 health · Apache-2.0 · 32.4k stars
- StackStormStackStorm (aka "IFTTT for Ops") is event-driven automation for auto-remediation, incident responses,… 48 health · Apache-2.0 · 6.6k stars
- ActivepiecesAI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with… 81 health · MIT · 25.3k stars
- InngestThe leading workflow orchestration platform. Run stateful step functions and AI workflows on serverless,… 75 health · Server Side Public License · 6k stars
- Trigger.devTrigger.dev – build and deploy durable AI agents and workflows 84 health · Apache-2.0 · 16.7k stars
Questions about Elsa Workflows
Is Elsa Workflows open source?
Yes. Elsa Workflows is published under MIT, an OSI-approved open-source license.
Is Elsa Workflows still maintained?
Its health score is 75 of 100 (actively developed). It had 2,095 commits in the last 90 days, the latest on 1 November 2026, and its latest release came out on 4 October 2026.
Did Elsa Workflows change its license?
Yes. It moved from BSD to MIT on 13 June 2021.
How do I run Elsa Workflows?
You can run it with Docker. The README on GitHub has the exact steps.
What are the alternatives to Elsa Workflows?
Close alternatives in the Workflow automation category include Conductor, StackStorm, Activepieces.