Release Compass

Release Compass

Customer-facing changelogs, without opening the repo.

Trigger a draft from CI, Jira, or the API. Rewrite the technical notes for customers, in every language you ship. Publish once — hosted changelog, feeds, and email all update together.

Create an accountView a changelog
  • Dashboard
  • GitHub Actions
  • GitLab
  • Jira
  • MCP
  • API

How it works

Write in the dashboard, or let CI open a draft. Either way, customers never see the ticket.

  1. 01

    Trigger a draft

    CI, a ticketing tool, MCP, or a plain API request can open a draft. GitHub Actions, GitLab, Jira automation, Linear, or anything that can POST JSON or Markdown. Reuse the notes you already have — a generated changelog or the release ticket. We never clone the repo or install an app.

  2. 02

    Edit the customer copy

    Source notes stay frozen. Rewrite the technical changelog into language customers understand — and into every market you ship to. Add media, review, then publish.

  3. 03

    Publish once

    One action updates the hosted changelog plus RSS and Atom, in each language you published. The public page is the customer view — not the engineering log.

  4. 04

    Notify subscribers

    Confirmed subscribers get email for the channels they opted into. Stable, RC, beta, alpha, and canary stay separate.

Technical notes stay in engineering. Customers get a story.

Source is frozen after the draft exists. Release managers rewrite the title and body before anything goes public.

  • Hosted page

    Customer view

  • RSS + Atom

    Follow without an account

  • Email

    By channel

  • Slack + Teams

    Soon

What you get

Secure workflow

No GitHub App, no repository contents, no clone. Every trigger is an HTTP caller with a project API key — CI, tickets, or a script.

Flexible trigger

GitHub Actions, GitLab, Jira, Linear, the API, MCP, or any webhook that can POST. You are not locked to GitHub Releases.

Channel-filtered email

Customers subscribe and choose stable, RC, beta, alpha, or canary. They only hear about channels they care about.

Feeds and Markdown

Public changelogs render Markdown. RSS and Atom stay in sync on every publish, so people can follow you without an account.

Multilingual changelogs

Write customer copy per language. Readers switch language on the public page; RSS and Atom follow. Missing translations fall back to the project default.

Feature and bugfix boards

Collect requests in a public or private board on the free plan. Readers can browse; upvotes arrive only through the API or MCP. You decide whether names are shown.

Embed in your product

Soon

Use our React, Vue, or Angular integration — or integrate it manually.

SSO

Soon

Sign in with your company identity provider. Planned for paid plans, with a trial and no card required.

Slack and Teams

Soon

Post a published changelog to Slack or Microsoft Teams so the rest of the company sees the customer notes too.

AI customer copy

Soon

Turn a technical changelog into a first draft of customer-facing notes. You still review before publish.

Start with a draft. Integrations can wait.

No GitHub, Jira, or API key required. Write the first release in the dashboard, then add CI when you are ready.

Create an accountRead the FAQ