Changes.Page is an AGPL-3.0 licensed, TypeScript-based changelog application built on Next.js that lets open-source maintainers and product teams create, host and self-host release notes without hand-maintaining a changelog document.

What it is

Changes.Page is a web application for changelog management, described in its own README as "an open-source solution revolutionizing changelog management" and, in its GitHub description, simply as "Changelog simplified." It lives in the TypeScript and Next.js ecosystem and is shipped as a monorepo containing two applications, apps/web and apps/page, each of which carries its own .env.example file. The stack named in the README is Next.js for the application layer, Tailwind CSS for styling, Supabase for the backing data service, Inngest for background job processing, and Postmark for email delivery. The project publishes a hosted option at changes.page alongside a documented self-hosting path.

The concrete problem it targets is the manual labour of writing and publishing changelog entries: maintaining a changelog by hand, formatting it, and getting it in front of readers. Changes.Page replaces that hand-rolled process with a dedicated application that owns changelog entries and their presentation, so that a project's release history is managed as data in a Supabase instance rather than as free text edited directly in a repository file. The tagline, "Effortless changelog creation for open-source projects," states the intended audience of that replacement directly.

Key capabilities

• Changelog management as a hosted application, with a public instance at changes.page and a documented self-hosting route.
• Monorepo layout with two distinct applications, apps/web and apps/page, each configured through its own .env.example.
• Supabase integration for the backing service, with credentials added during setup.
• Background and scheduled work handled by Inngest.
• Transactional email delivery through Postmark.
• Next.js and Tailwind CSS front end, with the development server reachable at http://localhost:3000.
• One-command local startup through pnpm dev, requiring Node.js >= 18.0.0 and pnpm >= 8.6.2.
• Distributed under the AGPL-3.0 licence.

Who uses it and how

• Open-source maintainers who want a published changelog without editing a changelog file by hand for every release.
• Teams that want the hosted convenience of changes.page rather than operating the stack themselves.
• Organisations that must keep changelog data in their own infrastructure, running the application against their own Supabase instance.
• Self-hosters deploying through Railway, which the README recommends for its automatic deployments, built-in databases and scaling.
• Operators who need background processing and email in the changelog workflow, supplied by Inngest and Postmark respectively.

Getting started

Clone https://github.com/techulus/changes-page, install with pnpm install, copy .env.example to .env in both apps/web and apps/page, add Supabase credentials, then run pnpm dev and open http://localhost:3000. The README also points to Railway as the recommended deployment platform, and a hosted instance is available at changes.page.

How it compares

No list of paid products is provided in the facts, and no comparable tool is named, so this project stands alone in this registry and no head-to-head comparison can be made without inventing one. The only comparison axis the facts actually support is licence: Changes.Page is AGPL-3.0, which obliges anyone distributing a modified version to publish their changes.

When to use it — and when not to

A self-hoster must operate a Supabase instance, provide Inngest-backed job processing and Postmark email credentials, and run Node.js 18 or newer with pnpm 8.6.2 or newer, which is a real operational load for a small project. The README is sparse: it documents setup and the stack, but not the feature set, permissions model or configuration options, and there are no topic tags on the repository to fill those gaps. Anyone who needs a fully documented, batteries-included product, or who cannot take on an AGPL-3.0 obligation, should look elsewhere; the repository shows 284 stars, 10 forks and no open issues.