Wexflow is an open-source, cross-platform workflow automation engine written in C# for developers and technical users who need to automate file operations, system processes, scripting, networking, scheduling and alerts instead of maintaining that plumbing by hand.

What it is

Wexflow is a workflow automation engine distributed both as the Wexflow NuGet package and as the aelassas/wexflow Docker image. It runs on Windows, Linux, macOS and Docker, and executes workflows in two shapes: sequential and flowchart. Jobs are defined as workflows, scheduled with cron expressions, and run on demand or on a schedule. A web dashboard provides a drag-and-drop visual designer, real-time workflow statistics and monitoring, and extensive logging. The engine ships with more than one hundred built-in activities, supports 6+ database engines, and is extensible with custom activities installed from NuGet.

The problem it solves is the everyday technical automation that accumulates around a codebase or an operations team: moving and uploading files, sending emails, running scripts, and scheduling batch processes. That work is usually handled with hand-written scripts and one-off scheduled jobs which are hard to visualise, monitor and hand over. Wexflow replaces those scattered scripts and schedulers with a single engine in which each job is a declared workflow carrying a cron schedule, a visual definition, a run history and logs. Where the built-in activity set falls short, an activity is written and installed as a NuGet package rather than bolted on as yet another script.

Key capabilities

• Cross-platform workflow server running sequential and flowchart workflows on Windows, Linux, macOS and Docker, with support for 6+ database engines.
• Cron-based scheduling for recurring jobs and batch processes.
• 100+ built-in activities spanning file operations, system processes, scripting and networking.
• Visual workflow designer with a drag-and-drop interface in the web dashboard, alongside real-time workflow statistics, monitoring and extensive logging.
• Push Notifications via SSE, giving real-time workflow job updates without polling.
• RESTful API with official client examples in C#, PowerShell, JavaScript, PHP, Python, Go, Rust, Ruby, Java and C++.
• Custom activities packaged and installed via NuGet, asynchronous workflow execution, error monitoring, and protection against XSS, XST, CSRF and MITM.

Who uses it and how

• Developers and technical users automating file operations, system processes and scripts, expressing each job as a workflow instead of an ad-hoc script.
• Operations and data teams scheduling recurring batch processes with cron expressions and checking run history and logs in the web dashboard.
• Teams wiring Wexflow into existing systems through the RESTful API, or driving it from the official C#, PowerShell, JavaScript, PHP, Python, Go, Rust, Ruby, Java and C++ clients.
• Organisations that need self-hosted automation, running the engine, dashboard and admin panel as a single Docker container on Windows, Linux, macOS or a container host.
• Teams whose cases exceed the built-in activity set, who write their own activity and install it via NuGet.

Getting started

Run from the official Docker image on Docker Hub with docker run -d -p 8000:8000 --name wexflow aelassas/wexflow:latest, which serves the admin panel at http://localhost:8000. The same engine can be installed from the Wexflow NuGet package or downloaded from the latest release, with installation and getting-started steps in the project wiki.

How it compares

No list of paid products that Wexflow replaces is provided in the facts, and no comparable tools are named alongside it in this registry, so on the available evidence it stands alone here. Any assessment against commercial workflow platforms is therefore not supported by the supplied material.

When to use it — and when not to

A self-hoster operates the engine, the web dashboard and one of the supported database engines, and must change the default admin / wexflow2018 credentials immediately after the Docker image starts, because the image ships with them enabled. Teams that want a fully managed hosted automation service, or a visual low-code platform aimed at non-technical business users, will find Wexflow's developer-facing activity and scripting model a poor fit. The README is also thin: it documents features, a Docker quick start and the MIT licence, and leaves installation detail, sizing and upgrade guidance to the wiki and release pages.

docker run -d -p 8000:8000 --name wexflow aelassas/wexflow:latest