Skip to main content

roboflow-workflows

Roboflow Workflows execution engine and block library.

roboflow-workflows is the Python distribution for the Workflows engine that powers Roboflow Inference. It can be installed independently for use in standalone pipelines or embedded in the full Inference server.

Changelog and versions

CHANGELOG.md records package changes, including an Execution engine subsection for compile/run behavior changes. Each release records its bundled engine version, starting with package 0.2.2. The package version identifies the distribution; the separate engine version controls workflow and block compatibility. Block-only releases can leave the engine version unchanged.

Earlier engine changes and migration examples remain in the historical engine changelog.

Installation

pip install roboflow-workflows

Optional extras:

pip install "roboflow-workflows[enterprise]"  # enterprise sink blocks
pip install "roboflow-workflows[test]"        # test-only dependencies

Local development (from this repository)

# Provision font assets (required by visualization blocks).
python workflows/build_scripts/download_fonts.py

# Install the package in editable mode with test + enterprise deps.
pip install -e './workflows[test,enterprise]'

# Run package unit and isolation tests.
cd workflows
python -m pytest tests/unit_tests tests/isolation

# Build a wheel from the same project directory (fonts already provisioned).
uv lock --check
uv build --out-dir ../dist

For editing roboflow_workflows source while running the full Inference server, install both projects together from the repository root:

pip install -e ./inference_models -e './workflows[test,enterprise]' -e .

The dev images also support mounting workflows/roboflow_workflows at /app/roboflow_workflows, alongside the existing /app/inference mount. Provision local fonts first, since a bind mount replaces bundled image files.

Font assets

Visualization blocks require pre-provisioned font files. Font binaries are downloaded by workflows/build_scripts/download_fonts.py (or make download_fonts at the repository root) and are gitignored. They are embedded as package-data in the published wheel so that offline environments work without a checkout.

Metadata

Release files for roboflow-workflows 0.2.4.post1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for roboflow-workflows 0.2.4.post1
File Size Uploaded
roboflow_workflows-0.2.4.post1.tar.gz 5.3 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for roboflow-workflows 0.2.4.post1
File Interpreter ABI Platform
roboflow_workflows-0.2.4.post1-py3-none-any.whl Python 3 none any Details

Total release size: 11.6 MB

Release files / roboflow_workflows-0.2.4.post1.tar.gz

Download URL roboflow_workflows-0.2.4.post1.tar.gz
Size 5.3 MB
Tags Source
SHA-256 checksum
How to use checksums
e5aa743a6bfdd53c221bc931742ffd4b4c1e43c31362e98e9d0b80662d2aaead
BLAKE2b-256 checksum
How to use checksums
0456c081430d7586d55bd072d8a9093dc4688547de8a5e2ffe7001992205d637
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.

Transparency log

Release files / roboflow_workflows-0.2.4.post1-py3-none-any.whl

Download URL roboflow_workflows-0.2.4.post1-py3-none-any.whl
Size 6.3 MB
Tags Python 3
SHA-256 checksum
How to use checksums
22d428904a16f71850d3a3f54d45a86a06984cb60c98fc45e45d79b6698a7004
BLAKE2b-256 checksum
How to use checksums
df6326bc51f620e8e5c059951a18078e63ebf074001f960dea4edfc355734fec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page