Changelog tooling for small SaaS teams

You've shipped twelve things since your last changelog. Your customers don't know about any of them.

Deltawire connects to your GitHub repo and drafts a changelog entry from your merged pull requests in plain language. Once a human on your team approves it, it publishes to a hosted page and goes out by email to subscribers.

Book a call →See how it works

"The changelog doesn't get written because writing it takes an hour you don't have during a busy week."

acmehq.io/changelogLast updated 4 months ago

May 12

v2.1 — Dashboard improvements

Improved loading states and fixed several layout bugs on mobile.

Apr 3

v2.0 — New billing system

Switched to Stripe billing.

Feb 18

v1.9 — Performance

General bug fixes.

Since May you've shipped SSO, team permissions, API controls, dark mode, Slack notifications, and a full reporting rewrite. None of it is here.

The four hours you keep postponing.

The sales call

A prospect asks what's new since they last looked. You pull up the changelog. It's four months old. The conversation doesn't recover.

The renewal

A customer deciding whether to stay goes to look at what you've shipped. They find a page that reads like you stopped caring in Q1.

The support ticket

Someone writes in about a problem you fixed six weeks ago. They didn't know it was fixed. Because nobody told them.

The changelog doesn't get written because writing it takes an hour you don't have during a busy week, and it keeps getting pushed until the backlog is so long the task feels impossible.

The mechanism

From merged PR to published changelog. Four steps, one of which is yours.

Most of the work happens automatically. Reading and approving the draft is the step that matters, and that stays with you. Click through to see each stage.

github.com / acmehq / app — merged this week

a3f8c1d

Fix: renewal emails not sending on plan change

maya · 2h ago

b72e9f2

Add bulk CSV export for account admins

tom · 5h ago

c1d4a7e

Improve dashboard load time (query optimization)

maya · 8h ago

3 PRs queued — draft ready to generate

By hand vs. Deltawire

What "doing it manually" actually looks like.

By hand

With Deltawire

Writing the entry

Whoever has time, in an hour of work you keep postponing

Draft generated from merged PRs, ready to edit in minutes

Keeping it accurate

You try to remember what shipped, check Slack, ask the engineer

Pulled directly from the PRs that actually merged

On a busy week

Skipped. It'll go out with the next release. (It won't.)

Draft already waiting. Approve or skip, it was drafted either way

What actually goes out

Whatever you had energy for when you finally sat down

What you approved, after reading and editing it

Who gets told

Nobody, or a Slack post that doesn't reach customers

Subscribers by email, public changelog updated

Why approval isn't optional

Nothing publishes without a human approving it first. That's deliberate.

Automation that publishes on its own can ship incorrect information, expose things you didn't intend to share, or announce something in a way that lands badly. The draft step handles the labor. The approval step keeps you in control of what your customers actually read.

Every entry in your changelog is something a person on your team read and signed off on. That's what makes it worth sending. We're not planning to add an "auto-publish" option. It would undermine the only thing that makes this trustworthy.

AI drafts from real commits

The draft comes from what actually merged, not from summaries you write or content someone made up.

You read and edit

Open the draft, fix anything that's off, add context the PR title didn't capture.

Explicit approval required

One button. Until it's clicked, nothing leaves the dashboard.

Published to page and email

Changelog updates. Subscribers get the email. You ship the next thing.

Common questions

Things you're probably wondering.

What does Deltawire cost?+

We haven't set pricing yet. We're talking to teams first to understand what this is worth to them. If you book a call, you won't be walked into a pricing page. We'll figure out what makes sense together.

Does this automatically publish anything?+

No. Every entry requires someone to open it, read it, edit it if needed, and explicitly approve it. Nothing publishes on its own. That's intentional.

What if our PRs are messy or technical?+

That's the point. The draft translates commit messages and PR titles into plain language, so you're publishing an edited version of what the draft extracted, not the raw PR itself. The approval step is where you fix whatever the draft got wrong.

Do we need to change how we write PRs?+

No. Deltawire works with however your team already merges code. Better PR descriptions produce better drafts, but it's not a requirement.

Can we use our own domain?+

Yes. Each project gets a hosted changelog page on a Deltawire subdomain by default, and you can point a custom domain at it.

Get started

If your changelog is months out of date, let's talk.

We're not taking signups yet. We're talking to teams first, so there's no pitch and no pricing page. You'll talk to a founder directly.