Skip to content
Changelog

ship it onceand everyone hears

Write release notes in markdown and publish them to your public page, an RSS feed and a What's new badge inside your app, all at once.

  1. 21 Aug 2026

    Slack integration for alerts

    slackintegration

    Connect slack to usefull notifications

  2. 21 Aug 2026

    Updated and fixed the plugin using plugin-check

    feedfastwordpress

    Now FeedFast plugin is complete clean

  3. 21 Aug 2026

    Team members and roles

    New

    Invite teammates and give them read-only or admin access. Still being written.

  4. 15 Aug 2026

    Scheduled maintenance windows

    New

    You can now announce planned downtime ahead of time. - Pick a window and the monitors it affects - Subscribers get an email when it's sched…

Scroll the timeline. These are live entries from the demo changelog.

one publisheverywhere it should be

Changelogs die because publishing is only step one, and then you still have to tell people. Here, publishing is telling people.

  1. Your page, your feed, your app

    One publish puts the entry on your public page, in a real RSS feed at /p/your-slug/rss.xml, and in the widget on your own site. Every entry gets its own URL, so a support reply can link the exact release.
  2. A badge that says something changed

    Until the user opens it, the floating What's new badge reads New, with the version and the latest title. People find out inside the product they're already using, which is the one place they reliably look.
  3. The people who asked hear first

    Ship a request from your feedback board and everyone who left an email on it gets a note that it's done, with a link to the release.

write in markdownsee it as it ships

A two-pane editor with nothing to learn, or no editor at all when the entry can write itself from the request it closes.

  1. 1

    Markdown left, the real page right

    The preview uses the exact public styles, so what you see while writing is what ships. Tag it New, Improved, Fixed or your own, and add a version if you use one. Drafts stay private until you publish.
  2. 2

    Code that reads like code

    Fence a block with a language and it's highlighted on the server, from hundreds of grammars. Markdown is sanitised before it renders, so no author markup is ever parsed as HTML.
  3. 3

    Or start from the request

    Mark a feedback post Done and the entry is pre-filled: the title, a link back to the post, and a tag from its category, so a bug becomes Fixed and a request becomes New.
  4. 4

    Or let your agent write itPro

    With the MCP server, your coding assistant calls publish_changelog as the last step of the fix. It asks you before anything goes public. The REST API takes the same fields.

Not sure what to write? Start from one of our changelog templates, previewed exactly as they will publish, no account needed.

looks like yoursnot like a tool

A changelog that obviously belongs to someone else is worse than no changelog at all.

  • Your logo and colourProCarried through links, buttons and badges, so the page reads as part of your product.
  • No FeedFast badgeProThe small Powered by FeedFast credit in the footer comes off entirely.
  • Each reader's timezoneDates are stored in UTC and shown in the visitor's own time, with the exact instant kept for feeds.
  • Tags you chooseNew, Improved and Fixed out of the box, as coloured badges. Add your own on top.
  • A link per entryEvery release has its own page, ready to paste into a reply, a tweet or a support ticket.
  • Readable anywhereSet like a publication, readable at 375px, with visible focus rings and reduced motion respected.

15 entries freeunlimited on Pro

  1. Only published entries count

    Free includes 15 published entries, and drafts never count toward them. Reaching the limit deletes nothing: everything stays live, and Pro lifts it entirely.

before youwrite the first one

The REST API for publishing from a script is in the docs.

Can I schedule an entry to publish later?

No, there's no scheduled publishing. An entry goes live when you press Publish, or when your agent publishes it. Drafts are private and unlimited, so you can write ahead and publish on the day.

Can I fix a typo after publishing?

Yes. Edit and save, and the entry keeps its original date and its URL, even if you change the title, so links you've already shared keep working. Unpublishing takes it off the page, the feed and the widget.

Can I add screenshots?

Yes, with markdown image syntax pointing at an image you host. There's no upload in the editor. Tables, task lists and fenced code work too; raw HTML, embedded video and iframes are stripped when the entry renders.

Can readers get release notes by email?

Not yet, with one exception: people who asked for something on your feedback board are emailed when you ship it. Everyone else can follow the RSS feed, or see the What's new badge inside your app.

Does the RSS feed carry the whole entry?

Yes. Each item has the full rendered entry and a link to its own page, so a feed reader shows the release without a click through.

Can I bring my existing changelog over?

There's no importer. On Pro the REST API can create entries, but each one is dated the moment it's published, so a back catalogue would all show today's date. It works better to start fresh and link the old changelog from your first entry.

Can I use the changelog without the feedback board or the status page?

Yes. Each module switches on and off per project, and the hub only shows the tabs that are on. The changelog, its feed and the What's new badge work the same on their own.

Write the first entry today

Free for one project, 15 entries to start, and the widget included. The next thing you ship can tell your users by itself.