whatisgithub

What is orchestrator?

webstonehq/orchestrator — explained in plain English

Analysis updated 2026-05-18

17RustAudience · developerComplexity · 3/5LicenseSetup · moderate

In one sentence

A single-binary workflow automation tool with YAML or visual flow editing, cron scheduling, and plugin-based tasks in any language.

Mindmap

mindmap
  root((Orchestrator))
    What it does
      Workflow automation
      Single binary
      Plugin tasks
    Tech stack
      Rust
      SQLite
      Docker
    Use cases
      Schedule cron jobs
      Fan out parallel tasks
      Automate API calls
    Audience
      Developers
      Ops teams
    License
      MIT

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Schedule and run cron-based automated workflows without setting up a separate database or scheduler.

USE CASE 2

Fan a task out over a list of items and watch progress on each item live.

USE CASE 3

Write a custom plugin in any language to add a new task type to a flow.

USE CASE 4

Route flow execution to separate worker machines while keeping one server as the control plane.

What is it built with?

RustSQLiteDockerYAML

How does it compare?

webstonehq/orchestratoracoyfellow/t2tarcanorca/sunreactor
Stars171717
LanguageRustRustRust
Last pushed2026-07-17
MaintenanceActive
Setup difficultymoderatemoderatemoderate
Complexity3/53/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Building from source needs Rust and Node.js, or use the prebuilt Docker image instead.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

So what is it?

Orchestrator is a workflow automation tool that ships as one single program, without needing a database server or separate services to install. A workflow, called a flow, is an ordered list of tasks, where each task type is a small plugin bundle that can be written in any programming language, and the tool ships with one built in plugin for making web requests. Flows can be edited two ways at once, either as plain YAML text or through a visual drag and drop builder, and both stay in sync with each other. The tool supports scheduling flows with cron style timing that respects time zones and has configurable rules for what happens if the program was offline when a scheduled run should have fired. It can fan a task out to run in parallel over a list of items, with a live view showing progress on each item individually. Every time a flow is saved it keeps a full history of past versions that can be restored later, and sensitive values like passwords or API keys can be stored encrypted, with those values hidden from logs and results. The entire program, meaning the web interface, the programming interface, the scheduler, and the part that actually runs tasks, is built as one Rust program with its data kept in a single SQLite database file. The visual interface itself is a single embedded web page, so nothing extra needs to be hosted separately. It requires creating a username and password on first launch, which the documentation notes makes it reasonably safe to expose on a public web address. While a run is happening, its status, progress counters, and logs stream live to the browser. For heavier setups, execution can also be routed to separate worker machines while the main program stays in control, rather than running every task on the same machine as the web interface. To try it, a developer needs Rust and Node.js installed to build it from source, or can instead run a ready-made Docker container that already includes everything needed. A guided demo script is included that sets up a sample flow, triggers a run, and follows its progress automatically. The project's code is released under the MIT license.

Copy-paste prompts

Prompt 1
Help me build and run Orchestrator locally using cargo build and the shipped http.request plugin.
Prompt 2
Walk me through deploying Orchestrator with Docker and persisting its data volume.
Prompt 3
Show me how to write a flow YAML file with a cron trigger and a parallel fan-out task.
Prompt 4
Explain how to write a custom plugin bundle for Orchestrator in my own language.

Frequently asked questions

What is orchestrator?

A single-binary workflow automation tool with YAML or visual flow editing, cron scheduling, and plugin-based tasks in any language.

What language is orchestrator written in?

Mainly Rust. The stack also includes Rust, SQLite, Docker.

What license does orchestrator use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is orchestrator to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is orchestrator for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.