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 in plain language from the work you've merged. Once a human on your team approves it, it goes live on a hosted page and in a small widget inside your app, and on Pro you can email it to your subscribers too.

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

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 code to published changelog in four steps, and you only have to think during one of them.

You start the draft with one click and Deltawire does the writing. Reading and approving it is the step that matters, and that stays with you. Click through to see each stage.

github.com / acmehq / app · merged since your last entry
a3f8c1d

Fix: renewal emails not sending on plan change (#418)

maya · 2h ago

b72e9f2

Add bulk CSV export for account admins (#415)

tom · 5h ago

c1d4a7e

Improve dashboard load time (#412)

maya · 8h ago

3 commits since your last entry · ready to draft

Person working at desk
Laptop with code on table
Person reviewing work on laptop

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 what merged, ready to edit in minutes
Keeping it accurate
You try to remember what shipped, check Slack, ask the engineer
Pulled from the commits and code changes that actually merged
On a busy week
Skipped. It'll go out with the next release. (It won't.)
One click drafts everything merged since your last entry, even if that was months ago
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
Anyone who checks your changelog page or the widget in your app, plus email subscribers on Pro
Knowing if anyone read it
No way to tell, so it's easy to stop bothering
View counts on every entry, plus clicks from the widget

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.

01

AI drafts from real commits

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

02

You read and edit

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

03

Explicit approval required

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

04

Published to your page and widget

Your changelog and in-app widget update when you publish. On Pro, one more click emails your subscribers.

Pricing

What it costs.

Everyone starts on Free. You can upgrade to Pro from Settings once three drafts a month stops being enough.

Free

For getting your changelog online.

$0

  • ✓A hosted changelog page at yourname.deltawire.app
  • ✓Your logo and brand color on the page
  • ✓RSS and JSON feeds, plus a sitemap
  • ✓A subscribe form so readers can follow along
  • ✓3 AI-drafted entries a month, pulled from your GitHub commits
  • ✓An embeddable "what's new" widget for your app (shows a small Deltawire credit)
  • ✓View counts for every entry
Start on Free →

Pro

Recommended

For teams shipping every week.

$29/month

Everything in Free, plus:

  • ✓Your own custom domain
  • ✓Unlimited AI drafts
  • ✓Email every update straight to your subscribers
  • ✓No Deltawire branding on your widget
Get Pro →

Common questions

Things you're probably wondering.

What does Deltawire cost?+

Free is $0 and gets your changelog online: a hosted page, feeds, a subscribe form, the in-app widget, and three AI drafts a month. Pro is $29 a month. It adds a custom domain, unlimited drafts, and email to your subscribers, and it takes the Deltawire credit off the widget. You can sign up and start on Free yourself, or request a call and we'll help you figure out which one fits.

Does this automatically publish anything?+

No. Every entry requires someone to open it, read it, edit it if needed, and click Publish. Nothing publishes on its own, and emailing subscribers is a separate click after that. That's intentional.

What if our commits are messy or technical?+

That's the point. The draft reads your commit messages along with the code changes behind them and turns them into plain language, leaving out internal work a customer wouldn't notice. The approval step is where you fix whatever the draft got wrong.

Do we need to change how we write commits?+

No. Deltawire works with however your team already merges code. Clearer commit messages produce better drafts, but since it also reads the code changes, it isn't a requirement.

Will the drafts sound like us?+

Once you've published three entries, Deltawire uses your most recent ones as a style guide, so new drafts read like the rest of your changelog. Before that, it writes in a plain, neutral voice that you can edit from there.

How does the in-app widget work?+

You paste one script tag into your app. It adds a small tab to the edge of the screen that shows a dot when you've published something new, and clicking it opens a panel with your latest entries, each linking to the full post on your changelog.

Can we see whether anyone reads it?+

Yes. The dashboard shows how many times each entry was viewed on your changelog page and how many people clicked through to it from the widget. We don't track email opens.

Can we use our own domain?+

Yes, on Pro. Every project gets a hosted changelog page at yourname.deltawire.app, and on Pro you can point your own domain at it instead.

Get started

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

You can sign up and start on Free on your own. If you'd rather talk it through first, you'll get a founder directly, and we'll figure out together whether Free or Pro is the right place to start.

Opens an email to hello@deltawire.app with these details filled in. Nothing sends until you do.