v1.4.0Stable18 Sep
Billing export for finance teams
Finance can download invoices as CSV. No engineering ticket required.
Release Compass
Customer-facing changelogs, without opening the repo.
Trigger a draft from CI, Jira, or the API. Agent skills rewrite technical notes for customers, in every language you ship. Publish now or schedule a time — hosted changelog, feeds, and email all update together.
- Dashboard
- GitHub Actions
- GitLab
- Jira
- MCP
- Agent skills
- API
How it works
Write in the dashboard, or let CI open a draft. Either way, customers never see the ticket.
01
Trigger a draft
CI, a ticketing tool, MCP, agent skills, 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.
02
Edit the customer copy
Source notes stay frozen. Rewrite the technical changelog into language customers understand — and into every market you ship to. Agent skills can do that rewrite and add translations for you. Add media, review, then publish.
03
Publish once
One action — now or at a time you pick — updates the hosted changelog plus RSS and Atom, in each language you published. The public page is the customer view — not the engineering log.
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
Schedule
Publish at a time you pick
RSS + Atom
Follow without an account
Email
By channel
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, agent skills, or any webhook that can POST. You are not locked to GitHub Releases.
Agent skills
A Cursor or Claude Code plugin rewrites GitHub release notes into customer copy and drives MCP — import history, add languages, publish — so you do not have to remember the tools.
Scheduled publishing
Pick a date, time, and time zone. The note stays off the public changelog until then. Team members with release access can preview drafts and scheduled notes on the hosted page.
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. Optionally let customers file and upvote by email (Turnstile plus a confirmation link), and optionally require an admin or release manager to approve new submissions. API and MCP votes still work. You decide whether names are shown.
Embed in your product
Public React and Angular packages for changelogs and request boards. Next.js server helpers hold your API key for private boards and voting. Vue is coming soon.
SSO
Company OIDC or SAML on the Team plan. Create an organization to start a 30-day trial with no card, then configure your IdP under Organization → SSO.
Slack and Teams
Post a published changelog to Slack or Microsoft Teams so the rest of the company sees the customer notes too.
AI customer copy
Turn a technical changelog into a first draft of customer-facing notes. Bring your own OpenAI-compatible key on Pro or Team. 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.