Changes.Page is an open-source changelog platform for publishing product release notes to a hosted page, an embeddable website widget, and RSS. It serves small product teams that want a dedicated place to announce updates, notify subscribers by email, and automate posts from their development pipeline instead of building a release-notes system themselves.[1]
Quick verdict
Changes.Page suits small product teams that want a dedicated changelog page, embeddable widget, and RSS feed without building their own release-notes pipeline. Its concrete strength is developer-shaped publishing: a dashboard plus markdown, a CLI, a REST API, a GitHub Action, and Zapier automation, including CLI input over stdin for AI agents. The material constraint is operational weight: self-hosting needs operator-provided Supabase, transactional email, and KV storage, and billing, custom domains, and AI features only work on specific hosting paths. If you publish web-product updates and can live with per-page hosted pricing or a Docker Compose self-host, choose Changes.Page; if you need customer idea voting and a public roadmap, choose ClearFlask instead.[1][2][3]
Key features
Hosted changelog pages Hosted changelog pages with per-page themes and a dedicated URL for each product's release notes, so updates live somewhere customers can bookmark.[1]
Custom domains with SSL Custom domains with SSL on hosted pages, so the changelog can sit on the team's own domain rather than a shared subdomain.[1]
Embeddable widget An embeddable widget that adds a changelog button and notification badge to an existing site, keeping users in the product while they catch up.[1]
RSS and email distribution Automatic RSS feeds for every changelog page plus email notifications to page subscribers on new posts.[1]
CLI, API, and GitHub Action Publishing from the terminal or CI with the command-line tool, the REST API, or the GitHub Action, including piping content over stdin so AI agents can publish programmatically, with Zapier automation also supported.[1]
Markdown authoring Markdown authoring in the dashboard or terminal, keeping release notes in a portable plain-text format.[1]
Docker and Vercel self-hosting Self-hosting with Docker Compose or a Vercel deploy, backed by Supabase with operator-provided transactional email and KV storage.[1]
AGPL-3.0 with Discussions support An AGPL-3.0 licensed codebase with support routed through GitHub Discussions while the issue tracker stays disabled.[1]
Who will love it
Small teams shipping a web product Small teams shipping a web product who want release notes, a subscriber list, and RSS without building and maintaining that plumbing.[1]
Developers automating releases Developers automating releases who will publish from CI with the CLI, API, or GitHub Action, or pipe agent-generated notes in over stdin.[1]
Supabase and Docker self-hosters Self-hosters comfortable with Supabase and Docker who prefer to own their changelog data under the AGPL-3.0 codebase.[1]
Who should avoid it
Voting and roadmaps needed Teams needing customer voting and roadmaps, where a feedback-portal product with idea boards fits better than a publish-only changelog.[1]
Fully managed expectations Non-technical teams wanting fully managed everything, since widget embedding, automation, and especially self-hosting assume developer involvement.[1][2]
Single-host feature limits Teams that need billing, custom domains, and AI on one arbitrary host, because self-hosted billing is Stripe-only, custom domains are Vercel-only, and AI features need an OpenRouter key.[1]
Running and maintenance notes
Next.js and Supabase stack A Next.js application with Tailwind CSS, Supabase, Inngest, Postmark for email, and Upstash Redis for KV, deployable to Railway or run locally with Node.js 18 and pnpm.[1]
Operator prerequisites Self-hosting prerequisites include the Supabase CLI, Stripe CLI, Resend, and Upstash Redis, so the guide assumes an operator comfortable with those services.[1]
Small maintainer footprint A single-contributor repository with the last commit in August 2026 and CLI v0.3.0 released in March 2026, so adopting teams should confirm the maintenance pace meets their needs.[1]
Questions worth asking
What is the best Changes.Page alternative for non-technical users?
Is Changes.Page really no-code?
How much does Changes.Page cost per month?
The official site offers a 14-day trial, and the published catalogue record describes hosted pricing of $2 per page per month thereafter, with free use for open-source projects and indie hackers arranged through the contact page. Self-hosting the AGPL-3.0 codebase is free apart from the operator's own infrastructure costs. Recheck the official pricing page before purchase.[1][2]
Can you self-host Changes.Page?
Sources and editorial review
Source research. Reviewed on October 9, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- changes.page homepage
official · Observed October 9, 2026
Official homepage: hero positioning, feature list, v2.4.0 release note, FAQ covering trial, custom domains/SSL, email+RSS notifications, CLI/API/GitHub Actions/Zapier automation and AI-agent stdin.
- techulus/changes-page repository
official · Observed October 9, 2026
Official repository: created 2024-01-23, 284 stars, 9 forks, 1 contributor, AGPL-3.0 license, Next.js/Tailwind/Supabase/Inngest/Postmark stack, Railway deploy, Node 18/pnpm local setup, Discussions support with issues disabled, CLI v0.3.0 March 2026.
- SELF-HOSTING.md
official · Observed October 9, 2026
Official self-hosting guide: Docker Compose or Vercel deploy with Supabase, operator-provided email and KV, OpenRouter for AI. Limits: Stripe-only billing, Vercel-only custom domains, OpenRouter key for AI.
Compared with these products
No explicit proprietary baseline is recorded.