RivalMove
Log inSign up

Competitor release monitoring

Competitor release monitoring with release-level analysis

Competitor release monitoring tracks the releases competitors publish — versioned release notes, changelog entries, GitHub releases — so a team knows what shipped and when. RivalMove monitors those sources every four hours, groups entries into releases (same source, same day), classifies each release by strategic area and importance, and computes release momentum against the competitor’s own cadence.

Start free See live company pages
Strategic direction · last 90 daysreleases / prev.
AI & Automation↑↑↑7 / 2
Integrations↑↑4 / 1
Pricing / Monetization↑2 / 1
Collaboration→1 / 1
Mobile↓0 / 2
Illustrative example — arrows are computed from real, dated public releases in the product.

Release notes are where the truth is — and nobody reads them

  • Release notes are long, technical and published on their own schedule.
  • A single release can contain twenty lines; counting lines makes busy competitors look strategic.
  • GitHub releases of developer tools rarely reach product managers.
  • Version numbers hide what actually changed.
  • Historical release cadence — is it speeding up or slowing down? — is never measured.

From release notes to release intelligence

  1. 1Add the release sources — Release-notes pages, changelogs and GitHub repositories; the catalog has them pre-verified for 700+ companies.
  2. 2Scan and date — Each release gets its publication date from metadata, JSON-LD, <time> elements or the GitHub API.
  3. 3Extract what shipped — A language model reads each release and lists the concrete changes with a one-line digest.
  4. 4Group into releases — Lines shipped together count once; breadth adds a small bonus, not a multiplier.
  5. 5Measure cadence and momentum — Releases per area over the period versus the previous one, normalised to the competitor’s usual rhythm.
  6. 6Surface shifts — Major strategic shifts trigger notifications; everything else is visible in the feed.

Release-level features

Release grouping

Same source, same day = one release, so changelog verbosity does not inflate momentum.

Release count per area

The direction table shows releases (current / previous), not raw entries.

GitHub releases

Public repositories monitored through the GitHub API, including pre-releases and tags with notes.

Comparative timeline

Releases of several competitors on one timeline, dot size by importance.

Source status

Last check, last change and errors per source.

Evidence under arrows

Click any arrow to see the releases that produced it.

Illustrative example

Competitor X publishes a 30-line release every Tuesday. Counted by lines it looks like the most active company in the matrix; counted by releases it ships once a week, mostly maintenance. RivalMove reports Developer Tools at → (steady, 12 releases vs 13) and flags one Security release as a strategic signal because it introduced SSO — the only entry that changes the picture.

Illustrative scenario. Real output is derived only from a competitor’s public updates and links to each of them.

Who it is for

  • Product managers
  • Developer-tool and platform teams
  • Product marketers
  • Founders
  • Competitive intelligence teams

Release monitoring vs release intelligence

A release monitor tells you a new version exists. A diff tool tells you the text changed. Neither tells you whether the release matters or whether the cadence is shifting.

RivalMove reads the release, classifies it, counts it once, and compares the period with the last one against the competitor’s own baseline. That is what makes an arrow trustworthy — and every arrow shows the releases underneath.

Frequently asked questions

What is competitor release monitoring?

Tracking the releases competitors publish through release notes, changelogs and GitHub, with their dates and contents, to understand what shipped and how the release cadence evolves.

Does RivalMove treat ten changelog lines as ten releases?

No. Entries from the same source on the same day are grouped into one release. Momentum is computed on releases with diminishing returns, so volume alone does not create momentum.

Can RivalMove monitor GitHub releases?

Yes. Public repositories are read through the GitHub releases API; each release is dated, summarised and classified like any other update.

How do I see release cadence?

The direction table shows releases in the current period versus the previous one per strategic area; the comparative timeline shows releases over time across competitors.

What if a competitor has no release notes?

Use their blog, public roadmap or RSS feed. RivalMove also follows new article links from listing pages and dates them from the article itself.

Related reading

Also: live company pages · comparisons · pricing

Track your first competitor in a minute

Paste a changelog URL or pick a company from the catalog. The first scan runs immediately; every signal links to its public source.

Start free — 1 competitor, no card See live examples