changes.page

What It Is

changes.page is a changelog platform built for both “humans and agents,” designed to create, publish, and distribute product updates. It offers a visual Markdown editor, while also allowing release notes to be pushed from a CI/CD pipeline via CLI/API. Its positioning clearly leans toward developer tools, SaaS teams, and open-source project maintainers.

Core Features and Ecosystem

The feature set is fairly comprehensive: the Markdown editor supports live preview and image uploads; users can create public roadmaps with community voting; publishing features include scheduling, reactions, and pinned posts; on the operations side, it provides audience analytics such as referrer, OS, and browser; and teams can invite members for collaboration. Developer-facing capabilities are a highlight. The site explicitly lists JSON API, RSS feed, React SDK, embeddable widget, CLI + API access, and provides a command example for chp posts create. For integrations, it supports GitHub, Zapier, and GitHub Changelog Agent, and also mentions that AI agents can create changelog posts.

Pricing

Pricing is very simple: a single plan at $2/page/month, with a 14-day free trial and no credit card required. Email notifications are an add-on at $0.01/email. Storage and bandwidth follow a fair usage model with no hard limits, though users may be contacted if usage significantly exceeds typical patterns. For small teams and multi-project pages, the pricing is transparent and has a low barrier to entry.

Pros and Cons

The main advantages are its focused product shape, covering manual writing, automated publishing, and embedded distribution in one place. It also includes roadmap, voting, analytics, and team collaboration features, reducing the need to stitch together multiple tools. The drawbacks are that the main copy does not explain self-hosting, SLA, data regions, backups, security compliance, or payment methods. Although “Open Source/Built in public” is mentioned, the license and the actual open-source scope are not provided. On the documentation side, only a CLI example and FAQ headings are currently visible, so the quality of the full API documentation still needs to be verified.

Best Fit and Access from China

It is suitable for SaaS, API, SDK, and open-source project teams that need to publish stable external updates and let developer users subscribe to or view changes. If you currently only use GitHub Releases, changes.page can provide a more productized presentation layer and analytics. Access from mainland China, payment availability, and email deliverability are not disclosed in the main copy, so they should be considered unknown. Alternatives to compare include GitHub/GitLab Releases, Headway, Canny, ReleaseNotes.io, or a self-hosted static changelog.