Most monitoring tools focus on infrastructure you control. Versionveil monitors the vendors you depend on — OpenAI, Stripe, Vercel, Supabase, Anthropic and more. It detects API, pricing, SDK, and infrastructure changes in real time, explains why they matter with AI-generated impact analysis, and routes alerts to Slack, Discord, or email before changes become production problems.
No reviews yetBe the first to leave a review for Versionveil
Maker
📌
Product Hunt, meet Versionveil 👋
Engineering teams get blindsided by vendor changes all the time. An API deprecation. A pricing restructure buried in a blog post. A subtle behavior change that takes down production at 2 AM.
The problem isn't that these changes don't get announced — it's that they're scattered across changelogs, docs pages, pricing tables, and RSS feeds for a dozen different vendors. And no team has the bandwidth to watch them all manually.
Versionveil does one thing well: continuously monitors the vendors you depend on, detects meaningful changes, analyzes their impact with AI, and sends severity-ranked alerts to Slack or Discord — in plain English.
The scraper engine handles docs pages, changelogs, pricing pages, API schemas, and RSS feeds across 10 vendors on a 30-minute cadence.
A bit about the build:
I built an initial version over 4 days — landing page, dashboard, Stripe integration, auth. About 52 commits in. But the architecture didn't sit right with me. The scraping config was too rigid, the workflows were tangled, and I kept fighting the abstractions.
So I started over. Clean slate.
The rewrite (10 days, 61 commits):
- Day 1-2: Supabase SSR, Cloudflare Workers, database schema, vendor scraping skeleton
- Day 3: Migrated from Cloudflare Workflows to Trigger.dev — better observability and retries for long-running scrape jobs
- Day 4-5: Slack and Discord OAuth integrations, Stripe billing, notification delivery
- Day 6-7: Dashboard UI, onboarding flow, vendor management, plan limits
- Day 8-9: AI-powered diff analysis via OpenRouter, test infrastructure, SEO, structured data, sitemap
- Day 10: Replaced Browserless.io with a local Puppeteer instance — one less external dependency
The rewrite was worth it. Everything is cleaner, more modular, and the scraping pipeline actually handles the real-world mess of vendor pages (RSS feeds, JS-rendered docs, inline styles, you name it).
Would love for you all to give it a spin and let me know what vendors you'd want monitored next. 🚀