# Riftmap

> Riftmap is a cross-repo dependency intelligence tool for engineering teams and AI coding agents. 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, Kubernetes manifests, Kustomize overlays, and ArgoCD applications — and shows you exactly what breaks when you make a change. The same graph is served two ways: an interactive UI for engineers, and an HTTP API for AI coding agents to query during planning.

Riftmap is live as a managed cloud service at app.riftmap.dev. A self-hosted deployment option is planned for the future. The HTTP API ships with every deployment.

## What Riftmap does

- Automatically discovers and maps cross-repo dependencies across an entire org
- Supports 12 ecosystems: Terraform, Docker, GitLab CI, GitHub Actions, Python, Ansible, Helm, Go, npm, Kubernetes, Kustomize, ArgoCD
- Visualises dependency graphs with blast-radius analysis
- Shows which repositories are affected when a shared component changes
- Exposes the same graph as an HTTP API for AI coding agents — three endpoints (`/repositories/lookup`, `/repositories/{id}/context`, `/repositories/{id}/impact`) callable from Claude Code, Cursor, or any tool that can consume an OpenAPI schema. MCP server and CLI on the roadmap.
- 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; the HTTP API is included on every tier

## 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.

AI coding agents working across more than one repository (Claude Code, Cursor, Codex, and similar) are a second class of consumer: they call the HTTP API during planning to resolve repos, hydrate dependencies/dependents, and check transitive blast radius — a query that would otherwise cost ~6,000 tokens of file exploration is reduced to a ~200-token lookup.

## 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

## Showcases

Interactive dependency graphs of real open-source organisations, scanned by Riftmap. Each page embeds the live graph component — pan, zoom, click any repository to see its dependencies/dependants, and simulate the blast radius of a breaking change.

- Showcase index: https://riftmap.dev/showcase/
- "Prometheus dependency graph — interactive showcase": https://riftmap.dev/showcase/prometheus/

## 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/
- "What 56 Prometheus repos actually depend on": https://riftmap.dev/blog/what-56-prometheus-repos-depend-on/
- "What 208 kubernetes-sigs repos actually depend on": https://riftmap.dev/blog/what-208-kubernetes-sigs-repos-actually-depend-on/
- "The catalog maintenance trap: why service catalogs go stale": https://riftmap.dev/blog/the-catalog-maintenance-trap/
- "Meta needed 50+ AI agents to map their tribal knowledge. The most durable piece of their stack is the part you can build today.": https://riftmap.dev/blog/meta-tribal-knowledge-engine-build-the-graph-first/
- "AI coding agents need cross-repo context. The teams running them at scale are already building it themselves.": https://riftmap.dev/blog/ai-coding-agents-need-cross-repo-context/
- "You don't need a virtual monorepo. You need a graph.": https://riftmap.dev/blog/you-dont-need-a-virtual-monorepo/
- "Cross-repo context is in product docs. The graph is not.": https://riftmap.dev/blog/cross-repo-context-is-in-product-docs/
- "Symbol graphs and artifact graphs: why Sourcegraph stops where infrastructure starts": https://riftmap.dev/blog/symbol-graphs-and-artifact-graphs/

## Links

- Documentation: https://docs.riftmap.dev/introduction
- Agent integration docs: https://docs.riftmap.dev/agents
- API reference (OpenAPI schema): https://app.riftmap.dev/openapi.json
- MCP server & CLI roadmap: https://docs.riftmap.dev/agents/mcp-cli-roadmap
- Status (uptime / incidents): https://status.riftmap.dev/
- Series — Find Every Consumer: https://riftmap.dev/blog/series/find-every-consumer/
- Series — What an org actually depends on (Prometheus, kubernetes-sigs): https://riftmap.dev/blog/series/org-scans/
- 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 — also called "cross-repo context" (glossary): https://riftmap.dev/what-is-cross-repo-dependency-mapping/
- For AI coding agents (the graph as a tool call — three endpoints, freshness contract, working code in curl/Python/TypeScript, plus a 0:53 demo of a Claude Code session calling the API): https://riftmap.dev/for-agents/
- Security & data handling: https://riftmap.dev/security/
- Full product description for AI: https://riftmap.dev/llms-full.txt
- Hero demo video (18s, MP4, silent): https://riftmap.dev/videos/riftmap-graph-demo.mp4 — graph view, searching for a service, impact mode showing affected consumers at depth 1 and 2, focus mode showing a repo's dependants and dependencies
- Agent demo video — short loop on the homepage (0:15, MP4, silent, 2x, autoplay loop): https://riftmap.dev/videos/riftmap-agent-demo-short.mp4 — Claude Code inside VS Code; the agent receives a prompt about deleting a helm:deploy GitLab CI job, calls the Riftmap API for cross-repo consumers, returns 51 consumers across the org, and classifies them by whether they pin a version constraint or float on main
- Agent demo video — full walkthrough (0:53, MP4, silent, 2x): https://riftmap.dev/videos/riftmap-agent-demo.mp4 — the long-form version of the short loop above; the agent surfaces all 51 consumers, calls out a caveat about edge granularity, and lives on the /for-agents/ page