Skip to main content
Open source · self-hosted

Release notes your team reviews. Infrastructure you control.

Collect merged work, classify it with explainable rules, review what matters, and publish a note for every audience—from one application running on your own infrastructure.

  • Human-reviewed workflow
  • Docker Compose quickstart
  • Apache 2.0, no open-core split
Product showcase

The two moments every release needs​

Screenshots of ReleaseFlow at work on a sample project, in the language and theme you are reading in.

The Change Inbox: the sync state of a Jira, a GitHub, a GitLab and a Linear source, then a change with its category and review badgesThe Change Inbox: the sync state of a Jira, a GitHub, a GitLab and a Linear source, then a change with its category and review badges

Change Inbox

Review normalized changes from GitHub, GitLab, Linear, and Jira with their category and review evidence visible.

A release in review with five of its eleven changes decided, its previous release, and the preview of its contributor noteA release in review with five of its eleven changes decided, its previous release, and the preview of its contributor note

Release review

Decide on every change before approval, then publish frozen release notes written for each audience.

Self-hosting / quickstart

Run it on one machine in a few commands​

The released quickstart runs ReleaseFlow and PostgreSQL with Docker Compose. There is no repository to clone and nothing to compile.

  • Docker Compose v2 and openssl
  • The application and PostgreSQL—nothing else
  • Application bound to loopback; database not published
Quickstart
mkdir releaseflow && cd releaseflow
base=https://github.com/hoangluongtran0309/ReleaseFlow/releases/latest/download
curl -fsSL --remote-name-all "$base/compose.yaml" "$base/quickstart.sh" "$base/SHA256SUMS"
sha256sum --check --ignore-missing SHA256SUMS
bash quickstart.sh
Then open http://localhost:8080/register

Keep the generated .env file. It contains the database password and the key that encrypts stored credentials.

Privacy & architecture

Your deployment is the system of record​

ReleaseFlow is one Spring Boot application and one PostgreSQL database. You decide where they run and which external services they may reach.

01

Deploy it yourself

Run the same Apache-2.0 code on your infrastructure. There is no hosted control plane or enterprise edition to depend on.

02

Protect stored credentials

Webhook secrets and provider tokens are encrypted with the master key you supply and are never read back into a page or API response.

03

Choose every outbound service

AI, translation, email, and delivery integrations are optional. They run only when you configure and use them.

Community & project health

Inspect the project. Help shape what comes next.​

ReleaseFlow keeps its code, decisions, release history, security process, and contribution path in the open.