Changelogs deserve more
than a Notion doc.

Drumroll exists because the moment after you ship is undervalued. Engineering teams pour weeks into a release and then surface it with a Slack message and a stale Notion page that nobody reads.

Most changelog tools either treat releases as marketing announcements (heavy CMS, scheduled posts, image carousels) or they hide them behind a help-desk widget customers never click. Neither feels right when your release process already lives in JIRA fix versions and Bitbucket tags and the Markdown files you commit to the repo.

Drumroll’s thesis: the changelog should follow your release mechanics, not replace them. Pull from where you already ship. Keep the page itself fast and uncluttered. Make embedding it inside your own product trivial. Charge nothing while it’s the kind of tool a small team would just self-host if it didn’t exist.

It’s a single-developer project. The roadmap is opinionated - we’ll add what makes the changelog itself better, and resist the gravity toward becoming a feedback portal, a roadmap tool, or another email-marketing surface.

If that resonates, the easiest way to feedback is to actually use it. Sign up and tell us what’s missing via the feedback widget in the bottom-right corner of every page.