Skip to main content

​
Why OpenWorkflow exists

A background job can finish several operations before a crash stops it. Restarting the whole job can repeat work that already succeeded. OpenWorkflow saves progress between steps so your code can resume after a crash or deploy. You write workflows in TypeScript or JavaScript and wrap operations in steps. Workers execute them and save the results in PostgreSQL or SQLite. Workflows can retry failed steps, pause on a timer, or wait for a signal before continuing. Your application and workers connect directly to your database, so you can run OpenWorkflow on your own infrastructure. Use it for background jobs, multi-step integrations, data pipelines, and AI workflows that need to keep their progress. The Quick Start walks through running a workflow locally, and the overview explains how workflows, steps, and workers fit together.

​
An open-source project

OpenWorkflow is developed on GitHub under the Apache-2.0 license. The repository includes the workflow engine, CLI, dashboard, documentation, and examples. Bugs, feature proposals, and code changes are discussed there. Contributions can be code, documentation fixes, bug reports, or feedback from using OpenWorkflow. Read the contribution guide before starting a change, and check the roadmap for planned work. See Contact for where to ask questions or report a problem.