Define data pipelines as DAGs, schedule them, monitor their execution, retry failures. Apache Airflow without the Kubernetes operator and the 2-hour setup.
Running a data pipeline orchestrator should not require a Kubernetes cluster, a managed database, and a DevOps team to keep it running. Pipeline is one file. Download it, run it, point your browser at it. That is the entire setup.
Start Pipeline with a port and a data directory. It creates its SQLite database on first run and serves both the API and the dashboard on the same port. Create pipelines through the web interface or POST JSON to the API. Filter by steps, schedule, or search by keyword. Update records with PUT, delete with DELETE. The stats endpoint returns aggregate counts grouped by status for monitoring.
A non-profit with no DevOps budget downloads the Pipeline binary, sets two environment variables, and runs it on the same Linux box that handles their email. It has been running for three months without intervention. When they need to update, they download the new binary and restart the process.
GET /api/pipelines — List all pipelines. Supports ?q=keyword for search and ?status=value for filteringPOST /api/pipelines — Create a new pipeline. Send JSON with at least nameGET /api/pipelines/{id} — Fetch one pipeline by IDPUT /api/pipelines/{id} — Update fields on an existing pipelineDELETE /api/pipelines/{id} — Remove a pipelineGET /api/stats — Returns total count and breakdown by statusGET /api/health — Returns {"status":"ok"} for uptime monitoringSelf-hosted data pipeline orchestrator. Self-hosted on your infrastructure. Your data never leaves your server.
curl -fsSL https://stockyard.dev/install.sh | sh -s -- --tool pipeline
PORT=9140 ./pipeline
http://localhost:9140
Single binary. Embedded SQLite. No Docker. No database. No dependencies.
Your license key arrives by email within 5 minutes of checkout. Set it as an environment variable and restart the binary.
export PIPELINE_LICENSE_KEY=stockyard_xxxxxxxxxxxxxxxxxxxx ./pipeline
No cloud connectivity required. The binary validates the key offline with Ed25519 signatures.