changes.watch
The community-rated changelog for the software ecosystem.
Every SaaS product, API, cloud provider, developer tool and platform changes constantly. But those changes are scattered across changelogs, blogs, docs, GitHub releases, pricing pages, emails, status pages and terms pages.
changes.watch brings important product changes into one public feed, classifies them by impact, and lets the community rate what actually matters.
One place for product-change intelligence.
changes.watch helps developers, founders, indie hackers, product teams, security teams and small businesses track important changes across the tools they depend on.
Discover
Important product changes in one public feed, classified by impact type.
Follow
Track products by dependency — SaaS, APIs, devtools, infra, AI platforms.
Rate
Mark updates as useful, noisy, risky, broken, or worth trying.
Subscribe
Weekly and personalized product-change digests for your stack.
Audit
Scan your dev stack against recent changes, deprecations and breaking updates.
Contribute
Submit missing changes; claim and manage your own product page.
A single unnoticed change can break your product.
Modern teams depend on dozens of external products: SaaS tools, APIs, AI platforms, cloud providers, devtools, payment providers, auth providers, analytics tools and collaboration platforms. A single unnoticed change can affect pricing, API behavior, limits, security posture, documentation, legal terms, integrations or user experience.
Today, every vendor publishes updates differently. Some changes are announced clearly. Others are hidden in docs, emails, release notes, GitHub releases, pricing pages or terms pages. changes.watch creates a public intelligence layer for these product changes.
What it looks like today.
Live MVP on Vercel — pre-launch, bootstrapped, pre-revenue.
changes.watch is live and hosted on Vercel. Bootstrapped, pre-revenue, and building a free community layer first. The MVP already includes public product pages, product-change timelines, community ratings, watchlists, digest subscriptions, stack audit, submit change flow, claim product page flow, source links and categorized updates.
Update signals include automated classification, source-level metadata, and early community ratings collected during pre-launch.
Organic usage before any launch.
changes.watch has not launched publicly and has not used paid marketing. All current traffic is from direct, organic social and referral channels.
Built on Vercel, public and content-heavy.
changes.watch is a public, content-heavy product with many indexable product and update pages. During initial database population, the product generated nearly 1,000 public update pages and hundreds of weekly archive pages, which created an early ISR Writes spike on Vercel.
This spike was caused by initial content population, not by a runaway traffic pattern. Ongoing write volume is expected to be significantly lower as new updates are added incrementally.
Infrastructure credits would help keep the public community layer stable while we prepare for Product Hunt, Vercel Day and broader launch, and would allow us to expand tracking, classification, digest delivery and community features without limiting access for early users.
Vercel is a strong fit because changes.watch depends on fast public pages, dynamic product timelines, indexable update archives, and a smooth experience for developers and founders.
Credits translate directly into growth.
What's coming next.
Siarhei · changes.watch
Interested in startup credits, partnerships, press, or anything else?