Riftmap: See what breaks before you ship — across every repo

Hey Product Hunt! 👋 I'm Daniel, the maker of Riftmap. I built this because I kept watching the same thing happen at every org I worked with: a senior engineer leaves, and suddenly nobody knows which repos depend on what. Someone pushes a change to a shared Terraform module or CI template, and three teams' pipelines break because there was no way to see the blast radius. The usual answer is "just use Backstage" or "maintain a YAML catalog", but those go stale within weeks. I wanted something that discovers dependencies automatically from the actual code, with zero per-repo setup, and across different tools and languages. Riftmap connects to your GitLab or GitHub org with a read-only token, scans across 10+ ecosystems (Terraform, Docker, Helm, Go modules, npm, Kubernetes manifests, CI pipelines, and more), and builds a live dependency graph. The key feature most teams get excited about: impact analysis - before you ship a change, see exactly what downstream repos and pipelines will be affected. When I shared the idea on Reddit, the response blew me away; 86 comments, 30K+ views, and 6 people told me they'd built DIY versions of the exact same tool internally. That convergence told me this wasn't just my problem. Would love your feedback! Especially from anyone managing 50+ repos across mixed ecosystems. What's the first thing you'd want to see on the graph?