Changes.page

Best Self Hosted Alternatives to Changes.page

A curated collection of the 4 best self hosted alternatives to Changes.page.

Hosted service to create and publish changelog and update pages, monitor web pages for content changes, and send alerts (email, RSS). Provides public roadmaps with voting, visitor analytics, custom domains/branding, developer-friendly feeds (JSON/markdown) and integrations.

Alternatives List

#1
Feedbase

Feedbase

Open-source feedback collection and changelog tool to centralize user requests, discussions, and product updates from a single dashboard.

Feedbase screenshot

Feedbase is an open-source product management tool for collecting user feedback and communicating product updates in a centralized public hub. It helps teams capture requests, engage with users, and share what changed via a simple changelog experience.

Key Features

  • Public feedback hub for collecting user feedback and discussions
  • Central dashboard to manage feedback and respond to user input
  • Changelog publishing to share product updates and keep users informed
  • Prioritization-oriented workflow (early-stage product direction)
  • Built-in auth and database integration via Supabase

Use Cases

  • Collect and triage feature requests from a product community
  • Publish release notes and updates in a lightweight changelog
  • Create a single place for customers to discuss and track product improvements

Limitations and Considerations

  • Project is in early development; some planned features (roadmaps, deeper analytics, more integrations) may be incomplete or evolving

Feedbase fits teams that want an open-source alternative to hosted feedback boards and changelog tools. It is especially suitable when you want a customizable public hub paired with an internal dashboard for managing updates and user input.

647stars
45forks
#2
Openchangelog

Openchangelog

Convert changelog Markdown files into a searchable, themeable changelog website with RSS, GitHub sync, password protection, analytics, and embeds.

Openchangelog screenshot

Openchangelog transforms changelog Markdown files into a dedicated changelog website that is easy to configure and self-host. It supports common changelog formats (single CHANGELOG.md or one file per release), offers search and RSS, and can sync releases from GitHub or local folders.

Key Features

  • Renders keep-a-changelog or per-release Markdown into a styled changelog site
  • Full-text search with category filtering for quick discovery of release notes
  • Automatic RSS feed generation for new releases
  • Password protection for private or internal changelogs
  • Custom domains, light/dark/system themes, and colorful release tags
  • GitHub integration to sync changelogs directly from repositories
  • Next.js embed support to insert changelog content into external sites
  • Built for containerized deployments with a straightforward YAML configuration

Use Cases

  • Publish product release notes as a dedicated, searchable changelog website
  • Serve internal release communications protected by a password for teams
  • Embed recent changelog entries into a marketing or docs site via Next.js

Limitations and Considerations

  • Focused specifically on changelogs; it is not a full-featured CMS or WYSIWYG editor
  • Content must be provided as Markdown files (repository or folder-based workflows)

Openchangelog is a lightweight solution for teams that want a polished changelog site driven by Markdown and CI workflows. It emphasizes simple configuration, GitHub integration, and easy deployment for publishing release notes.

282stars
21forks
#3
ShipShipShip

ShipShipShip

Modern self-hosted changelog and roadmap app with voting, emoji reactions, kanban roadmap, themeable public changelog, automated newsletters, and a REST API.

ShipShipShip screenshot

ShipShipShip is a lightweight, self-hostable changelog and roadmap web application for sharing product updates and collecting community feedback. It combines a public-facing changelog with an admin dashboard to manage events, statuses, and communications.

Key Features

  • Rich event management with a WYSIWYG editor (TipTap) supporting markdown-style content, tags, and media uploads
  • Emoji reactions (multiple reaction types) and a voting system for community feedback on proposed features
  • Kanban-style roadmap / board with drag-and-drop statuses for planning and tracking work
  • Theme system to install and customize public changelog appearance via theme manifests
  • Automated newsletter/email system with configurable SMTP and status-based triggers
  • Full-featured SvelteKit admin UI and a RESTful API for integrations and automation
  • Docker-ready deployment and single-file SQLite data storage for simple self-hosting

Use Cases

  • Publish release notes and maintain a public changelog to keep users informed
  • Run a community-driven roadmap where users vote and react to proposed features
  • Automate announcement emails when items change status (e.g., when features are released)

Limitations and Considerations

  • Default storage is SQLite (single-file); this is convenient for small deployments but may not scale for very high-traffic or multi-tenant installations
  • Email delivery requires proper SMTP configuration; deliverability depends on the chosen SMTP provider
  • Advanced enterprise features such as built-in SSO/LDAP or clustering are not provided out of the box

ShipShipShip is suitable for teams that want a focused, themeable changelog and roadmap tool with community voting and integrated newsletter automation. It emphasizes simplicity and developer-friendly deployment with Docker and a REST API.

237stars
10forks
#4
Webcap

Webcap

Webcap is a self-hosted tool to capture, screenshot, and archive web pages for later reference, sharing, and documentation.

Webcap screenshot

Webcap is a self-hosted web capture utility focused on turning URLs into durable artifacts you can reference later. It captures pages as images (and/or printable exports, depending on your configured capture pipeline) and organizes results so teams can keep evidence of how a page looked at a point in time.

Key Features

  • URL-to-capture workflow to create repeatable “snapshots” of web pages
  • Headless-browser based rendering for accurate visual captures
  • Organized capture history for auditing and traceability over time
  • Shareable capture outputs suitable for documentation and reporting
  • Simple, lightweight deployment oriented around running on your own server

Use Cases

  • QA/regression: keep visual evidence of UI changes across releases
  • Compliance/audit: preserve proof of published web content at specific dates
  • Research/OSINT: archive web pages before they change or disappear

Limitations and Considerations

  • Accuracy depends on headless rendering and target-site behavior (dynamic content, bot checks, auth walls)
  • High-volume or large-page captures can be resource intensive (CPU/RAM)

Webcap fits teams that need a practical way to preserve the “state” of a URL as a reproducible artifact. It is especially useful for documentation, audits, and visual change tracking where screenshots and archived outputs are preferable to bookmarks.

Why choose an open source alternative?

  • Data ownership: Keep your data on your own servers
  • No vendor lock-in: Freedom to switch or modify at any time
  • Cost savings: Reduce or eliminate subscription fees
  • Transparency: Audit the code and know exactly what's running