Recent.dev
Real-time changelog updates for your favorite tools
143 followers
Real-time changelog updates for your favorite tools
143 followers
Stop hunting for updates. Select your stack - from Next.js to Attio - and receive instant email updates the moment your tools change. Stay ahead of breaking changes and new features with a feed curated specifically for you. No noise.
Product Hunt
Novu
@curiouskitty Great question! The honest answer: it's the aggregation + curation combo.
Each of those solutions works for some tools:
- RSS - great when it exists (many don't publish one)
- GitHub releases - only covers open source, misses SaaS tools entirely
- Newsletters - buried in promo content, inconsistent timing
- Page monitors - noisy false positives, no semantic understanding
The feedback we hear most is "I was cobbling together 4-5 different systems and still missing things." Recent.dev provides a single feed in a normalized format, aggregating changelogs from tools that publish in completely different formats (RSS, JSON feeds, blog posts, and release pages).
The "aha" moment is usually: "Wait, I can see Vercel, Tailwind, Linear, and Postgres releases in the same place without setting up anything?" That simplicity is what gets people to switch.
Novu
This is amazing, makes your life much easier to follow project you find interesting, especially right now, with AI in the for front of builders, more projects are being built, and with greater velocity, the ability to see everything in one feed, just makes sense.
Also, @emilpearce and @dima_grossman rock!
Novu
@dima_grossman @tomer_barnea1 The velocity right now is insane - hard to keep up manually. Glad the single feed approach clicks for you. And appreciate the shoutout, that means a lot! 🙏
Novu
@emilpearce @tomer_barnea1 Thanks!
Great idea! How do you retrieve the framework update information?
Novu
@unkn0wndfbx We use a multi-strategy approach since every tool publishes differently:
1. RSS/Atom feeds - when available, this is the cleanest source
2. JSON feeds - some tools expose structured changelog data
3. Structured scraping - for tools that only have HTML changelog pages, we extract and normalize the content
4. GitHub releases - for open source tools that use GitHub's release system
Each tool gets configured with the best strategy for its source. The system runs on a sync schedule, detects new entries, deduplicates, and normalizes everything into a consistent format.
We also have drift detection, if a tool's changelog structure changes or a source starts failing, we flag it for review rather than serving stale data. It's genuinely one of the trickier parts of the product. Changelog formats are all over the place!
Tracking changelogs for the tools in my stack has been a manual process for too long. I'm curious whether there's an API or webhook option for triggering automations when updates come in—useful for teams that want to pipe alerts into their own workflows or internal tools.
Novu
@yamamoto7 Love this use case! Piping updates into your own workflows is exactly the kind of power-user behavior we want to support. Right now we don't have a public API or webhooks, but it's high on our list.
The internal architecture already tracks changes per-tool with timestamps, so the plumbing is there.
Curious: What would your ideal integration look like? A few options we're considering:
- Webhooks (POST to your endpoint when tools you follow ship updates)
- RSS feed per-user or per-collection
- Slack/Discord bot integration
- Public API for polling
Would love to hear what fits your team's workflow best, and will be happy to prioritize based on real demand.