Patchlog

Patchlog is a lightweight changelog widget you embed into any web app with a single <script> tag. No npm, no framework, no configuration required.

Once added, a floating "What's new" button appears in your product. Users click it and see your latest release notes right inside the app they are already using, rather than in a separate blog or an email they may never open.

The widget renders inside a Shadow DOM, so it never inherits or leaks your site's CSS, and it behaves the same in React, Vue, Rails or plain HTML. Every project also gets a hosted public changelog page and an RSS feed.

On the paid plan, an official GitHub Action turns your commits into draft entries. Add the action to your workflow and each push is sent for drafting; on the cadence you choose, an LLM writes one draft entry per user-facing change for you to review before anything publishes. Excluded paths such as lockfiles, .env, vendor and build output are stripped on the runner and never leave it. This is the part that matters most in practice, because writing the release notes is usually the reason a changelog goes stale, not installing one.

Other features: scheduled publishing so you can write updates ahead of time and have them post themselves, per-update view and click analytics, light/dark/auto theming with a custom accent colour on Pro, a read-only REST API over your own projects and entries, and 2FA on accounts.

Pricing is flat rather than metered on your traffic: free for 1 project and 25 updates, which displays a small "Powered by Patchlog" badge, or $7 per month ($60 per year) for unlimited projects and updates, badge removal and advanced analytics. Most tools in this category bill per monthly active user, so the cost rises as your app grows even though writing release notes does not get harder.

What Patchlog does not do: no user segmentation or targeting, no NPS surveys, no roadmaps or feature voting boards, and no email digests to your users. The API is read only, so you can pull your projects and entries but not create or publish them, and the GitHub drafting is GitHub only and triggers on pushes rather than pull requests or release tags. If you need feedback collection or a roadmap in the same tool, Beamer or Canny is genuinely the better fit.