Tags / Backend and APIs /
Workflow engine
An engine that runs multi-step workflows defined in code, graphs, or BPMN and keeps the state of each step; not a data pipeline orchestrator or a low-code app connector.
Repositories
10
Net stars gained, last 7 days
+545
Top-level Tag
Net stars gained each day, last 90 days
Peak days
- 1
Oct 22, 2026 +292 net stars (median day +94)
- tin-computer/tin+179 (61%)
- mastra-ai/mastra+33 (11%)
Published @mastra/[email protected] on Oct 21, 2026
- temporalio/temporal+30 (10%)
A peak day has at least 2 times the net stars of the median day of this chart, and at least 100 more. For each peak day, the list shows the repositories that gained the most net stars that day. It also shows their GitHub releases of that day or the day before (UTC), and their creation date when it was 14 days or less before. These events occur near the same day. They do not show why the stars came.
Largest
Most stars in total now.
readme:
Keep orchestration as a versioned, inspectable graph while workers and built-in tasks perform business logic and side effects.
readme:
XState provides a powerful and flexible way to manage application and workflow state by allowing developers to model logic as actors and state machines.
readme:
use Mastra's graph-based workflow engine to orchestrate complex multi-step processes.
- dapr/dapr26K
readme:
**Workflow patterns**: task chaining, fan-out/fan-in, monitors, human-in-the-loop with external events, and compensation
readme:
The Temporal server executes units of application logic called Workflows in a resilient manner that automatically handles intermittent failures, and retries failed operations.
readme:
The core stays small: the workflow engine, isolation, durable state, the attention queue and an audit trail.
readme:
Workflows are code too. Each task runs as its own job with its own logs, and waiting for an approval releases the worker:
readme:
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes.
readme:
The DSL defines repeatable steps, uses Jev for focused decisions, and calls an agent when the work needs investigation.
readme:
Save a workflow with its inputs and a schedule. Tin handles its timers, retries, and waits for your approval.
Newest Admissions
Entered the index by the rising rule, newest first.
readme:
The DSL defines repeatable steps, uses Jev for focused decisions, and calls an agent when the work needs investigation.
readme:
Save a workflow with its inputs and a schedule. Tin handles its timers, retries, and waits for your approval.
How a repository gets this Tag
An agent reads the description, the GitHub topics, and the start of the README of each repository. It chooses Tags only from the Tag list in the AwesomeRepos source code. For each Tag, it quotes the text. A code check keeps the Tag only when the quote is in that text. The quote under each repository is that evidence. A Tag does not rank repositories. It does not say that one repository can replace another. To report a wrong Tag, use "Report a problem with this page" on the page of the repository. All numbers on this page count only visible repositories.