about / retired november 2026

Riftmap has shut down.

Riftmap mapped how the repositories in a GitHub or GitLab organisation depend on each other — Terraform modules, Docker base images, Go modules, shared CI templates — to answer one question: if I change this repo, what breaks? I built it alone and ran it as a hosted service until November 2026, when I shut it down. Account data and access tokens were deleted.

what's here / 01

What's still here, and what's gone.

Gone: the app at app.riftmap.dev, the API, the documentation and the status page. Links to the app, the documentation and the status page now land on this page. There is nothing to sign up for.

Your data: if you had an account, the service's database — your account, workspaces, scan data and any stored access tokens — was deleted when it shut down, along with its backups. I kept one pseudonymised copy of the dependency data as a record of the project: email addresses, access tokens and private organisation and repository names were removed, git contributors were replaced with pseudonyms, and the names of public open-source organisations were kept. The analytics and error-reporting services the app used still hold some account-linked data; the privacy page says what, and how to have it deleted. If you once gave Riftmap a personal access token, Riftmap's copy of it is gone, and you can revoke the token itself on GitHub or GitLab.

why it shut down / 02

The problem is real.
The product was narrower than it, and never met a buyer.

The problem is real. Practitioners had built their own cross-repo dependency tooling for their teams — four of the six who described theirs had arrived at the same parse-the-source architecture Riftmap used. That part of the bet held up.

The product was narrower than the problem. Riftmap answered a question about packaging: which repository's Docker image, Terraform module, Helm chart or CI template another repository builds on. Services that call each other over the network are coupled too, but that coupling is written in no manifest, so Riftmap could not see it. By September 2026 it had scanned 22 organisation connections — mostly public open-source code that I connected myself to test it — and 5 of them produced a graph that answered the question robustly. For months the thin graphs looked like a coverage bug; at least some of them were the limit of what reading manifests can show. Which kinds of organisation the approach suits was never properly tested.

It was never tested against a buyer. Riftmap never had a paying customer. A handful of people signed up and tried it, none of them stayed, and none of my follow-up emails got a reply. Running a hosted service that nobody depended on stopped making sense, so I shut it down.

origin / 03

Why I built it.

I'm a software and DevOps engineer. Across consulting engagements, personal projects, and conversations with other engineers, the same problem kept surfacing: someone updates a base image, a Terraform module, or a CI template — and three hours later Teams or Slack is on fire because nobody knew what depended on what.

I looked for a tool that actually mapped cross-repository, cross-language dependencies and showed what consumed what. Renovate kept versions updated but didn't show consumers. Backstage needed humans to maintain a catalog that went stale within weeks. HCP Terraform Explorer only handled Terraform. Nothing covered the real shape of the problem.

The deeper I looked, the clearer it became: parsing twelve ecosystems, resolving cross-registry references, handling incremental updates, keeping a graph fast at 500+ repos — this wasn't a weekend script. It was a product.

Before committing seriously, I tested whether this was a widespread problem or just one I kept running into, by posting in r/devops and r/terraform. Two threads, 86 comments and about 26,500 views later, the strongest signal wasn't the complaints: six practitioners replied that they had built their own cross-repo dependency tooling, four of them by parsing the source files. Each had solved part of the problem for their own team. None of them had productised it.

Riftmap was that pattern, finished instead of abandoned.

who / 04

Daniel Westgaard.
Built it, ran it, shut it down.

Daniel Westgaard, who built Riftmap

Software and DevOps engineer based in Norway, with a background in development, automation and platform engineering consulting. Riftmap was my independent venture, operated under Westgaard Technologies and shipped in small, steady increments until it was retired in November 2026.

If you want to talk about cross-repo dependencies, platform engineering, or anything on this site, my inbox is still open.

principles / 05

How I built it.

Riftmap had strong opinions, and some were unusual. I stated them publicly to keep the product honest. They still hold up.

  1. 01

    Deterministic first, AI later.

    Riftmap parsed source files with static analysis — no LLM in the critical path, no hallucinated edges. The graph was deterministic, so anything calling it got the same answer: a human in the UI, a dashboard, or a coding agent during planning. AI was the consumer of verified structure, never the source of it.

  2. 02

    No catalog to maintain.

    The moment a tool requires humans to keep a YAML file current, it's already wrong. Dependencies were parsed from the files that already define them.

  3. 03

    Self-hosted in the architecture from day one.

    It launched as SaaS, for engineering orgs where shipping fast matters more than sovereignty. But I've consulted at Norwegian government agencies where nothing can leave the network, so the design kept a self-hosted path open throughout. That version never shipped.

  4. 04

    One answer per question.

    No configurable everything. Riftmap had opinions about how cross-repo dependency graphs should be modelled, and enforcing them kept the graph fast, legible, and comparable across orgs.

  5. 05

    Ship the small thing that works.

    Twelve ecosystems, not two. Incremental scans, not nightly re-clones. Canvas rendering above 900 repos because force-directed layouts die there. Each one was a concrete answer to a concrete problem — not a feature-matrix bullet.

norway / 06

Built in Norway.

Designed, built and operated from Norway, with GDPR as the default and a bias toward data protection that came from the regulated environments it was designed for.

See what it did.

no signup saved scans of real public orgs runs in your browser