DepGraph: Indie SaaS Third-Party Dependency Risk Scorer

The Problem

A recurring HN thread topic is indie SaaS founders discovering that a critical third-party service they depend on (a payment processor, email API, auth provider, or data enrichment tool) has been acquired, sunset, or changed pricing — often with 30 days notice. DepGraph lets a founder map their entire stack's external dependencies, then monitors each vendor for acquisition news, pricing page changes, status degradation trends, and forum chatter about reliability, sending a weekly risk digest so the founder knows which dependencies are becoming liabilities before it's a crisis.

Target Audience

Solo and small-team SaaS founders running production apps with 5+ third-party dependencies who have been burned by a vendor change

Monetization Angle

$15/mo for up to 20 monitored dependencies with weekly risk digests; $39/mo for real-time alerts and unlimited dependencies

Recommended Tech Stack

Why Now

The wave of VC-backed dev tools being acquired or sunset (Parse, Mailchimp price hikes, Heroku free tier removal, Pusher pricing changes) has created acute awareness among indie founders that vendor risk is existential.

MVP Scope

A manual form where a founder enters 5 vendor names, and a weekly email is sent with a hand-curated summary of any news or pricing changes found via Google News — no scraping automation needed at first.

AI Angle

AI reads scraped vendor blog posts, changelog pages, and HN comment threads to classify whether a signal represents a high-risk event (price increase, acquisition, deprecation) or routine noise.

Primary Risk

Reliable automated detection of pricing changes and acquisition news across hundreds of vendor websites requires significant scraping infrastructure that is brittle and expensive to maintain.

Validation Checklist

• Search HN for 'vendor sunset', 'pricing change', 'service shutting down' and catalog how many top comments are from indie founders who were caught off guard
• Post 'What's your process for monitoring vendor risk in your stack?' on r/indiehackers and measure whether most founders say 'I have none'
• Build a Notion-based manual version for 10 beta users and manually research their stated dependencies weekly for one month to prove the value before automating
• Check if existing uptime monitors like Better Uptime or Checkly address vendor business risk (they don't) to confirm the gap is real and unaddressed

Who Would Pay For This

Likely buyers are engineering teams, platform leads, developer-experience teams, and technical founders. Start with Solo and small-team SaaS founders running production apps with 5+ third-party dependencies who have been burned by a vendor change and look for teams already spending time or money on this workflow.

First 10 Users

Find the first 10 users by searching for recent complaints around "developer tools SaaS" in Hacker News, developer communities, GitHub issues, and niche Slack or Discord groups. Offer a concierge version first: manually solve the workflow for a few users, then automate only the repeated steps.

Idea Playbooks

This opportunity also appears in curated IdeaGenius playbooks for builders comparing adjacent markets.

More Developer Search Paths

Why This Idea Has Legs

• Sourced from real discussions and complaints across Reddit and social media
• Cross-checked against recurring demand signals in the IdeaGenius archive
• Difficulty rated Medium — buildable by a solo developer or small team
• Clear monetization path from day one

Generate Your Full Project Spec

Get a complete blueprint for building this app — tech stack, database schema, API endpoints, go-to-market plan, and more. Generated by AI in seconds. Download as Markdown.