# Riftmap

> Riftmap is a dependency intelligence tool for engineering teams. It scans your GitLab or GitHub organisation, maps every cross-repository dependency — Terraform modules, Docker base images, CI/CD templates, Python packages, Go modules, npm packages, Helm charts, Ansible roles, and Kubernetes manifests — and shows you exactly what breaks when you make a change.

Riftmap is live as a managed cloud service at app.riftmap.dev. A self-hosted deployment option is planned for the future.

## What Riftmap does

- Automatically discovers and maps cross-repo dependencies across an entire org
- Supports 10+ ecosystems: Terraform, Docker, GitLab CI, GitHub Actions, Python, Ansible, Helm, Go, npm, Kubernetes/Kustomize
- Visualises dependency graphs with blast-radius analysis
- Shows which repositories are affected when a shared component changes
- Works with GitLab (CE/EE) and GitHub (cloud and Enterprise)
- Managed cloud service: zero infrastructure to set up, isolated per workspace
- Free tier: up to 15 repos, no credit card required

## Target users

Platform engineers, DevOps teams, and engineering leads at companies with 10–200+ repositories who need to safely manage shared infrastructure and understand the downstream impact of changes.

## Key problems solved

- "What breaks if I update this Terraform module?" — answered instantly
- Replaces manual grepping, stale Backstage catalogs, and tribal knowledge
- Fills the gap that Renovate/Dependabot, HCP Terraform Explorer, and monorepo tooling leave

## Pricing

- Free: $0/month, up to 15 repos, 1 user, 1 org connection
- Team: $49/month, up to 100 repos, 5 users, daily incremental scans
- Business: $149/month, up to 500 repos, 15 users, near real-time scans
- Enterprise: custom pricing, contact sales

## Blog

Riftmap publishes articles on platform engineering, cross-repo dependency management, and infrastructure visibility.

- Blog index: https://riftmap.dev/blog/
- "The Infrastructure Dependency Problem No One Has Solved": https://riftmap.dev/blog/infrastructure-dependency-problem/
- "Auto-Discovering Infrastructure Dependencies Across 10 Ecosystems": https://riftmap.dev/blog/auto-discovering-infrastructure-dependencies-across-10-ecosystems/
- "The State of Infrastructure Dependency Tooling in 2026": https://riftmap.dev/blog/the-state-of-infrastructure-dependency-tooling-2026/
- "How to Find Every Consumer of Your Docker Base Image": https://riftmap.dev/blog/how-to-find-every-consumer-of-your-docker-base-image/
- "How to Find Every Consumer of Your Terraform Module": https://riftmap.dev/blog/how-to-find-every-consumer-of-your-terraform-module/
- "How to Find Every Consumer of Your GitHub Actions Workflow": https://riftmap.dev/blog/how-to-find-every-consumer-of-your-github-actions-workflow/
- "How to Find Every Consumer of Your Helm Chart": https://riftmap.dev/blog/how-to-find-every-consumer-of-your-helm-chart/
- "How to Find Every Consumer of Your Go Module": https://riftmap.dev/blog/how-to-find-every-consumer-of-your-go-module/
- "AI Doesn't Understand Blast Radius: Why Change Failure Rates Are Up 30%": https://riftmap.dev/blog/ai-doesnt-understand-blast-radius/
- "Change failure rate is up 30% — here's how to measure yours in an afternoon": https://riftmap.dev/blog/measure-your-change-failure-rate/

## Links

- Series — Find Every Consumer: https://riftmap.dev/blog/series/find-every-consumer/
- Homepage: https://riftmap.dev/
- App (sign up / log in): https://app.riftmap.dev
- About (founder story, principles, roadmap): https://riftmap.dev/about/
- Pricing: https://riftmap.dev/pricing/
- Blog: https://riftmap.dev/blog/
- How it works: https://riftmap.dev/#how-it-works
- Deployment options: https://riftmap.dev/#deployment
- What is cross-repo dependency mapping (glossary): https://riftmap.dev/what-is-cross-repo-dependency-mapping/
- Security & data handling: https://riftmap.dev/security/
- Full product description for AI: https://riftmap.dev/llms-full.txt