Publish release notes inside the documentation portal, next to the pages they change. Free text, badges where they help, and an RSS feed generated for you. No second tool, no second bill, no separate thing to style.
Changelogs are included on every plan. Compare plans →
An entry is a page. Prose, code blocks, screenshots, callouts, tables: whatever the release actually needs. Add a New, Improved, Fixed or Breaking badge when it earns its place, and leave it off when it does not. Readers get a clean timeline in the sidebar either way.
Every account can now subscribe to events instead of polling. Six event types to start with, more on the way.
An RSS feed for the developers who subscribe to things, an entry in the docs for everybody who will find it through search six weeks from now, and a block on your landing page for the people who never go looking at all.
Entries live independently of your versions, so cutting v4 never strands the release notes that explain how you got there.
Every entry is indexed the moment it is published, by the search bar in your portal and by the AI Assistant. When somebody's integration breaks at two in the morning, the change that caused it is one query away, in your docs or through Google.
Draft them on a branch, review them in a pull request, let the agent write the first version, and gate them if the release is not public yet. The same workflow as everything else in the portal.
Changelog posts sync both ways. Write the entry on a branch alongside the code that caused it, open the PR, and the same native checks run before anybody merges.
The agent turns a week of merges into a draft entry, in your voice, with the affected pages updated in the same changeset. You edit the tone and press publish.
Put the changelog behind the same access rules as the docs around it. Beta customers see the beta notes, everybody else sees the release they are actually on.
The changelog inherits the portal it lives in: logo, colours, custom domain, white-labelled throughout. When somebody in procurement asks for the release history, export the lot.
Logo, colours and custom domain, inherited from the portal.
Gate entries behind SSO or JWT for authenticated customers only.
Indexed by the AI Assistant, all the way back to the first entry.
Its own indexed URL, so Google finds the breaking change too.
Readers see only the entries that touch their integration.
The full history as a structured PDF or Markdown file.
Teams arrive here with a changelog tool, a status page, a mailing list and a docs site that disagree with each other. The changelog is part of the docs, so there is nothing to keep in sync.
Write the entry in the same editor as the docs, publish it to the same portal, and let RSS handle the distribution. Fourteen days free, no card, no sales call unless you want one.
