New

System Map

See your architecture. Know what breaks when you change a module.

Enable in dashboard Read the guide

How it works

What it maps

System Map builds a dependency graph from your repository code and configuration files. It maps module-to-infrastructure relationships, overlays incident history, and computes per-PR blast radius. The map rebuilds on every push to the default branch.

Module-to-infrastructure map

Pullminder reads your repository tree and connection strings to build a dependency graph of modules, datastores, queues, external APIs, and services. No config files required.

Incident overlay heat

When Collective Memory is enabled, Pullminder overlays incident counts onto the graph so you can see which parts of your architecture have been trouble-prone, right alongside the structural map.

PR blast radius

When a PR changes a module, Pullminder shows which downstream dependents are affected. Reviewers know what else might break before the merge button is pressed.

Org-wide stitching

When multiple repos have System Map enabled, Pullminder stitches their graphs together. Shared datastores and queues merge into one node, and cross-repo service edges are derived automatically.

The map is surfaced in the dashboard as an interactive graph. When Collective Memory is enabled, incident counts overlay onto each node, turning structural hotspots into risk hotspots at a glance.

Privacy

Opt-in, off by default, purgeable at any time

System Map builds its graph from your code transiently and stores nothing but derived metadata. It is opt-in per repository, off by default, and all data is purgeable from the dashboard.

Per-repository opt-in

Off by default for every repository. Enable it from the dashboard repo settings when you are ready.

Transient code access

Code is fetched to build the map, then deleted on disk and from memory. Only derived metadata (node keys, labels, types, and edge relationships) persists.

Secrets never stored

Connection strings and env literals are read transiently for classification, then discarded. A redacted handle like datastore:postgres is persisted where the real DSN once was.

Disabling purges data

Turn off System Map for a repository and all stored graph data (nodes, edges, and cached renders) is purged immediately and irreversibly.

CLI preview

Local map, no backend required

Run pullminder map in any repository to see its dependency graph right in your terminal. The local command uses the same extraction engine as the dashboard and never sends code anywhere.

Multiple output formats

pullminder map --format text|json|dot prints a summary table, JSON output, or a DOT graph you can pipe into Graphviz or rendering tools.

Zero configuration

No YAML files, no DSL, no agent deployment. Run the command and get a map of your local working tree in seconds.

FAQ

Questions you probably have

What does System Map actually map?
Code modules (directories), datastores (Postgres, MySQL, Redis, Mongo), queues (RabbitMQ, Kafka), external APIs (HTTP calls to third-party services), and internal services from Docker Compose files. It is a read-only architectural dependency map that never modifies your repository.
Does System Map store my code?
No. Code is fetched transiently to a temp directory, parsed for import statements and connection-string patterns, then the temp directory is deleted. Only derived metadata (node keys, labels, types, and edge relationships) is persisted. No source code, no diff content, no comment text is stored.
How is this different from Collective Memory?
Collective Memory tracks a file's incident history over time: reverts, hotfixes, churn. System Map shows the static architectural dependency graph of your repository with an optional incident overlay. They serve different purposes and work together when both are enabled on the same repository.
What are the current limits?
Phase 2 now supports org-wide stitching: when multiple repos have System Map enabled, they are merged into a single org graph. Per-repo caps of 5,000 nodes and 20,000 edges per build still apply. The map rebuilds on push to the default branch.
Does it work with private repositories?
Yes. System Map works with private repositories on all plans. The same opt-in and purge controls apply regardless of repository visibility.

Know your architecture before it breaks

Enable System Map from the dashboard. One toggle per repository. No YAML files, no DSL, no agent deployment.

Enable in dashboard Read the docs