

Riftmap
Dependency intelligence for multi-repo engineering teams. Maps every cross-repo dependency in your GitLab or GitHub org so you know what breaks before you ship.
Cost / License
- Freemium (Subscription)
- Proprietary
Platforms
- Software as a Service (SaaS)




Riftmap
Features
Support for Docker
- Kubernetes
Riftmap News & Activities
Recent activities
- DanielWestgaard added Riftmap
DanielWestgaard added Riftmap as alternative to Backstage, Port, Sourcegraph and Dependabot
Riftmap information
What is Riftmap?
Riftmap reads your GitLab or GitHub org and draws the one graph your architecture actually runs on. Click any artifact, see the blast radius before you make a change. Around fifty repositories, the mental model breaks. The senior engineer who held the graph in their head takes a week off, and a one-line change in a base image lights up Slack for three hours. Riftmap fixes this by parsing the source files that already define your dependencies. No service catalog, no YAML to maintain, no annotations.
What it sees:
- Visual dependency graph across every cross-repo relationship, with pan, zoom, and filtering by ecosystem or team
- Blast radius analysis: pick any artifact, see every direct and transitive consumer, colour-coded by impact severity
- Artifact consumer tracking: which repos pull your Docker base image, on what tag, version drift highlighted
- Auto-discovered, never declared: the graph is parsed from Terraform sources, Dockerfiles, CI templates, and more
- One graph across 12+ ecosystems: Terraform, Docker, GitLab CI, GitHub Actions, Python, Go, npm, Ansible, Helm, Kubernetes, Kustomize, and ArgoCD
- Zero ops: managed cloud, read-only token, code never stored permanently
Free for 15 repos with no credit card. Setup in under 5 minutes. Built for platform engineers and DevEx teams managing polyrepo infrastructure-as-code at medium-to-large organisations.
