Open Source Rust Workflow Management Software

This tool seeks to be a one-stop-shop for building and working with rust-generated WebAssembly that you would like to interop with JavaScript, in the browser or with Node.js. wasm-pack helps you build rust-generated WebAssembly packages that you could publish to the npm registry, or otherwise use alongside any javascript packages in workflows that you already use, such as webpack. This project is a part of the rust-wasm group. You can find more info by visiting that repo! Currently, wasm-pack requires that you have npm installed to pack and publish your package. Long-term, this will be replaced by a Rust-only version. If you would rather use another package manager that interfaces with the npm registry you may, however, the pack, publish, and login commands wrap the npm CLI interface and as a result require that npm be installed.

Windmill is a modern developer platform for building internal tools and automations using scripts written in Python, TypeScript, or Go. It provides a structured way to build, schedule, and share workflows as scripts with secure input forms and audit trails. Unlike traditional low-code platforms, Windmill caters to technical teams who want the flexibility of scripting with the convenience of a collaborative GUI. Users can turn scripts into APIs, schedule recurring jobs, and manage user access through role-based permissions. Its modular design encourages reusability and efficient collaboration across teams.

Arkflow is a Rust-based framework for building reactive, event-driven data pipelines. Inspired by tools like Airflow and Dagster, it focuses on strong typing, modularity, and performance. Arkflow is ideal for developers who want a fast, extensible way to orchestrate workflows and data transformations in Rust.

Flow-Like is a lightweight framework for building flow-based, reactive user interfaces that lets developers structure applications around declarative data flows and event pipelines instead of imperative state management. The core idea is that UI components react to changes in upstream flows, making it easier to reason about how data moves through the system and how user interactions propagate changes throughout the interface. This approach contrasts with traditional two-way binding or manual update patterns by treating flows as the single source of truth, simplifying complex interactions and reducing bugs caused by scattered state logic. Developers can compose and combine flows, establish transformations, and orchestrate asynchronous events using intuitive primitives, resulting in code that is easier to test, maintain, and scale.