Changelog page

A changelog page is a feed of product updates: entries by date and version with “new”, “improved”, “fixed” labels. Users filter by change type, subscribe to updates and learn what has appeared. Unlike a roadmap page, which shows PLANS and collects votes and ideas for the future (see the “Roadmap page” service), a changelog is proof of progress: the history of what is already shipped. Ready services (Headway, Beamer, Canny) are cheap and cover a standard changelog — if that is enough, use them. Your own page is needed when you need things they lack or charge a lot for: single sign-on (SSO) with your product, different changelogs for different user groups (beta, plans), multiple languages, hosting in your own environment without vendor lock-in, deep integration with releases and permissions. The base price starts from 50,000 ₽; the total depends on the categories, subscriptions and integrations.

• Users do not know you ship updates — it seems the product is standing still.
• They learn about improvements only from emails or by chance — there is no single “what is new” place.
• Support is asked “have you fixed or added X yet?” — there is no public list of changes.
• Changes pile up in the tracker and developer release notes — clients cannot see this.

• Entry feed: date, version, list of changes
• Change categories: new, improved, fixed — with colored labels
• Filter by type and product area, search across updates
• Update subscription: email, RSS, Telegram (of your choice)
• Segmentation: different updates for different user groups (beta, plans) — optional
• Your own brand, domain and sign-in; a link to the roadmap (what is planned)
• Integration: auto-posting from releases or a tracker, migrating an archive of entries (optional)
• Responsive, fast loading; SEO foundation — updates get indexed

• Users see the product is alive and evolving — higher trust and retention
• A single “what is new” place instead of emails and guesswork
• You can show different updates to different user groups (beta, plans) — which standard services do not offer
• Subscribers learn about updates right away — a reason to return to the product

• You leave a request and describe how releases ship and which categories you need
• We design the feed, categories, subscription and integrations
• We develop, migrate past entries and launch

• How is a changelog different from a roadmap?

  A roadmap shows plans and collects votes and ideas for the future. A changelog proves you ship them: a list of released changes by date. They are linked: from the roadmap a task moves to the changelog after release. These are different scenarios — expectations vs history.

• Can updates be posted automatically from releases?

  Yes, if you have release notes or a tracker (GitHub, Jira, etc.) — we set up auto-posting or import. Note: not all data is imported automatically, and sometimes adjustments are needed on your side (tags, format). Without integration, entries are maintained via a convenient editor.

• How much does it cost and what does the price depend on?

  The base price starts from 50,000 ₽ for a changelog page with categories, filtering and subscription. The price includes a custom design on brand, category and subscription setup, migration of an archive of entries and integration with releases — without vendor lock-in. If a ready service on a subscription is enough, it is cheaper to start with. Complex integrations and segmentation are estimated separately.