FerrFlow
ferrflow.com
- Free plan
- Windows
- macOS
- Linux
- Web
- Self-hosted
What FerrFlow is
FerrFlow automates software releases from conventional commits and is designed to run locally or in CI. It can calculate version bumps across repositories or monorepos, write changelogs, tag releases and publish GitHub releases from CI. Teams can choose semver, calver, sequential or zerover versioning. In monorepos, packages can have independent versions, shared paths, dependency chains and package-specific changelogs. FerrFlow lists native support for GitHub, GitLab and self-hosted forges, along with more than 14 version-file formats, including Cargo.toml, package.json, pyproject.toml and Chart.yaml. Alpha, beta, rc and dev pre-release channels can be controlled by branch or flag. Installation and CI options include Cargo, npm, Docker, a GitHub Action and a GitLab CI template. It is a single Rust binary without plugins. FerrFlow says it runs on the user's machine or CI runner, collects no user data and has no telemetry, error reporting, usage analytics or phone-home. It is MIT licensed and free.
Who it suits
FerrFlow suits developers and teams that want commit-based release automation, including teams maintaining monorepos. Its stated deployment model is local execution or a CI runner.
Good to know, and what to watch
- Supports semver, calver, sequential and zerover.
- Versions monorepo packages independently.
- Lists native GitHub, GitLab and self-hosted forge support.
- Offers Cargo, npm, Docker and CI integrations.
- Single Rust binary with no plugins.
- No free trial is listed.
Plans
Every plan and priceFree and open source
Open source
The verdict
FerrFlow brings versioning, changelog and tagging work into a single CI-friendly tool, with explicit monorepo support. Its free MIT license and stated lack of telemetry may appeal to teams seeking a locally run release process.
What the maker publishes
- Company
- FerrFlow is identified as a FerrLabs product; the FerrLabs homepage displays SIREN 104 243 951. source
- Data collection
- The security page states that FerrFlow does not collect, transmit, or store user data and has no telemetry, error reporting, usage analytics, or phone-home. source
- Forge support
- GitHub, GitLab, and self-hosted forges are listed as natively supported. source
- Install options
- The site lists Cargo, npm, Docker, a GitHub Action, and a GitLab CI template as installation or CI options. source
- Monorepos
- Packages can be versioned independently with shared paths, dependency chains, and per-package changelogs. source
- Pre-release channels
- It supports branch-based or flag-based alpha, beta, rc, and dev channels. source
- Purpose
- FerrFlow reads conventional commits, bumps versions across repositories or monorepos, writes changelogs, tags releases, and can publish GitHub releases from CI. source
- Runtime
- FerrFlow is described as a single Rust binary with no plugins, intended to run in CI. source
- Security posture
- FerrFlow says it runs on the user's machine or CI runner and has no account, database, or API endpoint handling user data. source
- Supply chain
- The security page says releases are built in GitHub Actions with build provenance attestations targeting SLSA L3, and that binaries and container images are signed. source
- Version files
- FerrFlow says it supports 14+ version-file formats, including Cargo.toml, package.json, pyproject.toml, and Chart.yaml. source
- Versioning
- It supports semver, calver, sequential, and zerover versioning strategies. source
- Vulnerability reporting
- The security page accepts vulnerability reports by email or GitHub private advisory and states a 90-day default coordinated disclosure period. source
Checked against the maker's pages on 4 Oct 2026.